Users Guide

permit udp (for IPv6 ACLs)
Congure a lter to pass UDP packets meeting the lter criteria.
Syntax
permit udp {source address mask | any | host ipv6-address} [operator port
[port]] {destination address | any | host ipv6-address} [operator port
[port]] [count [byte]] [log [interval minutes] [threshold-in-msgs [count]]
[monitor]
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 permit udp {source address mask | any | host ipv6-address}
{destination address | any | host ipv6-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 interval range is from 1 to 10 minutes.
monitor (OPTIONAL) Enter the keyword monitor when the rule is describing the trac
that you want to monitor and the ACL in which you are creating the rule is applied
to the monitored interface.
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. By default, ow-based monitoring is
not enabled.
Command Modes ACCESS-LIST
Command History
Version Description
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000–ON.
9.5(0.1) Introduced on the Z9500.
9.4(0.0) Added support for ow-based monitoring on the S4810, S4820T, S6000, and
Z9000 platforms.
9.3.0.0 Added support for logging of ACLs on the S4810, S4820T, and Z9000 platforms.
Usage Information
When the congured maximum threshold is exceeded, generation of logs is stopped. When the interval at
which ACL logs are congured 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 congured threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the congured 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
Access Control Lists (ACL)
311