3Com S7906E Configuration Manual page 822

# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp] router-id 3.3.3.3
[SwitchC-bgp] peer 3.1.2.2 as-number 65008
[SwitchC-bgp] peer 2.2.2.2 as-number 65009
[SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0
[SwitchC-bgp] network 9.1.1.0 255.255.255.0
[SwitchC-bgp] quit
[SwitchC] ip route-static 2.2.2.2 32 9.1.1.1
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table
Total Number of Routes: 3
BGP Local router ID is 1.1.1.1
Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,
h - history,
Origin : i - IGP, e - EGP, ? – incomplete
Network
*> 8.1.1.0/24
*> 9.1.1.0/24
*
From the above output information, you can find two valid routes to destination 9.1.1.0/24: the route
with next hop 3.1.1.1 is 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 only 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 to 9.1.1.0/24 with next
hop 3.1.1.1 and outbound interface VLAN-interface 200.
3) Configure loading balancing
Since Switch A has two routes to reach AS 65009, configuring load balancing over the two BGP routes
on Switch A can improve link utilization.
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp] balance 2
[SwitchA-bgp] quit
4) Verification
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table
Total Number of Routes: 3
BGP Local router ID is 1.1.1.1
Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,
h - history,
Origin : i - IGP, e - EGP, ? - incomplete
Network
*> 8.1.1.0/24
*> 9.1.1.0/24
*>
i - internal, s - suppressed, S - Stale
NextHop MED
0.0.0.0 0
3.1.1.1 0
3.1.2.1 0
i - internal, s - suppressed, S - Stale
NextHop MED
0.0.0.0 0
3.1.1.1 0
3.1.2.1 0
1-53
LocPrf PrefVal Path/Ogn
0 i
0 65009i
0 65009i
LocPrf PrefVal Path/Ogn
0 i
0 65009i
0 65009i