ip route vrf command to add a static route in the customer's VRF for each prefix in that
customer's site.
Each of these static routes must point to the link connecting the PE router to the CE
router. Typically, you redistribute these static routes in the VRF's address family in BGP
or use network commands to make those prefixes reachable from other CE routers in
the same VPN.
Figure 92: Configuring Static Routes
In Figure 92 on page 437, PE 2 has external BGP connections to CE 3 and CE 4. PE 1 has
an EBGP connection to CE 2. However, no BGP (or IGP) connection exists between PE 1
and CE 1. The following example shows how to configure static routes on VRF A for both
prefixes in CE 1.
host1(config)#virtual-router pe1
host1:pe1(config)#ip vrf vpnA
host1:pe1(config-vrf)#ip route vrf vrfA 10.3.0.0 255.255.0.0 10.1.1.1
host1:pe1(config-vrf)#ip route vrf vrfA 10.12.0.0 255.255.0.0 10.1.1.1
ip route vrf
• Use to add a static route to a VRF.
• Example
host1:pe1(config-router-af)#ip route vrf vrfA 10.0.0.0 255.0.0.0 192.168.1.1
• Use the no version to remove a static route from a VRF.
• See ip route.
Configuring IGPs on the VRF
If you do not configure static routes on the VRF for each prefix in the associated customer
site, then you must configure an IGP on the VRF so that the VRF can learn routes from
customer sites.
Configuring the IGP in the VRF Context
After creating a VRF, you can access it as if it were a virtual router for the purpose of
configuring the IGP.
437Copyright © 2010, Juniper Networks, Inc.
Chapter 6: Configuring BGP-MPLS Applications
To Next Page
Loading...
Need help?
General
