CLI Guide

Version Description
9.4(0.0) Added the support for ow-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.
8.2.1.0 Allows ACL control of fragmented packets for IP (Layer 3) ACLs.
8.1.1.0 Introduced on the E-Series ExaScale.
7.4.1.0 Added the monitor option.
6.5.10 Expanded to include the optional QoS order priority for the ACL entry.
Usage Information
The order option is relevant in the context of the Policy QoS feature only. For more information, refer to the
“Quality of Service” chapter of the Dell Networking OS Conguration Guide.
NOTE: When ACL logging and byte counters are congured simultaneously, byte counters may display
an incorrect value. Congure packet counters with logging instead.
When you use the log option, the CP processor logs details about the packets that match. Depending on how
many packets match the log entry and at what rate, the CP may become busy as it has to log these packets’
details.
The monitor option is relevant in the context of ow-based monitoring only. For more information, refer to Port
Monitoring.
You cannot include IP, TCP, or UDP lters in an ACL congured with ARP lters.
When the congured maximum threshold is exceeded, generation of logs is stopped. When the interval at which
ACL logs are congured 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 congured
threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the congured 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 congure 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 ow-based monitoring for a monitoring session by entering the flow-based enable
command in the Monitor Session mode. When you enable this capability, trac with particular ows 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 specied trac
instead all trac on the interface. This feature is particularly useful when looking for malicious trac. It is available
for Layer 2 and Layer 3 ingress and egress trac. You may specify trac 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).
permit icmp
Congure a lter to allow all or specic ICMP messages.
Syntax
permit icmp {source mask | any | host ip-address} {destination mask | any |
host ip-address} [dscp] [message-type] [count [byte]] [order] [fragments]
[threshold-in-msgs [count]]
228 Access Control Lists (ACL)