H3C MS4520V2-24TP, Руководство по настройке

Страница: 11 / 47

4
•
Route exchange between MCE and VPN site —Create VPN instances VPN 1 and VPN 2 on
the MCE. Bind VLAN-interface 2 to VPN 1, and VLAN-interface 3 to VPN 2. The MCE adds a
received route to the routing table of the VPN instance that is bound to the receiving interface.
•
Route exchange between MCE and PE —The MCE connects to PE 1 through trunk links. On
PE 1, create VPN instances for VPN 1 and VPN 2. Bind VLAN-interface 2 to VPN 1, and
VLAN-interface 3 to VPN 2. The MCE and PE add a received route to the routing table of the
VPN instance that is bound to the receiving interface.
Figure 3 Network diagram for the MCE feature
You can configure static routes, RIP, OSPF, IS-IS, EBGP, or IBGP between an MCE and a VPN site
and between an MCE and a PE.
NOTE:
To implement dynamic IP assignment for DHCP clients in private networks, you can configure
DHCP server or DHCP relay agent on the MCE. When the MCE functions as the DHCP server, the
IP addresses assigned to different private networks cannot overlap.
Restrictions and guidelines: MCE configuration
On the PE, disable routing loop detection to avoid route loss during route calculation, and disable
route redistribution between routing protocols to save system resources.
MCE tasks at a glance
To configure MCE, perform the following tasks:
1. Configuring VPN instances
Perform the following VPN instance tasks on PEs and MCEs:
a. Creating a VPN instance
b. Associating a VPN instance with a Layer 3 interface
c. (Optional.) Configuring route related attributes for a VPN instance
2. Configuring routing between an MCE and a VPN site
VPN 1
Site 1
VPN 2
Site 2
CE
CE
VPN 2
Site 3
VPN 1
Site 4
PE 3
PE 2
P
P
Vlan-int2
Vlan-int3
MCE
PE 1
Vlan-int2
Vlan-int3
Vlan-int2
Vlan-int3