[PE2-bgp] peer 1.1.1.9 connect-interface loopback 0
[PE2-bgp] address-family vpnv4
[PE2-bgp-vpnv4] peer 1.1.1.9 enable
[PE2-bgp-vpnv4] quit
[PE2-bgp] quit
# Execute the display bgp peer vpnv4 command on the PEs to verify that a BGP peer relationship
in Established state has been established between the PEs. (Details not shown.)
Verifying the configuration
# Execute the display ip routing-table vpn-instance command on the PEs.
[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
The output shows that PE 1 has a route to the remote CE. Output on PE 2 is similar.
# Verify that 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). (Details not shown.)
Configuring a hub-spoke network
Network requirements
The Spoke-CEs cannot communicate directly. They can communicate only through Hub-CE.
Configure EBGP between the Spoke-CEs and Spoke-PEs and between Hub-CE and Hub-PE to exchange
VPN routing information.
Configure OSPF between the Spoke-PEs and Hub-PE to implement communication between the PEs, and
configure MP-IBGP between them to exchange VPN routing information.
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
211
NextHop
Interface
127.0.0.1
InLoop0
10.1.1.2
Vlan11
10.1.1.2
Vlan11
127.0.0.1
InLoop0
10.1.1.2
Vlan11
3.3.3.9
Vlan13
127.0.0.1
InLoop0
127.0.0.1
InLoop0
127.0.0.1
InLoop0
127.0.0.1
InLoop0
0.0.0.0
NULL0
0.0.0.0
NULL0
127.0.0.1
InLoop0