H3C Technologies H3C S6800 Series Switches User Manual

Page 44

Destination: ::1/128 Protocol : Direct

NextHop : ::1 Preference: 0

Interface : InLoop0 Cost : 0

Destination: 2002:1::/64 Protocol : Direct

NextHop : :: Preference: 0

Interface : Vlan20 Cost : 0

Destination: 2002:1::1/128 Protocol : Direct

NextHop : ::1 Preference: 0

Interface : InLoop0 Cost : 0

Destination: 2012::/64 Protocol : OSPFv3

NextHop : FE80::20C:29FF:FE40:701 Preference: 150

Interface : Vlan20 Cost : 1

Destination: FE80::/10 Protocol : Direct

NextHop : :: Preference: 0

Interface : NULL0 Cost : 0

Destination: FF00::/8 Protocol : Direct

NextHop : :: Preference: 0

Interface : NULL0 Cost : 0

The output shows that the MCE has learned the private route of VPN 2. The MCE maintains the
routes of VPN 1 and VPN 2 in two different routing tables. In this way, routes from different VPNs

are separated.

Configure routing between the MCE and PE 1:
# On the MCE, configure the port connected to PE 1 as a trunk port, and configure it to permit
packets of VLAN 30 and VLAN 40 to pass with VLAN tags.

[MCE] interface fortygige 1/0/3

[MCE-FortyGigE1/0/3] port link-type trunk

[MCE-FortyGigE1/0/3] port trunk permit vlan 30 40

[MCE-FortyGigE1/0/3] quit

# On PE 1, configure the port connected to MCE as a trunk port, and configure it to permit packets
of VLAN 30 and VLAN 40 to pass with VLAN tags.

[PE1] interface fortygige 1/0/1

[PE1-FortyGigE1/0/1] port link-type trunk

[PE1-FortyGigE1/0/1] port trunk permit vlan 30 40

[PE1-FortyGigE1/0/1] quit

# On the MCE, create VLAN 30 and VLAN-interface 30, bind VLAN-interface 30 with VPN
instance vpn1, and configure an IPv6 address for the VLAN-interface 30.

[MCE] vlan 30

[MCE-vlan30] quit

[MCE] interface vlan-interface 30

[MCE-Vlan-interface30] ip binding vpn-instance vpn1

[MCE-Vlan-interface30] ipv6 address 30::1 64

[MCE-Vlan-interface30] quit