Administrator Guide

redistribute ospf 34 metric 1 route-map torip
!
route-map torip permit 10
match route-type internal
set tag 34
!
Continue Clause
Normally, when a match is found, set clauses are executed, and the packet is then forwarded; no more
route-map modules are processed.
If you configure the continue command at the end of a module, the next module (or a specified
module) is processed even after a match is found. The following example shows a continue clause at the
end of a route-map module. In this example, if a match is found in the route-map “test” module 10,
module 30 is processed.
NOTE: If you configure the continue clause without specifying a module, the next sequential
module is processed.
Example of Using the continue Clause in a Route Map
!
route-map test permit 10
match commu comm-list1
set community 1:1 1:2 1:3
set as-path prepend 1 2 3 4 5
continue 30!
Logging of ACL Processes
This functionality is supported on the Z9000 platform.
To assist in the administration and management of traffic that traverses the device after being validated
by the configured ACLs, you can enable the generation of logs for access control list (ACL) processes.
Although you can configure ACLs with the required permit or deny filters to provide access to the
incoming packet or disallow access to a particular user, it is also necessary to monitor and examine the
traffic that passes through the device. To evaluate network traffic that is subjected to ACLs, configure the
logs to be triggered for ACL operations. This functionality is primarily needed for network supervision and
maintenance activities of the handled subscriber traffic.
When ACL logging is configured, and a frame reaches an ACL-enabled interface and matches the ACL, a
log is generated to indicate that the ACL entry matched the packet.
When you enable ACL log messages, at times, depending on the volume of traffic, it is possible that a
large number of logs might be generated that can impact the system performance and efficiency. To
avoid an overload of ACL logs from being recorded, you can configure the rate-limiting functionality.
Specify the interval or frequency at which ACL logs must be triggered and also the threshold or limit for
the maximum number of logs to be generated. If you do not specify the frequency at which ACL logs
must be generated, a default interval of 5 minutes is used. Similarly, if you do not specify the threshold for
ACL logs, a default threshold of 10 is used, where this value refers to the number of packets that are
matched against an ACL .
A Layer 2 or Layer 3 ACL contains a set of defined rules that are saved as flow processor (FP) entries.
When you enable ACL logging for a particular ACL rule, a set of specific ACL rules translate to a set of FP
122
Access Control Lists (ACLs)