Troubleshooting Mpls L2Vpn - HP 12500 Series Configuration Manual

Total
Transport
VC ID
101
# Ping CE 2 from CE 1.
[CE1] ping 100.1.1.2
PING 100.1.1.2: 56
Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=30 ms
Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=60 ms
Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=50 ms
Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=40 ms
Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=70 ms
--- 100.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 30/50/70 ms

Troubleshooting MPLS L2VPN

Symptom 1:
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 (displayed as --).
Analysis:
The reason the VC is down may be that the PEs are configured with different encapsulation types.
Solution:
• Check whether the local PE and the peer PE are configured with the same encapsulation type. If not,
the connection is destined to fail.
Check whether the PEs are configured with the Remote argument and whether the peer addresses
•
are correctly configured.
ldp vc : 1 1 up
Client
Intf
GE5/0/1
data bytes, press CTRL_C to break
0 down 0 blocked
Service VC Local
ID State VC Label
-- up 65674
190
Remote
VC Label
65880