179
# On the interface connecting CE 2, create service instance 1000 and bind it with VPLS instance
aaa, and create service instance 2000 and bind it with VPLS instance bbb.
[PE2] interface gigabitethernet 1/0/1
[PE2-GigabitEthernet1/0/1] service-instance 1000
[PE2-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 100
[PE2-GigabitEthernet1/0/1-srv1000] xconnect vsi aaa
[PE2-GigabitEthernet1/0/1-srv1000] quit
[PE2-GigabitEthernet1/0/1] service-instance 2000
[PE2-GigabitEthernet1/0/1-srv2000] encapsulation s-vid 200
[PE2-GigabitEthernet1/0/1-srv2000] xconnect vsi bbb
[PE2-GigabitEthernet1/0/1-srv2000] quit
[PE2-GigabitEthernet1/0/1] quit
4. Verify the configuration:
# Issue the display vpls connection command on the PEs. The output shows that a PW connection
in up state has been established. Take PE 2 as an example:
[PE2] display vpls connection vsi aaa verbose
VSI Name: aaa Signaling: ldp
**Remote Vsi ID : 500
VC State : up
Encapsulation : vlan
Group ID : 0
Remote MTU : 1500
Peer Ip Address : 1.1.1.9
PW Type : label
Local VC Label : 89766
Remote VC Label : 81922
Link ID : 1
Tunnel Policy : --
Tunnel ID : 0x4600068
Configuring PW redundancy for H-VPLS access
Network requirements
As shown in Figure 44, CE 1 and CE 2 are connected to UPE through VLANs.
UPE establishes a PW connection (U-PW) with NPE 1 and NPE 2, with the NPE 2 link as the backup.
NPE 1 and NPE 2 each establish a PW connection (N-PW) with NPE 3.
Create a VPLS instance and configure it to support H-VPLS networking.
To Next Page
Loading...
Need help?
General
