You can set only a single route tag per IS-IS route. However, setting a tag for an IS-IS route has no effect by itself. To use the route tag to apply administrative policies such as route redistribution, route summarization, or route leaking, you must reference the tag value in a route map by issuing the match tag command (in Route Map Configuration mode). The route map must also include one or more set commands that modify attributes of the routes matching the tag value. These routes can reside on a different router than the one on which you set the route tag.
For example, the following commands define a route map to modify the metric and metric type attributes of IS-IS routes configured with a route tag value of 221. The redistribute isis ip command, as described in Redistributing Routes Between Levels, applies this route map when redistributing the routes from level 1 into level 2.
- host1(config)#route-map map1 permit 5
- host1(config-route-map)#match tag 221
- host1(config-route-map)#set metric 10
- host1(config-route-map)#set metric-type external
- host1(config-route-map)#exit
- host1(config)#router isis engineering
- host1(config-router)#redistribute isis ip
level-1 into level-2 route-map map1
Alternatively, you can use a route map to set the tag for an IS-IS route by issuing the set tag command (in Route Map Configuration mode). For example, the following commands define a route map that sets route tag 33 for those IS-IS routes configured with an administrative distance of 25:
- host1(config)#route-map map2 permit 10
- host1(config-route-map)#match distance 25
- host1(config-route-map)#set tag 33
- host1(config-route-map)#exit
- host1(config)#router isis marketing
- host1(config-router)#table-map map2
The table-map command, described in Configuring Table Maps, applies this route map to the IS-IS routes before they are added to the routing table. For details about configuring and using route maps, see JUNOSe IP Services Configuration Guide .