Hierarchical Vpls Configuration Example (Via Qinq) - H3C S9500 Series Operation Manual

Operation Manual – MPLS VPLS
H3C S9500 Series Routing Switches
[UPE-vsi-Hvpls] pwsignal ldp
[UPE-vsi-Hvpls-ldp] vsi-id 1
[UPE-vsi-Hvpls-ldp] peer 1.1.1.1 dual-npe
[UPE-vsi-Hvpls-ldp] peer 2.2.2.2 dual-npe
[UPE-vsi-Hvpls-ldp] quit
[UPE-vsi-Hvpls] broadcast-restrain 100
[UPE-vsi-Hvpls] bandwidth 1024000
[UPE-vsi-Hvpls] quit
# Bind the VPLS instance to the private network interface.
[UPE] vlan 3001
[UPE-vlan3001] interface vlan-interface 3001
[UPE-Vlan-interface3001] l2 binding vsi Hvpls access-mode ethernet
[UPE-Vlan-interface3001]
[UPE-Vlan-interface3001] quit
[UPE] interface Ethernet 3/1/17
[UPE-Ethernet3/1/17] port link-type access
[UPE-Ethernet3/1/17] port access vlan 3001
[UPE-Ethernet3/1/17] vlan-vpn enable

1.4.4 Hierarchical VPLS Configuration Example (via QinQ)

I. Network requriements
1) The devices NPE1, NPE2, and NPE3 are logically mesh-connected through PWs
to constitute an MPLS core network. On NPE1 and NPE2, VLAN 100 and VLAN
200 are for access of user data packets while VLAN 2 is for access of BPDUs.
2) In the network diagram, the MTU device needs to run QinQ (VLAN-VPN) and STP
or MSTP. In this example, an S9500 switch is used as the MTU device, to which
the user devices CE1 and CE2 are attached through ports G4/3/2 and G4/3/1.
Packets to be transparently transmitted are data packets tagged VLAN 1000 and
VLAN 1001 respectively.
II. Network diagram
Figure 1-7 Network diagram for H-VPLS configuration (via QinQ)
1-36
Chapter 1 VPLS Configuration