Users Guide
forwards (mirrors) them to another port. The source port is the monitored port (MD) and the destination 
port is the monitoring port (MG).
Related Commands
deny — assigns a lter to deny IP trac.
deny udp — assigns a lter to deny UDP trac.
deny udp (for Extended IP ACLs)
To drop user datagram protocol (UDP) packets meeting the lter criteria, congure a lter.
Syntax
deny udp {source mask | any | host ip-address} [operator port [port]] 
{destination mask | any | host ip-address} [dscp] [operator port [port]] 
[count [byte]] [order] [fragments] [log [interval minutes] [threshold-in-
msgs [count]]
To remove this lter, you have two choices:
• Use the no seq sequence-number command if you know the lter’s sequence number.
• Use the no deny udp {source mask | any | host ip-address} {destination 
mask | any | host ip-address} command.
Parameters
log (OPTIONAL) Enter the keyword log to enable the triggering of ACL log messages.
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.
interval minutes (OPTIONAL) Enter the keyword interval followed by the time period in minutes 
at which ACL logs must be generated. The time interval range is from 1 to 10 
minutes.
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 ve minutes.
Command Modes CONFIGURATION-EXTENDED-ACCESS-LIST
Command History
Version 9.3(0.0) Added support for logging of ACLs on the S4810, S4820T, and Z9000 platforms.
Usage Information
When the congured maximum threshold is exceeded, generation of logs is stopped. When the interval at 
which ACL logs are congured 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 congured threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the congured 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 congure ACL logging only on ACLs that are applied to ingress interfaces; you cannot 
enable logging for ACLs that are associated with egress interfaces.
Access Control Lists (ACL)
279










