Reference Guide

• Enter an IPv6 address in A::B format of the next-hop for a BGP route update in ROUTE-MAP mode.
set ipv6 next-hop address
• Enter the range value for the BGP route’s LOCAL_PREF attribute in ROUTE-MAP mode (0 to 4294967295).
set local-preference range-value
• Enter a metric value for redistributed routes in ROUTE-MAP mode (0 to 4294967295).
set metric {+ | - | metric-value}
• Enter an OSPF type for redistributed routes in ROUTE-MAP mode.
set metric-type {type-1 | type-2 | external | internal}
• 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 (0 to 4294967295).
set tag tag-value
• Enter a value as the route’s weight in ROUTE-MAP mode (0 to 65535).
set weight value
• Save the conguration.
do commit
Check set conditions
OS10(config)# route-map ip permit 1
OS10(conf-route-map)# match metric 2567
OS10(conf-route-map)# do commit
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 (by traditional mirroring methods). This feature is available for L2 and L3 ingress trac, and can be specied using ACL rules.
This mechanism 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 port that is being monitored, the packet validates against the congured ACL rules. If the packet matches an
ACL rule, the system examines the corresponding ow processor to perform 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.
Port-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. This can also be referred to as policy-based mirroring.
Access Control Lists
385