Reference Guide

222 | Access Control Lists (ACL)
www.dell.com | support.dell.com
Defaults
Not configured.
Command Modes
CONFIGURATION-EXTENDED-ACCESS-LIST
Command
History
Usage
Information
The order option is relevant in the context of the Policy QoS feature only. Refer to the Quality
of Service chapter of the FTOS Configuration Guide for more information.
The
monitor option is relevant in the context of the flow-based monitoring feature only. Refer
to the Port Monitoring chapter.
When you use the
log option, 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 C-Series and S-Series cannot count both packets and bytes, so when you enter the
count
byte
options, only bytes are incremented.
Most ACL rules require one entry in the CAM. However, rules with TCP and UDP port
operators (
gt, lt, range) may require more than one entry. The range of ports is configured in
the CAM based on bit mask boundaries; the space required depends on exactly what ports are
included in the range.
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 will be applied to the monitored interface. For details, refer to the section
“Flow-based Monitoring” in the Port Monitoring chapter of the FTOS
Configuration Guide.
fragments Enter the keyword fragments to use ACLs to control packet fragments.
Version 8.3.1.0 Added dscp keyword.
Version 8.2.1.0 Allows ACL control of fragmented packets for IP (Layer 3) ACLs.
Version 8.1.1.0 Introduced on E-Series ExaScale
Version 7.6.1.0 Added support for S-Series
Version 7.5.1.0 Added support for C-Series
Version 7.4.1.0 Added support for non-contiguous mask and added the
monitor option.
Version 6.5.10 Expanded to include the optional QoS order priority for the ACL entry.
Note: When ACL logging and byte counters are configured simultaneously, byte
counters may display an incorrect value. Configure packet counters with logging
instead.