Configuring A Hub-Spoke Network - HP 10500 SERIES Configuration Manual

127.0.0.0/8
127.0.0.1/32
[PE1] display ip routing-table vpn-instance vpn2
Routing Tables: vpn2
Destination/Mask
5.5.5.9/32
7.7.7.9/32
10.2.1.0/24
10.2.1.2/32
10.4.1.0/24
127.0.0.0/8
127.0.0.1/32
CEs of the same VPN can ping each other. Those of different VPNs cannot ping each other. 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
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
Request time out
Request time out
Request time out
Request time out
Request time out
--- 7.7.7.9 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss

Configuring a hub-spoke network

Network requirements
The spoke-CEs are not permitted to communicate with each other directly. Data transmission between
them depends on the hub-CE.
Configure EBGP to exchange VPN routing information between spoke-CE and spoke-PE, and between
hub-CE and hub-PE.
Direct 0
Direct 0
Destinations : 5
Proto Pre
BGP 255
BGP 255
Direct 0
Direct 0
BGP 255
Direct 0
Direct 0
data bytes, press CTRL_C to break
data bytes, press CTRL_C to break
0 127.0.0.1
0 127.0.0.1
Routes : 5
Cost NextHop
0 10.2.1.1
0 3.3.3.9
0 10.2.1.2
0 127.0.0.1
0 3.3.3.9
0 127.0.0.1
0 127.0.0.1
287
InLoop0
InLoop0
Interface
Vlan12
NULL0
Vlan12
InLoop0
NULL0
InLoop0
InLoop0