Service Manual

To remove this filter, you have two choices:
Use the no seq sequence-number command syntax if you know the filter’s sequence number
Use the no deny {ipv6-protocol-number | icmp | ipv6 | tcp | udp} command
Parameters
count OPTIONAL) Enter the keyword count to count packets processed by the filter.
byte (OPTIONAL) Enter the keyword byte to count bytes processed by the filter.
dscp (OPTIONAL) Enter the keyword dscp to match to the IP DSCP values.
order (OPTIONAL) Enter the keyword order to specify the QoS order of 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 order keyword, the
ACLs have the lowest order by default as
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 time interval range is from 1 to 10 minutes.
monitor (OPTIONAL) Enter the keyword monitor when the rule is describing the traffic 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 five minutes. By default, flow-based monitoring is not enabled.
Command Modes ACCESS-LIST
Command History
Version Description
9.9(0.0) Introduced on the FN IOM.
9.4(0.0) Added the support for flow-based monitoring on theMXL 10/40GbE Switch IO Module
platform.
9.3(0.0) Added the support for logging of ACLs on the MXL 10/40GbE Switch IO Module
platform.
Usage Information
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.
Access Control Lists (ACL) 253