Reference Guide
byte (OPTIONAL) Enter the keyword byte to count bytes processed by
the filter.
log (OPTIONAL, E-Series only) Enter the keyword log to have the
information kept in an ACL log file.
order (OPTIONAL) Enter the keyword order to specify the QoS priority for
the ACL entry. The range is from 0 to 254 (where 0 is the highest
priority and 254 is the lowest; lower order numbers have a higher
priority) If you did not use the keyword order, the ACLs have the
lowest order by default (255).
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 is applied to the monitored interface. For more
information, 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.
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.4.1.0 Added support for non-contiguous mask and added the monitor
option.
Version 6.5.1.0 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
.
The monitor option is relevant in the context of flow-based monitoring only. For more
information, refer to the Port Monitoring chapter.
When you use the log option, the CP processor logs details 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.
193