Troubleshooting Mpls L2Vpn - 3Com MSR 50 Series Configuration Manual

1456 C 78: MPLS L2VPN C
HAPTER
Troubleshooting MPLS
L2VPN
ONFIGURATION
[PE-mpls-l2vpn-ce-vpn1-ce2] connection ce-offset 1 interface serial 2/1
[PE-mpls-l2vpn-vpn1] quit
2 Verify your configuration
After completing the above configurations, you can issue the display mpls l2vpn
connection command on the PE. You should see that an L2VPN connection is
established and in the state of up. You can also view the connection
configurations. CE 1 and CE 2 should be able to ping each other.
[PE] display mpls l2vpn connection
2 total connections,
connections: 2 up, 0 down, 2 local, 0 remote, 0 unknown
VPN name: vpn1,
2 total connections,
connections: 2 up, 0 down, 2 local, 0 remote, 0 unknown
CE name: ce1, id: 1,
Rid type status peer-id
2 loc up
CE name: ce2, id: 2,
Rid type status peer-id
1 loc up
[PE]display mpls l2vpn vpn-name vpn1 local-ce
ce-name
ce1
ce2
[CE1] ping 30.1.1.2
PING 30.1.1.2: 56
Reply from 30.1.1.2: bytes=56 Sequence=1 ttl=255 time=90 ms
Reply from 30.1.1.2: bytes=56 Sequence=2 ttl=255 time=77 ms
Reply from 30.1.1.2: bytes=56 Sequence=3 ttl=255 time=34 ms
Reply from 30.1.1.2: bytes=56 Sequence=4 ttl=255 time=46 ms
Reply from 30.1.1.2: bytes=56 Sequence=5 ttl=255 time=94 ms
--- 30.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
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.
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.
route-distinguisher
--- ---
route-distinguisher
--- ---
ce-id range
1 10
2 10
data bytes, press CTRL_C to break
conn-num LB
1 8192/0/10
1 8202/0/10
intf
Serial2/0
intf
Serial2/1