Reference Guide

214 | Access Control Lists (ACL)
www.dell.com | support.dell.com
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.
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.
The
monitor option is relevant in the context of flow-based monitoring only. Refer to
the Port Monitoring chapter.
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.
For example, an ACL rule with TCP port
range 4000 - 8000 uses 8 entries in the
CAM:
Rule# Data Mask From To #Covered
1 0000111110100000 1111111111100000 4000 4031 32
2 0000111111000000 1111111111000000 4032 4095 64
3 0001000000000000 1111100000000000 4096 6143 2048
4 0001100000000000 1111110000000000 6144 7167 1024
5 0001110000000000 1111111000000000 7168 7679 512
6 0001111000000000 1111111100000000 7680 7935 256
7 0001111100000000 1111111111000000 7936 7999 64
8 0001111101000000 1111111111111111 8000 8000 1
Total Ports: 4001
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.
Deprecated
established keyword.
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.