CLI Guide
• Use the no seq sequence-number command if you know the lter’s sequence number.
• Use the no deny {any | mac-source-address mac-source-address-mask} command.
Parameters
any Enter the keyword any to specify that all routes are subject to the lter.
mac-source-
address
Enter a MAC address in nn:nn:nn:nn:nn:nn format.
mac-source-
address-mask
(OPTIONAL) Specify which bits in the MAC address must match. If no mask is specied,
a mask of 00:00:00:00:00:00 is applied (in other words, the lter allows only MAC
addresses that match).
count (OPTIONAL) Enter the keyword count to count packets processed by the lter.
byte (OPTIONAL) Enter the keyword byte to count bytes processed by the lter.
log (OPTIONAL) Enter the keywordlog to enable the triggering of ACL log messages.
threshold-in-msgs
count
(OPTIONAL) Enter thethreshold-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 threshold range is from 1 to 10 minutes.
monitor (OPTIONAL) Enter the keyword monitor when the rule is describing the trac 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-MAC ACCESS LIST-STANDARD
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.3.16.1 Introduced on the MXL 10/40GbE Switch IO Module platform.
Usage Information
When the congured maximum threshold is exceeded, generation of logs is stopped. When the interval at which
ACL logs are congured 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 congured
threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the congured 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 congure 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) 183