238
Network NextHop MED LocPrf PrefVal Path/Ogn
> 8.1.1.0/24 8.1.1.1 0 0 i
>e 9.1.1.0/24 3.1.1.1 0 0 65009i
* e 3.1.2.1 0 0 65009i
{ T h e o u t p u t s h o w s t w o v a l i d r o u t e s t o d e s t i n a t i o n 9.1.1.0 / 24 . T h e ro u t e w i t h n e x t h o p 3.1.1.1 i s
marked with a greater-than sign (>), indicating it is the best route (because the ID of Switch B is
smaller). The route with next hop 3.1.2.1 is marked with an asterisk (*), indicating it is a valid
route, but not the best.
{ By using the display ip routing-table command, you can find only one route to 9.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 the two
BGP routes on Switch A can improve link usage.
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp] ipv4-family 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 - damped, 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 0 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.
To Next Page
Loading...
