Specifications

ip route vrf
MP-101
Cisco IOS Multiprotocol Label Switching Command Reference
January 2010
Usage Guidelines Use a static route when the Cisco IOS software cannot dynamically build a route to the destination.
If you specify an administrative distance when you set up a route, you are flagging a static route that can
be
overridden by dynamic information. For example, Interior Gateway Routing Protocol (IGRP)-derived
routes have a default administrative distance of 100. To set a static route to be overridden by an IGRP
dynamic route, specify an administrative distance greater than 100. Static routes each have a default
administrative distance of 1.
Static routes that point to an interface are advertised through the Routing Information Protocol (RIP),
IG
RP, and other dynamic routing protocols, regardless of whether the routes are redistributed into those
routing protocols. That is, static routes configured by specifying an interface lose their static nature when
installed into the routing table.
However, if you define a static route to an interface not defined in a network command, no dynamic
ro
uting protocols advertise the route unless a redistribute static command is specified for these
protocols.
Supported Static Route Configurations
When configuring static routes in a Multiprotocol Label Switching (MPLS) or MPLS VPN environment,
some variations of the ip route and ip route vrf commands are not supported. These variations of the
commands are not supported in Cisco IOS releases that support the Tag Forwarding Information Base
(TFIB), specifically Cisco IOS Releases 12.xT, 12.xM, and 12.0S. The TFIB cannot resolve prefixes
when the recursive route over which the prefixes travel disappears and then reappears. However, the
command variations are supported in Cisco IOS releases that support the MPLS Forwarding
Infrastructure (MFI), specifically Cisco IOS Release 12.2(25)S and later releases. Use the following
guidelines when configuring static routes.
Supported Static Routes in an MPLS Environment
The following ip route command is supported when you configure static routes in MPLS environment:
ip route d
estination-prefix mask interface next-hop-address
The following ip r
oute commands are supported when you configure static routes in an MPLS
environment and configure load sharing with static nonrecursive routes and a specific outbound
interface:
ip route d
estination-prefix mask interface1 next-hop1
ip route d
estination-prefix mask interface2 next-hop2
Unsupported Static Routes in an MPLS Environment That Uses the TFIB
The following ip route command is not supported when you configure static routes in an MPLS
environment:
ip route d
estination-prefix mask next-hop-address
The following ip r
oute command is not supported when you configure static routes in an MPLS
environment and enable load sharing where the next hop can be reached through two paths:
ip route d
estination-prefix mask next-hop-address
The following ip r
oute command is not supported when you configure static routes in an MPLS
environment and enable load sharing where the destination can be reached through two next hops:
ip route d
estination-prefix mask next-hop1
ip route d
estination-prefix mask next-hop2
Use the in
terface and next-hop arguments when specifying static routes.