Users Guide

ip access-list extended test
remark 2 XYZ
remark 4 this remark corresponds to permit any host 1.1.1.1
seq 4 permit ip any host 1.1.1.1
remark 6 this remark has no corresponding rule
remark 8 this remark corresponds to permit ip any host 1.1.1.2
seq 8 permit ip any host 1.1.1.2
seq 10 permit ip any host 1.1.1.3
seq 12 permit ip any host 1.1.1.4
Route Maps
Although route maps are similar to ACLs and prefix lists in that they consist of a series of commands that
contain a matching criterion and an action, route maps can modify parameters in matching packets.
Implementation Information
ACLs and prefix lists can only drop or forward the packet or traffic. Route maps process routes for route
redistribution. For example, a route map can be called to filter only specific routes and to add a metric.
Route maps also have an “implicit deny.” Unlike ACLs and prefix lists; however, where the packet or traffic is
dropped, in route maps, if a route does not match any of the route map conditions, the route is not
redistributed.
The implementation of route maps allows route maps with the no match or no set commands. When there is
no match command, all traffic matches the route map and the set command applies.
Flow-Based Monitoring Support for
ACLs
Flow-based monitoring conserves bandwidth by monitoring only the specified traffic instead of all traffic on
the interface. It is available for Layer 2 and Layer 3 ingress traffic. You can specify traffic using standard or
extended access-lists. This mechanism copies incoming packets that matches the ACL rules applied on the
ingress port and forwards (mirrors) them to another port. The source port is the monitored port (MD) and the
destination port is the monitoring port (MG).
The port mirroring application maintains and performs all the monitoring operations on the chassis. ACL
information is sent to the ACL manager, which in turn notifies the ACL agent to add entries in the CAM area.
Duplicate entries in the ACL are not saved.
When a packet arrives at a port that is being monitored, the packet is validated against the configured ACL
rules. If the packet matches an ACL rule, the system examines the corresponding flow processor to perform
the action specified for that port. If the mirroring action is set in the flow processor entry, the destination port
details, to which the mirrored information must be sent, are sent to the destination port.
Access Control Lists (ACLs) 135