Specifications

ip route vrf
MP-102
Cisco IOS Multiprotocol Label Switching Command Reference
January 2010
Supported Static Routes in an MPLS VPN Environment
The following ip route vrf commands are supported when you configure static routes in an MPLS VPN
environment, and the next hop and interface are in the same VRF:
– ip route vrf vrf-name destination-prefix mask next-hop-address
– ip route vrf vrf-name destination-prefix mask interface next-hop-address
– ip route vrf vrf-name destination-prefix mask interface1 next-hop1
ip route vrf v
rf-name destination-prefix mask interface2 next-hop2
The following ip r
oute vrf commands are supported when you configure static routes in an MPLS VPN
environment, and the next hop is in the global table in the MPLS cloud in the global routing table. For
example, these commands are supported when the next hop is pointing to the Internet Gateway.
– ip route vrf vrf-name destination-prefix mask next-hop-address global
– ip route vrf vrf-name destination-prefix mask interface next-hop-address
(This command is supported when the next hop and interface are in the core.)
The following ip r
oute commands are supported when you configure static routes in an MPLS VPN
environment and enable load sharing with static nonrecursive routes and a specific outbound interfaces:
ip route d
estination-prefix mask interface1 next-hop1
ip route d
estination-prefix mask interface2 next-hop2
Unsupported Static Routes in an MPLS VPN Environment That Uses the TFIB
The following ip route command is not supported when you configure static routes in an MPLS VPN
environment, the next hop is in the global table in the MPLS cloud within the core, and you enable load
sharing where the next hop can be reached through two paths:
ip route vr
f destination-prefix mask next-hop-address global
The following ip r
oute commands are not supported when you configure static routes in an MPLS VPN
environment, the next hop is in the global table in the MPLS cloud within the core, and you enable load
sharing where the destination can be reached through two next hops:
ip route vr
f destination-prefix mask next-hop1 global
ip route vr
f destination-prefix mask next-hop2 global
The following ip r
oute vrf commands are not supported when you configure static routes in an MPLS
VPN environment, and the next hop and interface are in the same VRF:
ip route vrf v
rf-name destination-prefix mask next-hop1
ip route vrf v
rf-name destination-prefix mask next-hop2
Supported Static Routes in an MPLS VPN Environment Where the Next Hop Resides in the Global Table on the CE
Router
The following ip route vrf command is supported when you configure static routes in an MPLS VPN
environment, and the next hop is in the global table on the customer equipment (CE) side. For example,
the following command is supported when the destination prefix is the CE router’s loopback address, as
in external BGP (EBGP) multihop cases.
ip route vrf v
rf-name destination-prefix mask interface next-hop-address
The following ip r
oute commands are supported when you configure static routes in an MPLS VPN
environment, the next hop is in the global table on the CE side, and you enable load sharing with static
nonrecursive routes and a specific outbound interfaces:
ip route d
estination-prefix mask interface1 nexthop1
ip route d
estination-prefix mask interface2 nexthop2