Operation Manual – MCE
H3C S3610&S5510 Series Ethernet Switches
Chapter 1 MCE Overview
1-6
Figure 1-3
How MCE works
, the two VPN sites on the left side (Site 1 and Site 2) are connected to the
backbone network through an MCE device. Two VPN tunnels are expected between
them and the remote VPNs at Site 2 and Site 1.
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
and then maintains the corresponding routing table accordingly.
You need to also to bind the interfaces/sub-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.
1.2 Routing Information Exchange for MCE
Interface-to-VPN-instance binding enables CEs and PEs to determine the sources of
received packets and then forward the packets according to the routing information
concerning the corresponding VPNs. The following sections describe the way how
MCE transmits the private routing information of multiple VPNs to PEs properly.
1.2.1 Route Exchange between a CE and the Private Network
A CE can adopt the following routing protocols to exchange VPN routes with a site:
z
Static route
z
RIP
z
OSPF
z
IS-IS
