R3102-R3103-HP 6600/HSR6600 Routers MPLS Configuration Guide

243
[PE2-GigabitEthernet2/1/2] mpls
[PE2-GigabitEthernet2/1/2] mpls ldp
[PE2-GigabitEthernet2/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-3.3.3.3] quit
[PE2-vsi-aaa-ldp] quit
[PE2-vsi-aaa] quit
# Bind VPLS instance aaa to GigabitEthernet 2/1/1, the interface connected to CE 2.
[PE2] interface gigabitethernet 2/1/1
[PE2-GigabitEthernet2/1/1] l2 binding vsi aaa
[PE2-GigabitEthernet2/1/1] quit
5. Verify the configuration:
Execute the display vpls connection command on each device. You can see that a PW in up state
has been established between the devices.
Troubleshooting VPLS
Symptom
The VPLS PW is not up.
Analysis
• The public network LSP tunnel is not established.
• The extended session is not working correctly.
• A private network interface is not bound with the corresponding VPLS instance or the private
network interface is not up.
Solution
• Check the routing tables of the PEs to verify that a route is available between the two PEs. Verify that
each device 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.
• View the private interface status by using the display interface command. Make sure the private
interface is up.
• View the current configuration by using the display current-configuration command. Make sure the
two peers have the same PW ID and transport mode.