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

213
6. Verify your configuration.
Display L2VPN connection information on PE 1 or PE 2. The output shows that an L2VC established.
# Display L2VPN connection information on PE 1.
[PE1] 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
101 Vlan10 -- up 8193 8192
# Display L2VPN connection information on PE 2.
[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
101 Vlan10 -- 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=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
Example for configuring MPLS L2VPN connection for a service
instance
Netowrk requirments
CE 1 and CE 2 are connected to PE 1 and PE 2 respectively through VLAN interfaces.
On PE 1 and PE 2, create MPLS L2VPN connections for CE 1 and CE 2 in service instance view.