White Papers

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 Not configured.
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 flow-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.
Usage
Information
When the configured maximum threshold is exceeded, generation of logs are 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, Pv6 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 the ingress and egress direction. 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 ingress and egress traffic. You may
specify traffic using standard or extended access-lists. This mechanism copies all incoming or outgoing
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).
Related
Commands
deny — configures a MAC ACL filter to drop packets.
seq —configure a MAC ACL filter with a specified sequence number.
seq
To a deny or permit filter in a MAC access list while creating the filter, assign a sequence number.
Syntax
seq sequence-number {deny | permit} {any | mac-source-address [mac-source-
address-mask]} [count [byte]] [log [interval minutes] [threshold-in-msgs
[count]] [monitor]
To remove this filter, use the no seq sequence-number command.
Parameters
sequence-
number
Enter a number from 0 to 65535.
216 Access Control Lists (ACL)