
196
# Display VC information on PE 2. The output shows that a VC has been established.
[PE2] display mpls l2vc
Total ldp vc : 1 1 up 0 down 0 blocked
Transport Client Service VC Local Remote
VC ID Intf ID State VC Label VC Label
1000 XGE1/0/1 1000 up 8192 8193
# Ping CE 2 from CE 1. The output shows that CE 1 and CE 2 can ping each other.
[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
This section describes troubleshooting techniques for MPLS L2VPN.
Symptom 1
After the L2VPN configuration, the peer PEs cannot ping each other. The
display mpls l2vc
command output shows that the VC is down and the remote VC label is invalid (displayed as --).
Analysis
The reason the VC is down might be that the PEs are configured with different VC types.
Solution
1.
Verify that the local PE and the peer PE are configured with the same VC type.
2.
Verify that the remote peer is correctly configured on each PE.
Symptom 2
Serial 2/1/0 and Serial 2/1/1 are configured with different VC types: one is HDLC and the other PPP.
They each create a Martini VC, with the same VC ID of 1. If you change the VC type of Serial 2/1/1 to
HDLC, the Martini VC cannot be established.
Analysis
If you change the VC type of Serial 2/1/1 to HDLC, there are two Martini VCs with the same VC type
of HDLC and the same VC ID of 1. To avoid VC ID conflict, the system automatically removes the
Martini VC on Series 2/1.
Solution
Re-create Martini VCs on interface Serial 2/1/0 and interface Serial 2/1/1, and configure different VC
IDs for the two VCs.