Addendum

• Use the no deny {ipv6-protocol-number | icmp | ipv6 | tcp |
udp} command
Parameters
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. You can enter a threshold in the range of 1-100.
interval
minutes
(OPTIONAL) Enter the keyword interval followed by the
time period in minutes at which ACL logs must be generated.
You can enter an interval in the range of 1-10 minutes.
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 5 minutes.
Command
Modes
ACCESS-LIST
Command
History
Version 9.3.0.0 Added support for logging of ACLs on the S4810, S4820T,
Z9000, M I/O Aggregator and MXL 10/40GbE Switch IO
Module platforms.
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 reenabled for this new interval.
If ACL logging is stopped because the configured threshold is exceeded, it is
reenabled after the logging interval period elapses. ACL logging is supported for
standard and extended IPv4 ACLs, standard and extended IPv6 ACLs, and standard
and extended 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.
Flow-Based Monitoring Support for ACLs
This functionality to enable flow-based monitoring is supported on the S4810, S4820T, S6000, Z9000,
I/O Aggregator, and MXL platforms.
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 ingresss traffic. You may specify traffic using standard or extended access-lists. This mechanism
copies all incoming packets on one port and forwards (mirrors) them to another port. The source port is
the monitored port (MD) and the destination port is the monitoring port (MG).
The port mirroring application maintains and performs all the monitoring operations on the chassis. ACL
information is sent to the ACL manager, which in turn notifies the ACL agent to add entries in the CAM
area. Duplicate entries in the ACL are not saved.
Access Control Lists
81