White Papers

To remove this filter, you have two choices:
● Use the no seq sequence-number command, if you know the filter’s sequence number.
● Use the no deny icmp {source mask | any | host ip-address} {destination
mask | any | host ip-address} command.
Parameters
source Enter the IP address of the network or host from which the packets were sent.
mask Enter a network mask in /prefix format (/x) or A.B.C.D. The mask, when specified
in A.B.C.D format, may be either contiguous or non-contiguous.
any Enter the keyword any to specify that all routes are subject to the filter.
host ip-address Enter the keyword host then the IP address to specify a host IP address.
destination Enter the IP address of the network or host to which the packets are sent.
dscp Enter this keyword dscp to deny a packet based on the DSCP value. The range is
from 0 to 63.
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.
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).
fragments Enter the keyword fragments to use ACLs to control packet fragments.
threshold-in
msgs count
(OPTIONAL) Enter the threshold-in-msgs keyword followed by a value to
indicate the maximum number of ACL logs that can be generated, exceeding
which the generation of ACL logs is terminated with the seq, permit, or deny
commands. The threshold range is from 1 to 100.
Defaults
By default, 10 ACL logs are generated if you do not specify the threshold explicitly. The default frequency
at which ACL logs are generated is five minutes. By default, flow-based monitoring is not enabled.
Command Modes CONFIGURATION-IP ACCESS-LIST-EXTENDED
Supported Modes Full–Switch
Command
History
Version Description
9.9(0.0) Introduced on the FN IOM.
9.4(0.0) Added the support for flow-based monitoring on the MXL 10/40GbE Switch IO
Module.
9.3(0.0) Added the support for logging ACLs on the MXL 10/40GbE Switch IO Module.
8.3.16.1 Introduced on the MXL 10/40GbE Switch IO Module.
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 Dell Networking OS Configuration Guide.
When the configured maximum threshold is exceeded, generation of logs is stopped. When the interval
at which ACL logs are configured to be recorded expires, the subsequent, fresh interval timer is started
and the packet count for that new interval commences from zero. If ACL logging was stopped previously
because the configured threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the configured threshold is exceeded, it is re-enabled after the logging
interval period elapses. ACL logging is supported for standard and extended IPv4 ACLs, IPv6 ACLs, and
MAC ACLs. You can configure ACL logging only on ACLs that are applied to ingress interfaces; you
cannot enable logging for ACLs that are associated with egress interfaces.
You can activate flow-based monitoring for a monitoring session by entering the flow-based
enablecommand in the Monitor Session mode. When you enable this capability, traffic with particular
flows that are traversing through the ingress and egress interfaces are examined and, appropriate ACLs
can be applied in both the ingress and egress direction. Flow-based monitoring conserves bandwidth by
Access Control Lists (ACL) 201