Service Manual

Command Modes CONFIGURATION-EXTENDED-ACCESS-LIST
Command History
Version Description
9.9(0.0) Introduced on the FN IOM.
9.4(0.0) Added support for flow-based monitoring on the MXL 10/40GbE Switch IO Module
platform.
9.3(0.0) Added support for logging of ACLs on the MXL 10/40GbE Switch IO Module platform.
8.2.1.0 Allows ACL control of fragmented packets for IP (Layer 3) ACLs.
8.1.1.0 Introduced on the E-Series ExaScale.
7.4.1.0 Added the monitor option.
6.5.10 Expanded to include the optional QoS order priority for the ACL entry.
Usage Information
The monitor option is relevant in the context of flow-based monitoring only. For more information, refer to Port
Monitoring.
The order option is relevant in the context of the Policy QoS feature only. The following applies:
• The seq sequence-number command is applicable only in an ACL group.
• The order option works across ACL groups that have been applied on an interface via the QoS policy
framework.
• The order option takes precedence over seq sequence-number.
• If sequence-number is not configured, the rules with the same order value are ordered according to their
configuration order.
• If sequence-number is configured, the sequence-number is used as a tie breaker for rules with the same
order.
When you use the log option, the CP processor logs details about the packets that match. Depending on how
many packets match the log entry and at what rate, the CP may become busy as it has to log these packets’
details.
You cannot include IP, TCP, or UDP (Layer 3) filters in an ACL configured with ARP or Ether-type (Layer 2) filters.
Apply Layer 2 ACLs to interfaces in Layer 2 mode.
When the configured maximum threshold is exceeded, generation of logs is stopped. When the interval at which
ACL logs are configured to be recorded expires, the subsequent, fresh interval timer is started and the packet
count for that new interval commences from zero. If ACL logging was stopped previously because the configured
threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the configured threshold is exceeded, it is re-enabled after the logging interval
period elapses. ACL logging is supported for standard and extended IPv4 ACLs, IPv6 ACLs, and MAC ACLs. You
can configure ACL logging only on ACLs that are applied to ingress interfaces; you cannot enable logging for ACLs
that are associated with egress interfaces.
You can activate flow-based monitoring for a monitoring session by entering the flow-based enable
command in the Monitor Session mode. When you enable this capability, traffic with particular flows that are
traversing through the ingress and egress interfaces are examined and, appropriate ACLs can be applied in both
the ingress and egress direction. Flow-based monitoring conserves bandwidth by monitoring only specified traffic
instead all traffic on the interface. This feature is particularly useful when looking for malicious traffic. It is available
for Layer 2 and Layer 3 ingress and egress traffic. You may specify traffic using standard or extended access-lists.
234
Access Control Lists (ACL)