H3C Technologies H3C SR8800 User Manual

Page 231

Advertising
background image

220

<Sysname> system-view

[Sysname] sysname PE

[PE] l2vpn

[PE-l2vpn] mpls l2vpn

[PE-l2vpn] quit

[PE] mpls l2vpn vpn1 encapsulation ethernet

[PE-mpls-l2vpn-vpn1] route-distinguisher 100:1

[PE-mpls-l2vpn-vpn1] vpn-target 111:1

[PE-mpls-l2vpn-vpn1] ce ce1 id 1

[PE-mpls-l2vpn-ce-vpn1-ce1] connection ce-offset 2 interface GigabitEthernet4/1/1

[PE-mpls-l2vpn-ce-vpn1-ce1] quit

[PE-mpls-l2vpn-vpn1] ce ce2 id 2

[PE-mpls-l2vpn-ce-vpn1-ce2] connection ce-offset 1 interface GigabitEthernet4/1/2

[PE-mpls-l2vpn-vpn1] quit

2.

Verify your configuration.
# Issue the display mpls l2vpn connection command on the PE. The output shows that two local
L2VPN connections are established and in up state.

[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 route-distinguisher intf

2 loc up --- --- GigabitEthernet4/1/1

CE name: ce2, id: 2,

Rid type status peer-id route-distinguisher intf

1 loc up --- --- GigabitEthernet4/1/2

# Ping CE 2 from CE 1. The output shows that CE 1 and CE 2 can ping each other.

[CE1] ping 30.1.1.2

PING 30.1.1.2: 56 data bytes, press CTRL_C to break

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

Advertising