
314
Destinations : 3 Routes : 3
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 Direct 0 0 10.1.1.2 GE2/1/1
10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.0/24 BGP 255 0 2.2.2.9 NULL0
The CEs can ping each other.
[CE1] ping 10.2.1.1
PING 10.2.1.1: 56 data bytes, press CTRL_C to break
Reply from 10.2.1.1: bytes=56 Sequence=1 ttl=253 time=41 ms
Reply from 10.2.1.1: bytes=56 Sequence=2 ttl=253 time=69 ms
Reply from 10.2.1.1: bytes=56 Sequence=3 ttl=253 time=68 ms
Reply from 10.2.1.1: bytes=56 Sequence=4 ttl=253 time=68 ms
Reply from 10.2.1.1: bytes=56 Sequence=5 ttl=253 time=67 ms
--- 10.2.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 41/62/69 ms
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.
Configure OSPF between spoke-PE and hub-PE to ensure IP connectivity between PEs, and
configure MP-IBGP to exchange VPN routing information.
Figure 89 Network diagram
Device
Interface
IP address
Device
Interface
IP address
Spoke-CE 1
GE2/1/1
10.1.1.1/24 Hub-CE
GE2/1/1 10.3.1.1/24