destination
address
Enter the IPv6 address of the network or host to which the
packets are sent in the x:x:x:x::x format followed by the
prefix length in the /x format. The range is /0 to /128. The ::
notation specifies successive hexadecimal fields of zero.
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.
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 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 the ACL logs are generated in five minutes. By
default, flow-based monitoring is not enabled.
Command
Modes
ACCESS-LIST
Command
History
Version 9.4(0.0)
Added support for flow-based monitoring on the MXL
10/40GbE Switch IO Module platform.
Version 9.3(0.0)
Added 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
270
Access Control Lists (ACL)