H3C Technologies H3C SR8800 - Manual (Page 198)

187
[PE2–mpls-ldp] quit
# Configure basic MPLS for GigabitEthernet 3/1/2, the interface connected to ASBR 2.
[PE2] interface GigabitEthernet 3/1/2
[PE2-GigabitEthernet3/1/2] ip address 12.1.1.4 24
[PE2-GigabitEthernet3/1/2] mpls
[PE2-GigabitEthernet3/1/2] mpls ldp
[PE2-GigabitEthernet3/1/2] quit
# Enable L2VPN and MPLS L2VPN.
[PE2] l2vpn
[PE2-l2vpn] mpls l2vpn
[PE2-l2vpn] quit
# Configure VPLS instance aaa that uses LDP signaling.
[PE2] vsi aaa static
[PE2-vsi-aaa] pwsignal ldp
[PE2-vsi-aaa-ldp] vsi-id 500
[PE2-vsi-aaa-ldp] peer 3.3.3.3
[PE2-vsi-aaa-ldp] quit
[PE2-vsi-aaa] quit
# Bind VPLS instance aaa to GigabitEthernet 3/1/1, the interface connected to CE 2.
[PE2] interface GigabitEthernet 3/1/1
[PE2-GigabitEthernet3/1/1] l2 binding vsi aaa
[PE2-GigabitEthernet3/1/1] quit
5. Verify the configuration.
Execute the display vpls connection command on each device. You will see that a PW in up state
has been established between the devices.
Troubleshooting VPLS
Symptom
The VPLS link PW is not up.
Analysis
• The public network LSP tunnel is not established.
• The extended session is not working normally.
• A private VLAN virtual interface is not bound with the corresponding VPLS instance and is not up.
• When LDP is used as the PW signaling protocol, if the corresponding VPLS instances on the two
peers have different MTU settings, the PW cannot come up.
Solution
• Check the routing tables of the PEs to see whether a route is available between the two PEs. Check
whether each router can ping the loopback interface of the peer and whether the LDP session is
normal.
• Check whether any extended session configuration command is missing at either side.
• Check whether the private network interfaces are up or whether the PW to the UPE is up.
• Check whether the PW ID and transport mode are the same on the two peers.