270
Because Switch A has two routes to reach AS 65009, configuring load balancing over the two
BGP routes on Switch A can improve link usage.
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp] address-family ipv4 unicast
[SwitchA-bgp-ipv4] balance 2
[SwitchA-bgp-ipv4] quit
[SwitchA-bgp] quit
Verifying the configuration
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 3
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 8.1.1.0/24 8.1.1.1 0 32768 i
* >e 9.1.1.0/24 3.1.1.1 0 0 65009i
* >e 3.1.2.1 0 0 65009i
• The route 9.1.1.0/24 has two next hops, 3.1.1.1 and 3.1.2.1, both of which are marked with a
greater-than sign (>), indicating they are the best routes.
• By using the display ip routing-table command, you can find two routes to 9.1.1.0/24. One has next
hop 3.1.1.1 and outbound interface VLAN-interface 200, and the other has next hop 3.1.2.1 and
outbound interface VLAN-interface 300.
BGP community configuration example
Network requirements
As shown in Figure 67, Switch B establishes EBGP connections with Switch A and C. Configure
NO_EXPORT community attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any
other AS.
To Next Page
Loading...
