H3C Technologies H3C S7500E Series Switches - Manual (Page 225)

5-33
[CE2-Vlan-interface10] ip address 100.1.1.2 24
6) Verify your configuration
After the above configuration, display the L2VPN connection information on PE 1 and PE 2. You
should see that an L2VC has been established. CE 1 and CE 2 should be able to ping each other.
# Display the L2VPN connection information on PE 1.
[PE1] display mpls l2vc
Total ldp vc : 1 1 up 0 down
Transport Client Service VC Local Remote Tunnel
VC ID Intf ID State VC Label VC Label Policy
1000 GE2/0/1 1000 up 8193 8192 default
# Display the L2VPN connection information on PE 2.
[PE2] display mpls l2vc
Total ldp vc : 1 1 up 0 down
Transport Client Service VC Local Remote Tunnel
VC ID Intf ID State VC Label VC Label Policy
1000 GE2/0/1 1000 up 8192 8193 default
# Ping CE 2 from CE 1.
[CE1] ping 100.1.1.2
PING 100.1.1.2: 56 data bytes, press CTRL_C to break
Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=90 ms
Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=77 ms
Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=34 ms
Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=46 ms
Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=94 ms
--- 100.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 34/68/94 ms
Troubleshooting MPLS L2VPN
Symptom:
After the L2VPN configuration, the peer PEs cannot ping each other. The output of the display mpls
l2vc command shows that the VC is down and the remote VC label is invalid.
Analysis:
The reason the VC is down may be that the PEs are configured with different encapsulation types.
Solution:
z
Check whether the local PE and the peer PE are configured with the same encapsulation type. If
not, the connection is destined to fail.
z
Check whether the PEs are configured with the Remote argument and whether the peer
addresses are correctly configured.