H3C Technologies H3C S10500 Series Switches User Manual

Page 292

281

Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

3.3.3.9 100 4 8 0 0 00:00:09 Established

Verify your configurations

Issue the display ip routing-table vpn-instance command on the PEs. The output shows the routes to the

peer CEs. Take PE 1 as an example:

[PE1] display ip routing-table vpn-instance vpn1

Routing Tables: vpn1

Destinations : 7 Routes : 7

Destination/Mask Proto Pre Cost NextHop Interface

4.4.4.9/32 BGP 255 0 10.1.1.1 Vlan11

6.6.6.9/32 BGP 255 0 3.3.3.9 NULL0

10.1.1.0/24 Direct 0 0 10.1.1.2 Vlan11

10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0

10.3.1.0/24 BGP 255 0 3.3.3.9 NULL0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

[PE1] display ip routing-table vpn-instance vpn2

Routing Tables: vpn2

Destinations : 5 Routes : 5

Destination/Mask Proto Pre Cost NextHop Interface

5.5.5.9/32 BGP 255 0 10.2.1.1 Vlan12

7.7.7.9/32 BGP 255 0 3.3.3.9 NULL0

10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan12

10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0

10.4.1.0/24 BGP 255 0 3.3.3.9 NULL0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

CEs of the same VPN can ping each other, whereas those of different VPNs can not. For example, CE 1
can ping CE 3 (6.6.6.9), but cannot ping CE 4 (7.7.7.9):

[CE1] ping 6.6.6.9

PING 6.6.6.9: 56 data bytes, press CTRL_C to break

Reply from 6.6.6.9: bytes=56 Sequence=1 ttl=253 time=72 ms

Reply from 6.6.6.9: bytes=56 Sequence=2 ttl=253 time=34 ms

Reply from 6.6.6.9: bytes=56 Sequence=3 ttl=253 time=50 ms

Reply from 6.6.6.9: bytes=56 Sequence=4 ttl=253 time=50 ms

Reply from 6.6.6.9: bytes=56 Sequence=5 ttl=253 time=34 ms

--- 6.6.6.9 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 34/48/72 ms

[CE1] ping 7.7.7.9

PING 7.7.7.9: 56 data bytes, press CTRL_C to break

Request time out