Administrator Guide

Configuring Set Conditions
To configure a set condition, use the following commands.
• Generate a tag to be added to redistributed routes.
CONFIG-ROUTE-MAP mode
set automatic-tag
• Specify an OSPF area or ISIS level for redistributed routes.
CONFIG-ROUTE-MAP mode
set level {backbone | level-1 | level-1-2 | level-2 | stub-area}
• Specify a value for redistributed routes.
CONFIG-ROUTE-MAP mode
set metric {+ | - | metric-value}
• Specify an OSPF or ISIS type for redistributed routes.
CONFIG-ROUTE-MAP mode
set metric-type {external | internal | type-1 | type-2}
• Assign an IP address as the route’s next hop.
CONFIG-ROUTE-MAP mode
set next-hop ip-address
• Specify a tag for the redistributed routes.
CONFIG-ROUTE-MAP mode
set tag tag-value
To create route map instances, use these commands. There is no limit to the number of set commands per
route map, but the convention is to keep the number of set filters in a route map low. Set commands do not
require a corresponding
match command.
Configure a Route Map for Route
Redistribution
Route maps on their own cannot affect traffic and must be included in different commands to affect routing
traffic. To apply a route map to traffic, you must call or include that route map in a command such as the
redistribute or default-information originate commands in OSPF and BGP.
Route redistribution occurs when the system learns the advertising routes from static or directly connected
routes or another routing protocol. Different protocols assign different values to redistributed routes to
identify either the routes and their origins. The metric value is the most common attribute that is changed to
properly redistribute other routes into a routing protocol. Other attributes that can be changed include the
metric type (for example, external and internal route types in OSPF) and route tag. Use the redistribute
Access Control Lists (ACLs) 152