Bgp/Mpls Vpn Model - 3Com 8800 Configuration Manual

3com 8800: install guide
Hide thumbs Also See for 8800:
Table of Contents

Advertisement

3Com Switch 8800 Configuration Guide

37.1.1 BGP/MPLS VPN Model

I. BGP/MPLS VPN model
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
CE
CE
CE
CE
CE
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
VPN2
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
site 3
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
Figure 37-1 MPLS VPN model
As shown in Figure 37-1, MPLS VPN model contains three parts: CE, PE and P.
CE (Customer Edge) device: It is a composing part of the customer network, which
is usually connected with the service provider directly through an interface. It may
be a router or a switch which cannot sense the existence of VPN.
PE (Provider Edge) router: It is the Provider Edge router, namely the edge device
of the provider network, which connects with your CE directly. In MPLS network,
PE router processes all the operations for VPN.PE needs to possess MPLS basic
forwarding capability.
P (Provider) router: It is the backbone router in the provider network, which is not
connected with CE directly. P router needs to possess MPLS basic forwarding
capability.
The classification of CE and PE mainly depends on the range for the management of
the provider and the customer, and CE and PE are the edges of the management
ranges.
II. Nested BGP/MPLS VPN model
In a basic BGP/MPLS VPN model, the PEs are in the network of the service provider
and are managed by the service provider.
When a VPN user wants to subdivide the VPN into multiple VPNs, the traditional
solution is to configure these VPNs directly on the PEs of the service provider. This
solution is easy to implement, but has the following disadvantages: the number of the
VPNs carried on PEs may increase rapidly; the operator may have to perform more
operations when required by a user to adjust the relation between the user's internal
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
Backbone network of
Backbone network of
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
the service provider
the service provider
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
Chapter 37 BGP/MPLS VPN Configuration
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
37-2
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
site 1
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
VPN 2
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
VPN1
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
site 2
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE
CE

Advertisement

Table of Contents
loading

Table of Contents