Operation Manual

Security ACL Commands
Security ACL Commands
15 – 407
Leaves in secondary Number of ACL data entries stored in secondary leaf memory.
Sum node depth Total number of security ACL data entries.
Fragmentation
control
Control value for handling fragmented IP packets.
Note: The current MSS version filters only the first packet of a fragmented
IP packet and passes the remaining fragments.
UC switchdest Control value for handling fragmented IP packets.
Note: The current MSS version filters only the first packet of a fragmented
IP packet and passes the remaining fragments.
Port number Control value for handling fragmented IP packets.
Note: The current MSS version filters only the first packet of a fragmented
IP packet and passes the remaining fragments.
Number of action
types
Number of actions that can be performed by ACLs. This value is always 2, because
ACLs can either permit or deny.
LUdef in use Number of the lookup definition (LUdef) table currently in use for packet handling.
Default action
pointer
Memory address used for packet handling, from which default action data is obtained
when necessary.
L4 global Security ACL mapping on the MX switch:
❑ True—Security ACLs are mapped.
❑ False—No security ACLs are mapped.
No rules Security ACE rule mapping on the MX switch:
❑ True—No security ACEs are mapped.
❑ False—Security ACEs are mapped.
Non-IP rules Non-IP security ACE mapping on the MX switch:
❑ True—Non-IP security ACEs are mapped.
❑ False—Only IP security ACEs are mapped.
Note: The current MSS version supports security ACEs for IP only.
Root in first
Leaf buffer allocation:
❑ True—Enough primary leaf buffers are allocated in nonvolatile memory to
accommodate all leaves.
❑ False—Insufficient primary leaf buffers are allocated in nonvolatile memory to
accommodate all leaves.
Static default action Definition of a default action:
❑ True—A default action types is defined.
❑ False—No default action type is defined.
No per-user (MAC)
mapping
Per-user application of a security ACL with the Filter-Id attribute, on the MX switch:
❑ True—No security ACLs are applied to users.
❑ False—Security ACLs are applied to users.
Out mapping Application of security ACLs to outgoing traffic on the MX switch:
❑ True—Security ACLs are mapped to outgoing traffic.
❑ False—No security ACLs are mapped to outgoing traffic.
In mapping Application of security ACLs to incoming traffic on the MX switch:
❑ True—Security ACLs are mapped to incoming traffic.
❑ False—No security ACLs are mapped to incoming traffic.
Table 15– 1. show security acl resource-usage Output (continued)
Field Description