286indicating it is the best route (because the ID of Switch B is smaller); the route with next hop3.1.2.1 is marked with an asterisk (*), indicating it is a valid route, but not the best.Using the display ip routing-table command, you can find only one route to9.1.1.0/24 with next hop 3.1.1.1 and outbound interface VLAN-interface 200.3. Configure loading balancing.Because Switch A has two routes to reach AS 65009, configuring load balancing over thetwo BGP routes on Switch A can improve link utilization.a. Configure Switch A.[SwitchA] bgp 65008[SwitchA-bgp] balance 2[SwitchA-bgp] quit4. Verify the configuration.a. Display the BGP routing table on Switch A.[SwitchA] display bgp routing-tableTotal Number of Routes: 3BGP Local router ID is 1.1.1.1Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,h - history, i - internal, s - suppressed, S - StaleOrigin : i - IGP, e - EGP, ? - incompleteNetwork NextHop MED LocPrf PrefValPath/Ogn*> 8.1.1.0/24 0.0.0.0 0 0 i*> 9.1.1.0/24 3.1.1.1 0 065009i*> 3.1.2.1 0 065009iThe route 9.1.1.0/24 has two next hops, 3.1.1.1 and 3.1.2.1, both of which are markedwith a greater-than sign (>), indicating they are the best routes.Using the display ip routing-table command, you can find two routes to 9.1.1.0/24:one with next hop 3.1.1.1 and outbound interface VLAN-interface 200, the other with nexthop 3.1.2.1 and outbound interface VLAN-interface 300.BGP community configurationNetwork requirementsIn Figure 92, Switch B establishes eBGP connections with Switch A and C. Configure No_Exportcommunity attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any otherAS.
