HP 10500 Series Configuration Manual page 134

Peer
3.3.3.9
Verify the configuration:
6.
Execute the display ip routing-table vpn-instance command on the PEs. The output shows the
routes to the CEs. Take PE 1 as an example:
[PE1] display ip routing-table vpn-instance vpn1
Destinations : 13
Destination/Mask
0.0.0.0/32
10.1.1.0/24
10.1.1.0/32
10.1.1.2/32
10.1.1.255/32
10.3.1.0/24
127.0.0.0/8
127.0.0.0/32
127.0.0.1/32
127.255.255.255/32
224.0.0.0/4
224.0.0.0/24
255.255.255.255/32
CEs of the same VPN can ping each other, whereas those of different VPNs cannot. For example,
CE 1 can ping CE 3 (10.3.1.1) but cannot ping CE 4 (10.4.1.1):
[CE1] ping 10.3.1.1
PING 10.3.1.1 (10.3.1.1): 56 data bytes
56 bytes from 10.3.1.1: icmp_seq=0 ttl=254 time=5.000 ms
56 bytes from 10.3.1.1: icmp_seq=1 ttl=254 time=2.000 ms
56 bytes from 10.3.1.1: icmp_seq=2 ttl=254 time=3.000 ms
56 bytes from 10.3.1.1: icmp_seq=3 ttl=254 time=1.000 ms
56 bytes from 10.3.1.1: icmp_seq=4 ttl=254 time=2.000 ms
--- 10.3.1.1 ping statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.000/2.600/5.000/1.356 ms
[CE1] ping 10.4.1.1
PING 10.4.1.1 (10.4.1.1): 56 data bytes
Request time out
Request time out
Request time out
Request time out
Request time out
--- 10.4.1.1 ping statistics ---
5 packet(s) transmitted, 0 packet(s) received, 100.0% packet loss
AS MsgRcvd
100 3
Routes : 13
Proto Pre Cost
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
BGP 255 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
128
MsgSent OutQ PrefRcv Up/Down
6 0
NextHop
127.0.0.1
10.1.1.2
10.1.1.2
127.0.0.1
10.1.1.2
3.3.3.9
127.0.0.1
127.0.0.1
127.0.0.1
127.0.0.1
0.0.0.0
0.0.0.0
127.0.0.1
State
0 00:00:32 Established
Interface
InLoop0
Vlan11
Vlan11
InLoop0
Vlan11
Vlan13
InLoop0
InLoop0
InLoop0
InLoop0
NULL0
NULL0
InLoop0