Chapter 1 About Cisco IP Solution Center
About MPLS VPNs
Figure 1-9 VRFs for Sites in Multiple VPNs
Site 1 |
|
|
| Site 4 |
VPN A | Site 2 | VPN B | Site 3 | VPN C |
ip vrf site1 rd 100:1
ip vrf site2 rd 100:2
Multihop
PP
PE1 | PE2 |
ip vrf site3 rd 100:3
ip vrf site4 rd 100:4
VRF
for site 1
(100:1)
Site 1 routes Site 2 routes
Site 1
VRF
for site 2
(100:2)
Site 1 routes Site 2 routes Site 3 routes
Site 2
VRF
for site 3
(100:3)
Site 2 routes Site 3 routes Site 4 routes
Site 3
VRF
for site 4
(100:4)
Site 3 routes Site 4 routes
Site 4
28558
VRF Implementation Considerations
When implementing VPNs and VRFs, Cisco recommends you keep the following considerations in mind:
•A local VRF interface on a PE is not considered a
vrf vrf_name command.
•The global routing table and the
•You can issue a standard Telnet command from a CE router to connect to a PE router. However, from that PE, you must issue the following command to connect from the PE to the CE:
telnet CE_RouterName /vrf vrf_name
Similarly, you can utilize the Traceroute and Ping commands in a VRF context.
Cisco IP Solution Center, 3.0: MPLS VPN Management User Guide, 3.0
|
| ||
|
|