Users Guide

monitor (OPTIONAL) Enter the keyword monitor when the rule is describing the trac that you
want to monitor and the ACL in which you are creating the rule is applied to the
monitored interface.
NOTE: For more information, refer to the Flow-based Monitoring section in the
Port Monitoring chapter of the Dell Networking OS Conguration Guide .
Defaults
By default, 10 ACL logs are generated if you do not specify the threshold explicitly. The default frequency at which
ACL logs are generated is ve minutes. By default, ow-based monitoring is not enabled.
Command Modes CONFIGURATION-EXTENDED-ACCESS-LIST
Supported Modes Full–Switch
Command History
Version Description
9.9(0.0) Introduced on the FN IOM.
9.4(0.0) Added support for ow-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 ow-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 congured, the rules with the same order value are ordered according to their
conguration order.
• If sequence-number is congured, 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) lters in an ACL congured with ARP or Ether-type (Layer 2) lters.
Apply Layer 2 ACLs to interfaces in Layer 2 mode.
When the congured maximum threshold is exceeded, generation of logs is stopped. When the interval at which
ACL logs are congured 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 congured
threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the congured 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
Access Control Lists (ACL)
245