route-map

route-map

Defines a route map. Enters route-map configuration mode.

Syntax: [no] route map map-name [permit|deny][sequence-number]

map-name

Name of this route map. Multiple route maps may have the same map-name. Use the sequence number to differentiate between route maps with the same map-name.

permit

If the match criteria for this route-map are met, permit enables the route to be redistributed (as defined by the set actions). Routes are distributed only if the match permits the route.

If the match criteria are not met, the next instance of route map (with the same map-name) is tested. If the route does not match any of the criteria for any instance of the route map, it is not redistributed.

deny

If the match criteria for this route-map are met, deny prevents the route from being redistributed. This is true even if the match in any access list is a permit match.

sequence-number

Indicates the position this route map occupies in a list of route maps with the same map-name.

Description: Route maps are used to control and modify routing information that is exchanged between routing domains. Route maps consist of a list of match and set configuration commands. The match commands specify match criteria for incoming routes and the set commands specify the action taken if the match criteria are met.

Route maps are used to define the conditions for redistributing routes from one protocol to another, and within the BGP protocol (BGP peer to BGP peer).

Redistribution

Use route maps when you need fine control over how routes are advertised throughout the network. Use the route-map command in conjunction with the match and set commands to define the conditions for redistributing routes from one routing protocol to another and within the same routing protocol.

You can enter match commands into a route map in any order. If the match criteria are met, and permit is on, then the route is redistributed or controlled as defined by the set commands and route-map processing is complete.

If the match criteria are met, and deny is on, then the route is not redistributed or controlled and route-map processing is complete.

You can define multiple route maps with the same map-name. Maps with the same map-name are differentiated by a sequence-number. If a route passing through a route map controlling redistribution does not meet any of the match criteria, the route is passed through the next instance of the route map with the same map-name and next higher sequence number. Route processing continues until a match is made or the route is processed by all instances of the route map with no match. If the route is processed by all instances of a route map with no match, the route is not accepted (inbound route maps) or forwarded (outbound route maps).

Use the route-map command to define the name of the route-map and to specify permit or deny. This command changes the command mode to route-map configuration mode.

Use the set and match commands to define the conditions for enabling policy routing or redistribution.

Use the no route-map command to delete a route map. To delete a single instance of a route map from a list of route maps with the same map-name, use the sequence number with the no option to identify which instance of the map is deleted. Use the no option with no sequence number to delete all instances of a route map with the specified map-name.

Factory Default: No route maps configured.

Command Mode: Configuration.

Example 1: In the following example, the route-map, match ip address, and set weight commands create a route-map named setweight45 that filters route updates according to the criteria defined in access list 10 and sets the weight for routes that match to 45:

router(config)#route-map setweight45 permit 10

router(config-route-map)#match ip address 10

router(config-route-map)#set weight 45

router(config-route-map)#end

router(config)#

Example 2: In the following example, the route-map, match metric, and set metric commands create a route-map ospf-to-bgp:

router(config)#route-map ospf-to-bgp permit 10

router(config-route-map)#match metric 1

router(config-route-map)#set metric 5

router(config-route-map)#end

router(config)#

The redistribute command applies the route-map ospf-to-bgp to OSPF routes redistributed into BGP:

router(config)#router bgp 101

router(config-router)#redistribute ospf route-map ospf-to-bgp

OSPF routes with a metric of 1 are redistributed into BGP with a metric of 5.

Related Commands: show route-map
match as-path
match community
match ip address
match ip next-hop
match ip route-source
match metric
match route-type
match tag
set as-path
set community
set community
set ip next-hop
set level
set local-preference
set metric
set metric-type
set origin
set tag
set weight

map-name	Name of this route map. Multiple route maps may have the same map-name. Use the sequence number to differentiate between route maps with the same map-name.
permit	If the match criteria for this route-map are met, permit enables the route to be redistributed (as defined by the set actions). Routes are distributed only if the match permits the route. If the match criteria are not met, the next instance of route map (with the same map-name) is tested. If the route does not match any of the criteria for any instance of the route map, it is not redistributed.
deny	If the match criteria for this route-map are met, deny prevents the route from being redistributed. This is true even if the match in any access list is a permit match.
sequence-number	Indicates the position this route map occupies in a list of route maps with the same map-name.

router(config)#route-map setweight45 permit 10 router(config-route-map)#match ip address 10 router(config-route-map)#set weight 45 router(config-route-map)#end router(config)#

router(config)#route-map ospf-to-bgp permit 10 router(config-route-map)#match metric 1 router(config-route-map)#set metric 5 router(config-route-map)#end router(config)#

router(config)#router bgp 101 router(config-router)#redistribute ospf route-map ospf-to-bgp

   Source File Name: Routing_Pol.fm
    HTML File Name: Routing_Pol30.html
    Last Updated: 05/10/04 at 16:38:37

route-map

Redistribution

Please email suggestions and comments to: doc@avici.com