Reference Guide
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 Add the DSCP value for ACL matching.
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 the non-contiguous mask and added the
monitor option. Deprecated the keyword established.
Version 6.5.10 Expanded to include the optional QoS order priority for the ACL
entry.
Usage
Information
The monitor option is relevant in the context of flow-based monitoring only. For more
information, refer to Port Monitoring.
The order option is relevant in the context of the Policy QoS feature only. The following
applies:
• The seq sequence-number command is applicable only in an ACL group.
• The order option works across ACL groups that have been applied on an interface
via the QoS policy framework.
• The order option takes precedence over seq sequence-number.
• If sequence-number is not configured, the rules with the same order value are
ordered according to their configuration order.
• If sequence-number is configured, the sequence-number is used as a tie breaker
for rules with the same order.
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.
If you configure the sequence-number, the sequence-number is used as a tie breaker
for rules with the same order.
NOTE: When ACL logging and byte counters are configured simultaneously, byte counters
may display an incorrect value. Configure packet counters with logging instead.
Related
Commands
deny — configures a filter to drop packets.
213