Service Manual

host ipv6-address Enter the keyword host then the IPv6 address of the host in the x:x:x:x::x format. The ::
notation specifies successive hexadecimal fields of zero.
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 then the prefix length in the /x format. The range is from /0 to /128.
The :: notation specifies successive hexadecimal fields of zero.
message-type (OPTIONAL) Enter an ICMP message type, either with the type (and code, if necessary)
numbers or with the name of the message type. The range is from 0 to 255 for ICMP
type and from 0 to 255 for ICMP code.
count (OPTIONAL) Enter the keyword count to count packets the filter processes.
byte (OPTIONAL) Enter the keyword byte to count bytes the filter processes.
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 to monitor traffic on the monitoring interface
specified in the flow-based monitoring session along with the filter operation.
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 the MXL 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
9.2(0.0) Introduced 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.
You can activate flow-based monitoring for a monitoring session by entering the flow-based enable
command in the Monitor Session mode. When you enable this capability, traffic with particular flows that are
traversing through the ingress and egress interfaces are examined and, appropriate ACLs can be applied in both
IPv6 Access Control Lists (IPv6 ACLs) 611