H3C Technologies H3C S10500 Series Switches - Manual (Page 231)

220
5. Verify your configuration
# Issue the display mpls l2vpn connection command on the PEs. The output shows that an L2VPN
connection in up state has been established between the PEs. Take PE 1 as an example:
Display the MPLS L2VPN connection information on PE 1.
[PE1] display mpls l2vpn connection
1 total connections,
connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown
VPN name: vpn1,
1 total connections,
connections: 1 up, 0 down, 0 local, 1 remote, 0 unknown
CE name: ce1, id: 1,
Rid type status peer-id route-distinguisher intf
2 rmt up 4.4.4.4 100:1 Vlan10
# 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
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.