Reference Guide

• Enter an ORIGIN attribute in ROUTE-MAP mode.
set origin {egp | igp | incomplete}
• Enter a tag value for the redistributed routes in ROUTE-MAP mode, from 0 to 4294967295.
set tag tag-value
• Enter a value as the route’s weight in ROUTE-MAP mode, from 0 to 65535.
set weight value
Check set conditions
OS10(config)# route-map ip permit 1
OS10(conf-route-map)# match metric 2567
continue Clause
Only BGP route-maps support the continue clause. When a match is found, set clauses run and the packet is forwarded — no route-
map processing occurs. If you congure the continue clause without conguring a module, the next sequential module processes.
If you congure the continue command at the end of a module, the next module processes even after a match is found. The example
shows a continue clause at the end of a route-map module — if a match is found in the route-map test module 10, module 30 processes.
Route-map continue clause
OS10(config)# route-map test permit 10
OS10(conf-route-map)# continue 30
ACL ow-based monitoring
Flow-based monitoring conserves bandwidth by selecting only the required ow to be mirrored instead of mirroring entire packets from an
interface. This feature is available for L2 and L3 ingress trac. Specify ow-based monitoring using ACL rules. Flow-based monitoring
copies incoming packets that match 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).
When a packet arrives at a monitored port, the packet validates against the congured ACL rules. If the packet matches an ACL rule, the
system examines the corresponding ow processor and performs the action specied for that port. If the mirroring action is set in the ow
processor entry, the port details are sent to the destination port.
Flow-based mirroring
Flow-based mirroring is a mirroring session in which trac matches specied policies that are mirrored to a destination port. Port-based
mirroring maintains a database that contains all monitoring sessions, including port monitor sessions. The database has information
regarding the sessions that are enabled or not enabled for ow-based monitoring. Flow-based mirroring is also known as policy-based
mirroring.
To activate ow-based mirroring, use the flow-based enable command. Trac with particular ows that are traversing through the
ingress interfaces are examined. Appropriate ACL rules apply in the ingress direction. By default, ow-based mirroring is not enabled.
To enable the evaluation and replication of trac traversing to the destination port, congure the monitor option with the permit, deny,
or
seq commands for ACLs assigned to the source or the monitored port (MD). Enter the keywords capture session session-id
with the seq, permit, or deny command for the ACL rules to allow or drop IPv4, IPv6, ARP, UDP, EtherType, ICMP, and TCP packets.
IPV4-ACL mode
seq sequence-number {deny | permit} {source [mask] | any | host ip-address} [count [byte]]
[fragments] [threshold-in-msgs count] [capture session session-id]
414
Access Control Lists