Reference Guide

Access Control Lists (ACL) | 221
Defaults
Not configured.
Command Modes
CONFIGURATION-EXTENDED-ACCESS-LIST
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
monitor option is relevant in the context of flow-based monitoring only. Refer to
the Port Monitoring chapter.
You cannot include IP, TCP or UDP filters in an ACL configured with ARP filters.
count (OPTIONAL) Enter the keyword count to count packets processed
by the filter.
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.
Range: 0-254 (where 0 is the highest priority and 254 is the
lowest; lower order numbers have a higher priority)
Default: If the order keyword is not used, 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 will be applied to the monitored interface.
For details, 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.
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.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.
Note: When ACL logging and byte counters are configured simultaneously, byte
counters may display an incorrect value. Configure packet counters with logging
instead.