Cisco Catalyst 3750 Software Configuration Manual page 716

Metro switch
Hide thumbs Also See for Catalyst 3750:
Table of Contents

Advertisement

Understanding MPLS VPNs
Figure 30-1
devices.
Figure 30-1 VPNs with a Service-Provider Backbone
Site 1
VPN 1
CE
Each VPN contains customer devices attached to the CE devices. The customer devices use VPNs to
exchange information between devices, and the provider routers (P) are not aware of the VPNs.
Figure 30-2
with these sites:
VPN1: Sites 2 and 4
VPN2: Sites 1, 3, and 4
VPN3: Sites 1, 3, and 5
Catalyst 3750 Metro Switch Software Configuration Guide
30-4
Flexible addressing—Customers can continue to use their present address spaces without network
address translation (NAT) because the MPLS VPN provides a public and private view of the address.
A NAT is required only if two VPNs with overlapping address spaces want to communicate.
Straightforward migration—You can build MPLS VPNs over multiple network architectures.
Migration for the end customer is simplified because the CE router is not required to support MPLS,
so no customer's intranet modifications are needed.
MPLS VPN also provides increased BGP functionality.
shows an example of a VPN with a service-provider backbone network, PE routers, and CE
Service provider
PE
backbone
P
P
shows five customer sites communicating within three VPNs. The VPNs can communicate
P
PE
PE
P
Site 3
VPN 2
Chapter 30
Configuring MPLS and EoMPLS
Site 2
VPN 1
CE
VPN 2
CE
CE
78-15870-01

Advertisement

Table of Contents
loading

Table of Contents