match ip route-source




match ip route-source [access-list-number | access-list-name] [...access-list-number | ...access-list-name]
no match ip route-source
[access-list-number | access-list-name] [...access-list-number | ...access-list-name]


Syntax Description:

access-list-number | access-list-name Number or name of a standard or extended access list. It can be an integer from 1 to 199.


Command Description:

To redistribute routes that have been advertised by routers and access servers at the address specified by the access lists, use the match ip route-source command in route-map configuration mode. To remove the route-source entry, use the no form of this command.

An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the access-list-number or access-list-name argument.

Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.

The match route-map configuration command has multiple formats. The match commands can be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.

A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure second route map section with an explicit match specified.

There are situations in which the next hop and source router address of the route are not the same.


The following example distributes routes that have been advertised by routers and access servers at the addresses specified by access lists 5 and 80:

Router(config)# route-map name
Router(config)# match ip route-source 5 80



Related Commands:

match as-path
match community
match interface
match ip address
match ip next-hop
match metric
match route-type
match tag
set as-path
set automatic-tag
set community
set level
set local-preference
set metric BGP OSPF RIP
set metric-type
set next-hop
set tag
set weight

� Cisco Systems, Inc. 2001, 2002, 2003
World Wide Education

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)