- Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols, Release 12.2
Feedback
Table Of Contents
set ip default next-hop verify-availability
set ip next-hop verify-availability
redistribute (IP)
To redistribute routes from one routing domain into another routing domain, use the redistribute command in router configuration mode. To disable redistribution, use the no form of this command.
redistribute protocol [process-id] {level-1 | level-1-2 | level-2} [as-number] [metric {metric-value | transparent}] [metric-type type-value] [match {internal | external 1 | external 2}]
[tag tag-value] [route-map map-tag] [subnets]no redistribute protocol [process-id] {level-1 | level-1-2 | level-2} [as-number] [metric {metric-value | transparent}] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [subnets]
Syntax Description
Command Default
Route redistribution is disabled.
protocol: No source protocol is defined.
process-id: No process ID is defined.
metric metric-value: 0
metric-type type-value: Type 2 external route
match internal | external: Internal, external 1, external 2
external: Internal
tag tag-value: If no value is specified, the remote autonomous system number is used for routes from BGP and EGP; for other protocols, the default is 0.
route-map map-tag: If the route-map keyword is not entered, all routes are redistributed; if no map-tag value is entered, no routes are imported.
subnets: No subnets are defined.Command Modes
Router configuration
Address family configurationCommand History
Usage Guidelines
Changing or disabling any keyword will not affect the state of other keywords.
A router receiving a link-state protocol with an internal metric will consider the cost of the route from itself to the redistributing router plus the advertised cost to reach the destination. An external metric only considers the advertised metric to reach the destination.
Routes learned from IP routing protocols can be redistributed at Level 1 into an attached area or at Level 2. The level-1-2 keyword allows both Level 1 and Level 2 routes in a single command.
Redistributed routing information must be filtered by the distribute-list out router configuration command. This guideline ensures that only those routes intended by the administrator are passed along to the receiving routing protocol.
Whenever you use the redistribute or the default-information router configuration commands to redistribute routes into an OSPF routing domain, the router automatically becomes an ASBR. However, an ASBR does not, by default, generate a default route into the OSPF routing domain.
When routes are redistributed into OSPF from protocols other than OSPF or BGP, and no metric has been specified with the metric-type keyword and type-value argument, OSPF will use 20 as the default metric. When routes are redistributed into OSPF from BGP, OSPF will use 1 as the default metric. When routes are redistributed from one OSPF process to another OSPF process, Autonomous system (AS) external and not-so-stubby-area (NSSA) routes will use 20 as the default metric. When intra-area and inter-area routes are redistributed between OSPF processes, the internal OSPF metric from the redistribution source process is advertised as the external metric in the redistribution destination process. (This is the only case in which the routing table metric will be preserved when routes are redistributed into OSPF.)
When routes are redistributed into OSPF, only routes that are not subnetted are redistributed if the subnets keyword is not specified.
Routes configured with the connected keyword affected by this redistribute command are the routes not specified by the network router configuration command.
You cannot use the default-metric command to affect the metric used to advertise connected routes.
Note
The metric value specified in the redistribute command supersedes the metric value specified using the default-metric command.
Default redistribution of IGPs or EGP into BGP is not allowed unless the default-information originate router configuration command is specified.
Examples
The following example shows how OSPF routes are redistributed into a BGP domain:
router bgp 109redistribute ospfThe following example causes Enhanced Interior Gateway Routing Protocol (EIGRP) routes to be redistributed into an OSPF domain:
router ospf 110redistribute eigrpThe following example causes the specified EIGRP process routes to be redistributed into an OSPF domain. The EIGRP-derived metric will be remapped to 100 and RIP routes to 200.
router ospf 109redistribute eigrp 108 metric 100 subnetsredistribute rip metric 200 subnetsThe following example configures BGP routes to be redistributed into IS-IS. The link-state cost is specified as 5, and the metric type will be set to external, indicating that it has lower priority than internal metrics.
router isisredistribute bgp 120 metric 5 metric-type externalIn the following example, network 172.16.0.0 will appear as an external link-state advertisement (LSA) in OSPF 1 with a cost of 100 (the cost is preserved):
interface ethernet 0ip address 172.16.0.1 255.0.0.0ip ospf cost 100interface ethernet 1ip address 10.0.0.1 255.0.0.0!router ospf 1network 10.0.0.0 0.255.255.255 area 0redistribute ospf 2 subnetrouter ospf 2network 172.16.0.0 0.255.255.255 area 0Related Commands
route-map (IP)
To define the conditions for redistributing routes from one routing protocol into another, or to enable policy routing, use the route-map command in global configuration mode and the match and set command in route-map configuration modes. To delete an entry, use the no form of this command.
route-map map-tag [permit | deny] [sequence-number]
no route-map map-tag [permit | deny] [sequence-number]
Syntax Description
Defaults
No default is available.
Command Modes
Global configuration
Command History
Usage Guidelines
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
Redistribution
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.
Use route maps when you want detailed control over how routes are redistributed between routing processes. The destination routing protocol is the one you specify with the router global configuration command. The source routing protocol is the one you specify with the redistribute router configuration command. See the "Examples" section for an illustration of how route maps are configured.
When you are passing routes through a route map, 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 a second route map section with an explicit match specified.
Policy Routing
Another purpose of route maps is to enable policy routing. Use the ip policy route-map command, in addition to the route-map command, and the match and set commands to define the conditions for policy routing packets. The match commands specify the conditions under which policy routing occurs. The set commands specify the routing actions to perform if the criteria enforced by the match commands are met. You might want to policy route packets some way other than the obvious shortest path.
The sequence-number argument works as follows:
1.
2.
3.
If the no route-map map-tag command is specified (with no sequence-number argument), the whole route map is deleted.
Examples
The following example redistributes Routing Information Protocol (RIP) routes with a hop count equal to 1 into Open Shortest Path First (OSPF). These routes will be redistributed into OSPF as external link-state advertisements (LSAs) with a metric of 5, metric type of Type 1, and a tag equal to 1.
router ospf 109redistribute rip route-map rip-to-ospfroute-map rip-to-ospf permitmatch metric 1set metric 5set metric-type type1set tag 1Related Commands
send-lifetime
To set the time period during which an authentication key on a key chain is valid to be sent, use the send-lifetime key chain key configuration command. To revert to the default value, use the no form of this command.
send-lifetime start-time {infinite | end-time | duration seconds}
no send-lifetime [start-time {infinite | end-time | duration seconds}]
Syntax Description
Defaults
Forever (the starting time is January 1, 1993, and the ending time is infinite)
Command Modes
Key chain key configuration
Command History
Usage Guidelines
Specify a start-time value and one of the following values: infinite, end-time, or duration seconds.
We recommend running Network Time Protocol (NTP) or some other time synchronization method if you intend to set lifetimes on keys.
If the last key expires, authentication will continue and an error message will be generated. To disable authentication, you must manually delete the last valid key.
Examples
The following example configures a key chain called trees. The key named chestnut will be accepted from 1:30 p.m. to 3:30 p.m. and be sent from 2:00 p.m. to 3:00 p.m. The key named birch will be accepted from 2:30 p.m. to 4:30 p.m. and be sent from 3:00 p.m. to 4:00 p.m. The overlap allows for migration of keys or discrepancies in the set time of the router. There is a 30-minute leeway on each side to handle time differences.
interface ethernet 0ip rip authentication key-chain treesip rip authentication mode md5!router ripnetwork 172.19.0.0version 2!key chain treeskey 1key-string chestnutaccept-lifetime 13:30:00 Jan 25 1996 duration 7200send-lifetime 14:00:00 Jan 25 1996 duration 3600key 2key-string birchaccept-lifetime 14:30:00 Jan 25 1996 duration 7200send-lifetime 15:00:00 Jan 25 1996 duration 3600Related Commands
set automatic-tag
To automatically compute the tag value, use the set automatic-tag command in route-map configuration mode. To disable this function, use the no form of this command.
set automatic-tag
no set automatic-tag
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example configures the Cisco IOS software to automatically compute the tag value for the Border Gateway Protocol (BGP) learned routes:
route-map tagmatch as path 10set automatic-tag!router bgp 100table-map tagRelated Commands
set default interface
To indicate where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination, use the set default interface command in route-map configuration mode. To delete an entry, use the no form of this command.
set default interface interface-type interface-number [...interface-type interface-number]
no set default interface interface-type interface-number [...interface-type interface-number]
Syntax Description
interface-type
Interface type, used with the interface number, to which packets are output.
interface-number
Interface number, used with the interface type, to which packets are output.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the interface-type interface-number arguments.
Use this command to provide certain users a different default route. If the Cisco IOS software has no explicit route for the destination, then it routes the packet to this interface. The first interface specified with the set default interface command that is up is used. The optionally specified interfaces are tried in turn.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. 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 policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
3.
4.
Examples
In the following example, packets that have a Level 3 length of 3 to 50 bytes and for which the software has no explicit route to the destination are output to Ethernet interface 0:
interface serial 0ip policy route-map brighton!route-map brightonmatch length 3 50set default interface ethernet 0Related Commands
set interface
To indicate where to output packets that pass a match clause of a route map for policy routing, use the set interface command in route-map configuration mode. To delete an entry, use the no form of this command.
set interface interface-type interface-number [...interface-type interface-number]
no set interface interface-type interface-number [...interface-type interface-number]
Syntax Description
interface-type
Interface type, used with the interface number, to which packets are output.
interface-number
Interface number, used with the interface type, to which packets are output.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the interface-type interface-number arguments.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. 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 policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met.
If the first interface specified with the set interface command is down, the optionally specified interfaces are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
3.
4.
A useful next hop implies an interface. As soon as a next hop and an interface are found, the packet is routed.
Specifying the set interface null 0 command is a way to write a policy that the packet be dropped and an "unreachable" message be generated.
Note
Examples
In the following example, packets with a Level 3 length of 3 to 50 bytes are output to Ethernet interface 0:
interface serial 0ip policy route-map testing!route-map testingmatch length 3 50set interface ethernet 0Related Commands
set ip default next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination, use the set ip default next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set ip default next-hop ip-address [...ip-address]
no set ip default next-hop ip-address [...ip-address]
Syntax Description
ip-address
IP address of the next hop to which packets are output.The next hop must be an adjacent router.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, then it routes the packet to this next hop. The first next hop specified with the set ip default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. 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 policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
3.
4.
Note
Examples
The following example provides two sources with equal access to two different service providers. Packets arriving on asynchronous interface 1 from the source 10.1.1.1 are sent to the router at 172.16.6.6 if the software has no explicit route for the destination of the packet. Packets arriving from the source 10.2.2.2 are sent to the router at 172.17.7.7 if the software has no explicit route for the destination of the packet. All other packets for which the software has no explicit route to the destination are discarded.
access-list 1 permit ip 10.1.1.1 0.0.0.0access-list 2 permit ip 10.2.2.2 0.0.0.0!interface async 1ip policy route-map equal-access!route-map equal-access permit 10match ip address 1set ip default next-hop 172.16.6.6route-map equal-access permit 20match ip address 2set ip default next-hop 172.17.7.7route-map equal-access permit 30set default interface null0Related Commands
set ip default next-hop verify-availability
To configure a router, for policy routing, to check the CDP database for the availability of an entry for the default next hop that is specified by the set ip default next-hop command, use the set ip default next-hop verify-availability route map configuration command. To disable this function, use the no form of this command.
set ip default next-hop verify-availability
no set ip default next-hop verify-availability
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
Use this command to force the configured policy routing to check the CDP database to determine if an entry is available for the next hop that is specified by the set ip default next-hop command. This command is used to prevent traffic from being "black holed" if the configured next hop becomes unavailable.
Examples
The following example :
Router(config-route-map)# set ip default next-hop verify-availabilityRelated Commands
set ip next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing, use the set ip next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set ip next-hop ip-address [...ip-address]
no set ip next-hop ip-address [...ip-address]
Syntax Description
ip-address
IP address of the next hop to which packets are output. The next hop must be an adjacent router.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. 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 policy routing occurs. The set commands specify the set actions—the particular routing actions to perform if the criteria enforced by the match commands are met.
If the interface associated with the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
1.
2.
3.
4.
Note
Examples
In the following example, packets with a Level 3 length of 3 to 50 bytes are output to the router at IP address 10.14.2.2:
interface serial 0ip policy route-map thataway!route-map thatawaymatch length 3 50set ip next-hop 10.14.2.2Related Commands
set ip next-hop verify-availability
To configure policy routing to verify if the next hops of a route map are Cisco Discovery Protocol (CDP) neighbors before policy routing to those next hops, use the set ip next-hop verify-availability command in route-map configuration mode.
set ip next-hop verify-availability
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
One example of when you might configure this command is if you have some traffic traveling via a satellite to a next hop. It might be prudent to verify that the next hop is reachable before trying to policy route to it.
This command has the following restrictions:
•
•
•
•
If the router is policy routing packets to the next hop and the next hop happens to be down, the router will try unsuccessfully to use Address Resolution Protocol (ARP) for the next hop (which is down). This behavior will continue forever.
To prevent this situation, use this command to configure the router to first verify that the next hops of the route map are the CDP neighbors of the router before routing to those next hops.
This command is optional because some media or encapsulations do not support CDP, or it may not be a Cisco device that is sending the router traffic.
If this command is set and the next hop is not a CDP neighbor, the router looks to the subsequent next hop, if there is one. If there is none, the packets simply are not policy routed.
If this command is not set, the packets are either successfully policy routed or remain forever unrouted.
If you want to selectively verify availability of only some next hops, you can configure different route map entries (under the same route map name) with different criteria (using access list matching or packet size matching), and use the set ip next-hop verify-availability command selectively.
Examples
The following example configures Policy Routing with CEF. Policy routing is configured to verify that next hop 50.0.0.8 of the route map named test is a CDP neighbor before the router tries to policy route to it.
If the first packet is being policy routed via route map test sequence 10, the subsequent packets of the same flow always take the same route map test sequence 10, not route map test sequence 20, because they all match or pass the access list 1 check.
ip cefinterface ethernet0/0/1ip route-cache flowip policy route-map testroute-map test permit 10match ip address 1set ip precedence priorityset ip next-hop 50.0.0.8set ip next-hop verify-availabilityroute-map test permit 20Related Commands
Displays counts of the one-way route map IPC messages sent from the RP to the VIP when NetFlow policy routing is configured.
set ip precedence
To set the precedence value in the IP header, use the set ip precedence command in route-map configuration mode. To instruct the router to leave the precedence value alone, use the no form of this command.
set ip precedence number | name
no set ip precedence
Syntax Description
Defaults
This command has no default behavior.
Command Modes
Route-map configuration
Command History
Usage Guidelines
You can set the precedence using either a number or the corresponding name.
Note
The way the network gives priority (or some type of expedited handling) to the marked traffic is through the application of WFQ or weighted random early detection (WRED) at points downstream in the network. Typically, you would set IP precedence at the edge of the network (or administrative domain) and have queueing act on it thereafter. WFQ can speed up handling for high precedence traffic at congestion points. WRED ensures that high precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. The customer can define the meaning of a precedence value by enabling other features that use the value. In the case of Cisco high-end Internet quality of service (QoS), IP precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network. For example, IP Precedence 2 can be given 90 percent of the bandwidth on output links in the network, and IP Precedence 6 can be given 5 percent using the distributed weight fair queueing (DWFQ) implementation on the Versatile Interface Processors (VIPs).
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. 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 or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the IP Precedence value to 5 (critical) for packets that pass the route map match:
interface serial 0ip policy route-map texas!route-map texasmatch length 68 128set ip precedence 5Related Commands
set level (IP)
To indicate where to import routes, use the set level command in route-map configuration mode. To delete an entry, use the no form of this command.
set level {level-1 | level-2 | level-1-2 | stub-area | backbone}
no set level {level-1 | level-2 | level-1-2 | stub-area | backbone}
Syntax Description
Defaults
This command is disabled by default.
For Intermediate System-to-Intermediate System (IS-IS) destinations, the default value is level-2. For OSPF destinations, the default value is backbone.
Command Modes
Route-map configuration
Command History
Usage Guidelines
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
In the following example, routes will be imported into the Level 1 area:
route-map nameset level level-lRelated Commands
set local-preference
To specify a preference value for the autonomous system path, use the set local-preference command in route-map configuration mode. To delete an entry, use the no form of this command.
set local-preference number-value
no set local-preference number-value
Syntax Description
Defaults
Preference value of 100
Command Modes
Route-map configuration
Command History
Usage Guidelines
The preference is sent only to all routers in the local autonomous system.
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
You can change the default preference value with the bgp default local-preference command.
Examples
The following example sets the local preference to 100 for all routes that are included in access list 1:
route-map map-preferencematch as-path 1set local-preference 100Related Commands
set metric (BGP, OSPF, RIP)
To set the metric value for a routing protocol, use the set metric command in route-map configuration mode. To return to the default metric value, use the no form of this command.
set metric metric-value
no set metric metric-value
Syntax Description
Defaults
The dynamically learned metric value.
Command Modes
Route-map configuration
Command History
Usage Guidelines
We recommend that you consult your Cisco technical support representative before changing the default value.
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the metric value for the routing protocol to 100:
route-map set-metricset metric 100Related Commands
set metric-type
To set the metric type for the destination routing protocol, use the set metric-type command in route-map configuration mode. To return to the default, use the no form of this command.
set metric-type {internal | external | type-1 | type-2}
no set metric-type {internal | external | type-1 | type-2}
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
Use the route-map global configuration command with 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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Note
Examples
The following example sets the metric type of the destination protocol to OSPF external Type 1:
route-map map-typeset metric-type type-1Related Commands
set next-hop
To specify the address of the next hop, use the set next-hop command in route-map configuration mode. To delete an entry, use the no form of this command.
set next-hop next-hop
no set next-hop next-hop
Syntax Description
Defaults
Default next hop address.
Command Modes
Route-map configuration
Command History
Usage Guidelines
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of the router are met. When all match criteria are met, all set actions are performed.
Examples
In the following example, routes that pass the access list have the next hop set to 172.160.70.24:
route-map map_hopmatch address 5set next-hop 172.160.70.24Related Commands
set tag (IP)
To set a tag value of the destination routing protocol, use the set tag command in route-map configuration mode. To delete the entry, use the no form of this command.
set tag tag-value
no set tag tag-value
Syntax Description
Defaults
If not specified, the default action is to forward the tag in the source routing protocol onto the new destination protocol.
Command Modes
Route-map configuration
Command History
Usage Guidelines
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 set route-map configuration commands specify the redistribution set actions to be performed when all the match criteria of a route map are met. When all match criteria are met, all set actions are performed.
Examples
The following example sets the tag value of the destination routing protocol to 5:
route-map tagset tag 5Related Commands
show ip cache policy
To display the cache entries in the policy route cache, use the show ip cache policy command in EXEC mode.
show ip cache policy
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip cache policy command:
Router# show ip cache policyTotal adds 10, total deletes 10Type Routemap/sequence Age Interface Next HopNH george/10 00:04:31 Ethernet0 172.110.1.2Int george/30 00:01:23 Serial4 172.110.5.129Table 52 describes the significant fields shown in the display.
Related Commands
ip route-cache
Configures the router to export the flow cache entry to a workstation when a flow expires.
show ip local policy
To display the route map used for local policy routing, if any, use the show ip local policy command in EXEC mode.
show ip local policy
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip local policy command:
Router# show ip local policyLocal policy routing is enabled, using route map equalroute-map equal, permit, sequence 10Match clauses:length 150 200Set clauses:ip next-hop 10.10.11.254Policy routing matches: 0 packets, 0 bytesroute-map equal, permit, sequence 20Match clauses:ip address (access-lists): 101Set clauses:ip next-hop 10.10.11.14Policy routing matches: 2 packets, 172 bytesTable 53 describes the significant fields shown in the display.
Related Commands
show ip policy
To display the route map used for policy routing, use the show ip policy command in EXEC mode.
show ip policy
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip policy command:
Router# show ip policyInterface Route maplocal equalEthernet0 equalThe following is sample output from the show route-map command, which relates to the preceding sample display:
Router# show route-maproute-map equal, permit, sequence 10Match clauses:length 150 200Set clauses:ip next-hop 10.10.11.254Policy routing matches: 0 packets, 0 bytesroute-map equal, permit, sequence 20Match clauses:ip address (access-lists): 101Set clauses:ip next-hop 10.10.11.14Policy routing matches: 144 packets, 15190 bytesTable 54 describes the significant fields shown in the display.
Related Commands
show ip protocols
To display the parameters and current state of the active routing protocol process, use the show ip protocols command in EXEC mode.
show ip protocols
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The information displayed by the show ip protocols command is useful in debugging routing operations. Information in the Routing Information Sources field of the show ip protocols output can help you identify a router suspected of delivering bad routing information.
Examples
The following is sample output from the show ip protocols command, showing Interior Gateway Routing Protocol (IGRP) processes:
Router# show ip protocolsRouting Protocol is "igrp 109"Sending updates every 90 seconds, next due in 44 secondsInvalid after 270 seconds, hold down 280, flushed after 630Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setDefault networks flagged in outgoing updatesDefault networks accepted from incoming updatesIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0IGRP maximum hopcount 100IGRP maximum metric variance 1Redistributing: igrp 109Routing for Networks:172.160.72.0Routing Information Sources:Gateway Distance Last Update172.160.72.18 100 0:56:41172.160.72.19 100 6d19172.160.72.22 100 0:55:41172.160.72.20 100 0:01:04172.160.72.30 100 0:01:29Distance: (default is 100)Routing Protocol is "bgp 1878"Sending updates every 60 seconds, next due in 0 secondsOutgoing update filter list for all interfaces is 1Incoming update filter list for all interfaces is not setRedistributing: igrp 109IGP synchronization is disabledAutomatic route summarization is enabledNeighbor(s):Address FiltIn FiltOut DistIn DistOut Weight RouteMap192.108.211.17 1192.108.213.89 1198.6.255.13 1172.160.72.18 1172.160.72.19172.160.84.17 1Routing for Networks:192.108.209.0192.108.211.0198.6.254.0Routing Information Sources:Gateway Distance Last Update172.160.72.19 20 0:05:28Distance: external 20 internal 200 local 200Table 55 describes the significant fields shown in the display.
The following is sample output from the show ip protocols command, showing EIGRP process 77:
Router# show ip protocolsRouting Protocol is "eigrp 77"Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setRedistributing: eigrp 77Automatic network summarization is in effectRouting for Networks:172.180.0.0Routing Information Sources:Gateway Distance Last Update172.180.81.28 90 0:02:36172.180.80.28 90 0:03:04172.180.80.31 90 0:03:04Distance: internal 90 external 170Table 56 describes the significant fields shown in the display.
The following is sample output from the show ip protocols command, showing Intermediate System-to-Intermediate System (IS-IS) processes:
Router# show ip protocolsRouting Protocol is "isis"Sending updates every 0 secondsInvalid after 0 seconds, hold down 0, flushed after 0Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setRedistributing: isisAddress Summarization:NoneRouting for Networks:Serial0Routing Information Sources:Distance: (default is 115)The following is sample output from the show ip protocols command, showing Routing Information Protocol (RIP) processes:
Router# show ip protocolsRouting Protocol is "rip"Sending updates every 30 seconds, next due in 2 secondsInvalid after 180 seconds, hold down 180, flushed after 240Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setRedistributing: ripDefault version control: send version 2, receive version 2Interface Send Recv Key-chainEthernet0 2 2 treesFddi0 2 2Routing for Networks:172.19.0.02.0.0.010.3.0.0Routing Information Sources:Gateway Distance Last UpdateDistance: (default is 120)show ip route
To display the current state of the routing table, use the show ip route command in EXEC mode.
show ip route [[ip-address [mask] [longer-prefixes]] | [protocol [process-id]] | [list access-list-number | access-list-name]]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip route command when entered without an address:
Router# show ip routeCodes: I - IGRP derived, R - RIP derived, O - OSPF derived,C - connected, S - static, E - EGP derived, B - BGP derived,* - candidate default route, IA - OSPF inter area route,i - IS-IS derived, ia - IS-IS, U - per-user static route,o - on-demand routing, M - mobile, P - periodic downloaded static route,D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,N2 - OSPF NSSA external type 2 routeGateway of last resort is 10.119.254.240 to network 10.140.0.0O E2 172.150.0.0 [160/5] via 10.119.254.6, 0:01:00, Ethernet2E 172.17.10.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2O E2 172.70.132.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2O E2 10.130.0.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2E 172.30.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2E 10.129.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2E 172.80.129.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2E 10.10.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2E 172.60.139.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2E 172.90.208.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2E 192.84.148.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2E 192.168.223.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2E 192.44.236.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2E 10.141.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2E 141.140.0.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2The following is sample output that includes IS-IS Level 2 routes learned:
Router# show ip routeCodes: I - IGRP derived, R - RIP derived, O - OSPF derived,C - connected, S - static, E - EGP derived, B - BGP derived,* - candidate default route, IA - OSPF inter area route,i - IS-IS derived, ia - IS-IS, U - per-user static route,o - on-demand routing, M - mobile, P - periodic downloaded static route,D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,N2 - OSPF NSSA external type 2 routeGateway of last resort is not set172.180.0.0 is subnetted (mask is 255.255.255.0), 3 subnetsC 172.180.64.0 255.255.255.0 is possibly down,routing via 0.0.0.0, Ethernet0i L2 172.180.67.0 [115/20] via 172.180.64.240, 0:00:12, Ethernet0i L2 172.180.66.0 [115/20] via 172.180.64.240, 0:00:12, Ethernet0Table 57 describes the significant fields shown in the displays.
When you specify that you want information about a specific network displayed, more detailed statistics are shown. The following is sample output from the show ip route command when entered with the address 10.119.0.0:
Router# show ip route 10.119.0.0Routing entry for 10.119.0.0 (mask 255.255.0.0)Known via "igrp 109", distance 100, metric 10989Tag 0Redistributing via igrp 109Last update from 10.108.35.13 on TokenRing0, 0:00:58 agoRouting Descriptor Blocks:* 10.108.35.13, from 10.108.35.13, 0:00:58 ago, via TokenRing0Route metric is 10989, traffic share count is 1Total delay is 45130 microseconds, minimum bandwidth is 1544 KbitReliability 255/255, minimum MTU 1500 bytesLoading 2/255, Hops 4When an IS-IS router advertises its link-state information, it includes one of its own IP addresses to be used as the originator IP address. When other routers calculate IP routes, they can store the originator IP address with each route in the routing table.
The following example shows the output from the show ip route command when looking at an IP route generated by IS-IS. Each path that is shown under the Routing Descriptor Blocks report displays two IP addresses. The first address (10.22.22.2) is the next hop address, the second is the originator IP address from the advertising IS-IS router. This address helps you determine where a particular IP route has originated in your network. In the example the route to 10.0.0.1/32 was originated by a router with IP address 223.191.255.247.
Router# show ip route 10.0.0.1Routing entry for 10.0.0.1/32Known via "isis", distance 115, metric 20, type level-1Redistributing via isisLast update from 223.191.255.251 on Fddi1/0, 00:00:13 agoRouting Descriptor Blocks:* 10.22.22.2, from 223.191.255.247, via Serial2/3Route metric is 20, traffic share count is 1223.191.255.251, from 223.191.255.247, via Fddi1/0Route metric is 20, traffic share count is 1Compare the report using the show ip route command with an IP address to the following report using the show ip route isis command:
Router# show ip route isis10.0.0.0/8 is variably subnetted, 2 subnets, 2 masksi L1 10.0.0.1/32 [115/20] via 10.22.22.2, Serial2/3[115/20] via 223.191.255.251, Fddi1/022.0.0.0/24 is subnetted, 2 subnetsi L1 22.22.23.0 [115/20] via 223.191.255.252, Fddi1/0Table 58 describes the significant fields shown when using the show ip route command with an IP address (previous displays).
The following is sample output using the longer-prefixes keyword. When the longer-prefixes keyword is included, the address and mask pair becomes the prefix, and any address that matches that prefix is displayed. Therefore, multiple addresses are displayed.
In the following example, the logical AND operation is performed on the source address 128.0.0.0 and the mask 128.0.0.0, resulting in 128.0.0.0. Each destination in the routing table is also logically ANDed with the mask and compared to that result of 128.0.0.0. Any destinations that fall into that range are displayed in the output.
Router# show ip route 128.0.0.0 128.0.0.0 longer-prefixesCodes: I - IGRP derived, R - RIP derived, O - OSPF derived,C - connected, S - static, E - EGP derived, B - BGP derived,* - candidate default route, IA - OSPF inter area route,i - IS-IS derived, ia - IS-IS, U - per-user static route,o - on-demand routing, M - mobile, P - periodic downloaded static route,D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,N2 - OSPF NSSA external type 2 routeGateway of last resort is not setS 10.134.0.0 is directly connected, Ethernet0S 10.10.0.0 is directly connected, Ethernet0S 10.129.0.0 is directly connected, Ethernet0S 172.30.0.0 is directly connected, Ethernet0S 172.40.246.0 is directly connected, Ethernet0S 172.20.97.0 is directly connected, Ethernet0S 172.50.88.0 is directly connected, Ethernet0S 172.19.141.0 is directly connected, Ethernet0S 172.60.138.0 is directly connected, Ethernet0S 192.44.237.0 is directly connected, Ethernet0S 192.168.222.0 is directly connected, Ethernet0S 172.90.209.0 is directly connected, Ethernet0S 10.145.0.0 is directly connected, Ethernet0S 10.141.0.0 is directly connected, Ethernet0S 10.138.0.0 is directly connected, Ethernet0S 10.128.0.0 is directly connected, Ethernet0172.19.0.0 255.255.255.0 is subnetted, 1 subnetsC 172.19.64.0 is directly connected, Ethernet0172.110.0.0 is variably subnetted, 2 subnets, 2 masksC 172.110.232.32 255.255.255.240 is directly connected, Ethernet0S 172.110.0.0 255.255.0.0 is directly connected, Ethernet0Router#Related Commands
show interfaces tunnel
Displays a list of tunnel interface information.
Displays the current state of the routing table in summary format.
show ip route profile
To display routing table change statistics, use the show ip route profile command in EXEC mode.
show ip route profile
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
Use this command in combination with the ip route profile global configuration command to validate the routing table change statistics.
Examples
The following example shows the frequency of routing table changes in a 5-second sampling interval. In this example, the Prefix add change occurred 22 times in one interval and 24 times in another interval. The output represents this with a Fwd-path change value of 2 and a Prefix add value of 2:
Router# show ip route profile--------------------------------------------------------------------Change/ Fwd-path Prefix Nexthop Pathcount Prefix interval change add Change Change refresh--------------------------------------------------------------------0 87 87 89 89 891 0 0 0 0 02 0 0 0 0 03 0 0 0 0 04 0 0 0 0 05 0 0 0 0 010 0 0 0 0 015 0 0 0 0 020 2 2 0 0 025 0 0 0 0 0Table 59 describes the significant fields shown in the display.
Related Commands
show ip route summary
To display the current state of the routing table, use the show ip route summary command in EXEC mode.
show ip route summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ip route summary command:
Router# show ip route summaryRoute Source Networks Subnets Overhead Memory (bytes)connected 0 3 126 360static 1 2 126 360igrp 109 747 12 31878 91080internal 3 360Total 751 17 32130 92160Table 60 describes the significant fields shown in the display.
Related Commands
show ip route supernets-only
To display information about supernets, use the show ip route supernets-only privileged command in EXEC mode.
show ip route supernets-only
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show ip route supernets-only command. This display shows supernets only; it does not show subnets.
Router# show ip route supernets-onlyCodes: I - IGRP derived, R - RIP derived, O - OSPF derivedC - connected, S - static, E - EGP derived, B - BGP derivedi - IS-IS derived, D - EIGRP derived* - candidate default route, IA - OSPF inter area routeE1 - OSPF external type 1 route, E2 - OSPF external type 2 routeL1 - IS-IS level-1 route, L2 - IS-IS level-2 routeEX - EIGRP external routeGateway of last resort is not setB 172.160.0.0 (mask is 255.255.0.0) [20/0] via 172.160.72.30, 0:00:50B 192.0.0.0 (mask is 255.0.0.0) [20/0] via 172.160.72.24, 0:02:50Table 61 describes the significant fields shown in the display.
show key chain
To display authentication key information, use the show key chain command in EXEC mode.
show key chain [name-of-chain]
Syntax Description
Defaults
Information about all key chains is displayed.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show key chain command:
Router# show key chainKey-chain trees:key 1 -- text "chestnut"accept lifetime (always valid) - (always valid) [valid now]send lifetime (always valid) - (always valid) [valid now]key 2 -- text "birch"accept lifetime (00:00:00 Dec 5 1995) - (23:59:59 Dec 5 1995)send lifetime (06:00:00 Dec 5 1995) - (18:00:00 Dec 5 1995)Related Commands
show route-map
To display configured route maps, use the show route-map command in EXEC mode.
show route-map [map-name]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show route-map command:
Router# show route-maproute-map abc, permit, sequence 10Match clauses:tag 1 2Set clauses:metric 5route-map xyz, permit, sequence 20Match clauses:tag 3 4Set clauses:metric 6Table 62 describes the significant fields shown in the display.
Related Commands
show route-map ipc
To display counts of the one-way route map interprocess communication (IPC) messages sent from the rendezvous point (RP) to the Versatile Interface Processor (VIP) when NetFlow policy routing is configured, use the show route-map ipc command in EXEC mode.
show route-map ipc
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
This command displays the counts of one-way route map IPC messages from the RP to the VIP when NetFlow policy routing is configured. If you execute this command on the RP, the messages are shown as "Sent." If you execute this command on the VIP console, the IPC messages are shown as "Received."
Examples
The following is sample output from the show route-map ipc command when it is executed on the RP:
Router# show route-map ipcRoute-map RP IPC Config Updates SentName: 4Match access-list: 2Match length: 0Set precedence: 1Set tos: 0Set nexthop: 4Set interface: 0Set default nexthop: 0Set default interface: 1Clean all: 2The following is sample output from the show route-map ipc command when it is executed on the VIP:
VIP-Slot0# show route-map ipcRoute-map LC IPC Config Updates ReceivedName: 4Match access-list: 2Match length: 0Set precedence: 1Set tos: 0Set nexthop: 4Set interface: 0Set default nexthop: 0Set default interface: 1Clean all: 2Table 63 describes the significant fields shown in the first display.
Related Commands
Configures policy routing to verify if the next hops of a route map are CDP neighbors before policy routing to that next hop.
traffic-share min
To configure traffic to use minimum cost routes, when there are multiple routes that have different cost routes to the same destination network, use the traffic-share min across-interfaces command in router configuration mode. To disable this function, use the no form of this command.
traffic-share min {across-interfaces}
no traffic-share min {across-interfaces}
Syntax Description
This command has no arguments or keywords.
Defaults
Traffic is configured to use minimum cost paths.
Command Modes
Router configuration
Command History
10.0
This command was introduced.
11.0(3)
This command became protocol independent when the across-interfaces keyword was added.
Usage Guidelines
The traffic-share min command causes the Cisco IOS software to divide traffic only among the routes with the best metric. Other routes will remain in the routing table, but will receive no traffic. Configuring this command with the across-interfaces keyword allows you to configure multi-interface load splitting on different interfaces with equal cost paths.
Examples
In the following example, multi-interface load splitting is configured on different interfaces with equal cost paths:
router ospf 5traffic-share min across-interfaces
