Deployment Guide

mask (OPTIONAL) Enter a network mask in /prex format (/x) or A.B.C.D. The mask, when
specied in A.B.C.D format, may be either contiguous or non-contiguous.
any Enter the keyword any to specify that all routes are subject to the lter.
host ip-address Enter the keyword host then the IP address to specify a host IP address or hostname.
count (OPTIONAL) Enter the keyword count to count packets processed by the lter.
bytes (OPTIONAL) Enter the keyword bytes to count bytes processed by the lter.
dscp (OPTIONAL) Enter the keyword dcsp to match to the IP DCSCP values.
order (OPTIONAL) Enter the keyword order to specify the QoS priority for the ACL entry. The
range is from 0 to 254 (where 0 is the highest priority and 254 is the lowest; lower-order
numbers have a higher priority). If you do not use the keyword order, the ACLs have the
lowest order by default (255).
fragments Enter the keyword fragments to use ACLs to control packet fragments.
log (OPTIONAL) Enter the keyword log to enable the triggering of ACL log messages.
threshold-in msgs
count
(OPTIONAL) Enter the threshold-in-msgs keyword followed by a value to indicate
the maximum number of ACL logs that can be generated, exceeding which the generation
of ACL logs is terminated with the seq, permit, or deny commands. The threshold
range is from 1 to 100.
interval minutes (OPTIONAL) Enter the keyword interval followed by the time period in minutes at
which ACL logs must be generated. The interval range is from 1 to 10 minutes.
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.
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
platforms.
9.3(0.0) Added support for logging of ACLs on the MXL 10/40GbE Switch IO Module platform.
Usage Information
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
can congure ACL logging only on ACLs that are applied to ingress interfaces; you cannot enable logging for ACLs
that are associated with egress interfaces.
Access Control Lists (ACL) 233