Operation Manual – MPLSH3C S9500 Series Routing Switches Chapter 3 BGP/MPLS VPN Configuration3-38[PE-B] bgp 100[PE-B-bgp] group 20[PE-B-bgp] peer 20.1.1.1 group 20[PE-B-bgp] peer 20.1.1.1 connect-interface loopback 0[PE-B-bgp] ipv4-family vpnv4[PE-B-bgp-af-vpn] peer 20 enable[PE-B-bgp-af-vpn] peer 20.1.1.1 group 20[PE-B-bgp-af-vpn] quit3.4.3 Hub&Spoke Configuration ExampleI. Network requirementsHub&Spoke networking is also called central server networking. The Site in the centeris called Hub-Site, while the one not in the center is called Spoke-Site. The Hub-Siteknows the routes to all other Sites in the same VPN, and the Spoke-Site must send itstraffic first to the Hub-Site and then to the destination. Hub-Site is the central node ofSpoke-Sites.A bank has a headquarters network and subsidiary networks, and it requires that thesubsidiaries cannot directly exchange data with each other, but they can exchange datathrough the headquarters network which provides uniform control. In this case,Hub&Spoke networking topology is used: CE2 and CE3 are spoke-sites, while CE1 is ahub-site in the bank data center. CE1 controls communication between CE2 and CE3.z Set up IBGP adjacency between PE1 and PE2 or PE1 and PE3, but not betweenPE2 and PE3, that is, VPN routing information cannot be exchanged between PE2and PE3.z Create two VPN-instances on PE1, import VPN routes of VPN-target 100:11 and100:12, set VPN-target for VPN routes advertised as 100:2.z Create a VPN-instance on PE2, import VPN routes of VPN-target 100:2, setVPN-target for VPN routes advertised as 100:11.z Create a VPN-instance on PE3, import VPN routes of VPN-target 100:2, setVPN-target for VPN routes advertised as 100:12.Then PE2 and PE3 can only learn their neighbor’s routes through PE1.
