Bgp Community Configuration - H3C S5800 Series Configuration Manual

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, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Network
*> 8.1.1.0/24
*> 9.1.1.0/24
*>
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.
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 next hop 3.1.2.1 and
outbound interface VLAN-interface 300.

BGP Community Configuration

Network requirements
As shown in the following figure, 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.
Figure 6-23 Network diagram for BGP community configuration
Configuration procedure
1) Configure IP addresses for interfaces (omitted)
2) Configure eBGP
NextHop MED
0.0.0.0 0
3.1.1.1 0
3.1.2.1 0
6-57
LocPrf PrefVal Path/Ogn
0 i
0 65009i
0 65009i