Reference Guide
count (OPTIONAL) Enter the keyword count to count packets the filter
processes.
byte (OPTIONAL) Enter the keyword byte to count bytes the filter
processes.
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 0 to 254 (where 0 is the highest priority
and 254 is the lowest; lower-order numbers have a higher priority). If
you do 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.
NOTE: For more information, refer to the Flow-based Monitoring
section in the Port Monitoring chapter of the
FTOS Configuration
Guide
.
Defaults Not configured
Command Modes CONFIGURATION-EXTENDED-ACCESS-LIST
Command History
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 the monitor option.
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.
284