Reference Guide

NOTE: For more information, refer to the Flow-based Monitoring
section in the Port Monitoring chapter of the
FTOS Configuration
Guide
.
fragments Enter the keyword fragments to use ACLs to control packet
fragments.
Defaults Not configured.
Command Modes CONFIGURATION-EXTENDED-ACCESS-LIST
Command History
This guide is platform-specific. For command information about other platforms, refer to the
relevant
FTOS Command Line Reference Guide
.
The following is a list of the FTOS version history for this command.
Version 8.3.19.0 Introduced on the S4820T.
Version 8.3.11.1 Introduced on the Z9000.
Version 8.3.7.0 Introduced on the S4810.
Version 8.3.1.0 Added the keyword dscp.
Version 8.2.1.0 Allows ACL control of fragmented packets for IP (Layer 3) ACLs.
Version 8.1.1.0 Introduced on the E-Series ExaScale.
Version 7.6.1.0 Introduced on the S-Series.
Version 7.5.1.0 Introduced on the 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.
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
FTOS Configuration Guide
.
NOTE: When ACL logging and byte counters are configured simultaneously, byte counters
may display an incorrect value. Configure 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 S-Series cannot count both packets and bytes; when you enter the count byte options,
only bytes are incremented.
The monitor option is relevant in the context of flow-based monitoring only. For more
information, refer to Port Monitoring.
Most ACL rules require one entry in the CAM. However, rules with TCP and UDP port operators
(for example, gt, lt, or 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.
186