
Operation Manual – MPLS L2VPN
H3C S9500 Series Routing Switches
Chapter 1 MPLS L2VPN Configuration
1-35
[PEA-mpls-l2vpn-vpn1] route-distinguisher 100:1
[PEA-mpls-l2vpn-vpn1] vpn-target 1:1
[PEA-mpls-l2vpn-vpn1] ce ce1 id 1 range 10
[PEA-mpls-l2vpn-ce-vpn1-ce1] connection ce-offset 2 interface vlan-interface
10
[PEA-mpls-l2vpn-ce-vpn1-ce1] quit
[PEA-mpls-l2vpn-vpn1] quit
# Configure PE B.
[PEB] mpls l2vpn vpn1 encapsulation vlan
[PEB-mpls-l2vpn-vpn1] route-distinguisher 100:1
[PEB-mpls-l2vpn-vpn1] vpn-target 1:1
[PEB-mpls-l2vpn-vpn1] ce ce2 id 2 range 10
[PEB-mpls-l2vpn-ce-vpn1-ce2] connection ce-offset 1 interface Vlan-interface
10
[PEB-mpls-l2vpn-ce-vpn1-ce2] quit
[PEB-mpls-l2vpn-vpn1] quit
5)
Verify the configuration
After completing the above configurations, you can issue the
display mpls l2vpn
connection
command on the PEs. You should see that an L2VPN connection is
established between the PEs and the connection is up. CE A and CE B should be able
to ping each other. The following takes PE A as an example:
[PEA] 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
[CEA] 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