171
# Execute the
display minm connection
command on BEB-PE. You can see the MAC-in-MAC uplink
information of the VSI
aaa
. The information means that BEB-PE has learnt the B-MAC information
from BEB, its peer device.
[BEB-PE] display minm connection vsi aaa
VSIID LinkID BMAC BVLAN Interface Name State AGING TIME(s)
500 1 000F-E200-0001 VLAN 20 GigabitEthernet3/0/1 Learned AGING
# Ping CE 2 from CE 1. The ping operation succeeds.
<CE1> ping 10.1.1.2
PING 10.1.1.2: 56 data bytes, press CTRL_C to break
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=180 ms
Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=60 ms
Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=10 ms
Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=70 ms
Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=60 ms
--- 10.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 10/76/180 ms
Troubleshooting VPLS
Symptom
The VPLS PW is not up.
Analysis
•
The public network LSP tunnel is not established.
•
The extended session is not working normally.
•
A private network interface is not bound with the corresponding VPLS instance or the private
network interface is not up.
•
The AC port at the private network side is not up.
•
Negotiation of VPLS parameters, such as PW ID, MTU, and transport mode, is failed on the two
peers.
Solution
•
Check the routing tables of the PEs to see whether a route is available between the two PEs. Check
whether each device can ping the loopback interface of the peer and whether the LDP session is
normal.
•
Check whether any extended session configuration command is missing at either side.
•
View the private interface status by using the
display interface
command. Make sure the private
interface is up.
•
View the current configuration by using the
display current-configuration
command. Make sure that
the two peers have the same PW ID and transport mode.