Configuring Routing On An Mce; Route Exchange Between An Mce And A Vpn Site - HP MSR2000 series Configuration Manual

Figure 129 Network diagram for the MCE function
VPN 1
Site 1
VPN 2
Site 2
On the left-side network, there are two VPN sites, both of which are connected to the MPLS backbone
through the MCE device. VPN 1 and VPN 2 on the left-side network must establish a tunnel with VPN 1
and VPN 2 on the right-side network, respectively.
With MCE enabled, routing tables can be created for VPN 1 and VPN 2 individually, VLAN-interface 2
can be bound to VPN 1, and VLAN-interface 3 can be bound to VPN 2. When receiving a piece of
routing information, MCE determines the source of the routing information according to the number of
the interface receiving the information. It then maintains the corresponding routing table accordingly.
You must also bind the interfaces to the VPNs on PE 1 in the same way as those on the MCE device. The
MCE device is connected to PE 1 through a trunk, which permits packets of VLAN 2 and VLAN 3 with
VLAN tags carried. In this way, PE 1 can determine the VPN a received packet belongs to according to
the VLAN tag of the packet and passes the packet to the corresponding tunnel.

Configuring routing on an MCE

Interface-to-VPN-instance binding enables MCEs and PEs to determine the sources of received packets
and then forward the packets according to the routing information concerning the corresponding VPNs.
MCE routing configuration includes:
MCE-VPN site routing configuration
•
MCE-PE routing configuration
•

Route exchange between an MCE and a VPN site

An MCE can adopt the following routing protocols to exchange VPN routes with a site:
Static route
•
RIP
•
OSPF
•
• IS-IS
IBGP
•
PE1
VLAN-int2
VLAN-int7
VLAN-int8
VLAN-int3
MCE
P
P
PE
393
VPN 2
Site 1
CE
PE2
CE
Site 2
VPN 1