H3C Technologies H3C S5820V2 Series Switches - Manual (Page 11)

5
You must also bind PE 1' interfaces connected to the MCE to the VPNs in the same way. The MCE
connects to PE 1 through a trunk link, 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 sends the packet through the corresponding tunnel.
Configuring an MCE
Configuring VPN instances
Configuring VPN instances is required in all MCE networking schemes.
VPN instances isolate not only VPN routes from public network routes, but also routes among VPNs. This
feature allows VPN instances to be used in networking scenarios besides MCE.
Creating a VPN instance
You can configure a description for a VPN instance to record its related information, such as its
relationship with a certain VPN.
To create and configure a VPN instance:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a VPN instance and
enter VPN instance view.
ip vpn-instance vpn-instance-name
No VPN instance is created by
default.
3. Configure an RD for the VPN
instance. route-distinguisher
route-distinguisher No RD is specified for the VPN
instance by default.
4. (Optional) Configure a
description for the VPN
instance.
description text
No description is configured for
the VPN instance by default.
NOTE:
To configure BGP for a VPN instance on the MCE, you must configure an RD for the VPN instance.
Associating a VPN instance with an interface
After configuring a VPN instance, you must associate the VPN instance with the interfaces connected to
the VPN site or the PE.
To associate a VPN instance with an interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Associate the current interface
with a VPN instance. ip binding vpn-instance
vpn-instance-name No VPN instance is associated
with an interface by default.