Bgp community configuration at the cli, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual

Page 509

Advertising
background image

484

{

From the output, 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; 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.

{

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 outgoing interface GE0/2.

3.

Configure load balancing:
Since SecPath A has two routes to reach AS 65009, configuring load balancing over the two BGP
routes on SecPath A can improve link utilization.
# Configure SecPath A.

[SecPathA] bgp 65008

[SecPathA-bgp] balance 2

[SecPathA-bgp] quit

4.

Verify the configuration:
# Display the BGP routing table on SecPath A.

[SecPathA] 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 NextHop MED LocPrf PrefVal Path/Ogn

*> 8.1.1.0/24 0.0.0.0 0 0 i

*> 9.1.1.0/24 3.1.1.1 0 0 65009i

*> 3.1.2.1 0 0 65009i

{

From the above output information, you can find two valid routes to the destination 9.1.1.0/24,
and both of them 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 with
next hop 3.1.1.1 and outgoing interface GE0/2, the other with next hop 3.1.2.1 and outgoing

interface GE0/3.

BGP community configuration at the CLI

Network requirements

As shown in

Figure 291

, SecPath B establishes EBGP connections with SecPath A and SecPath C.

Configure No_Export community attribute on SecPath A to make routes from AS 10 not advertised by AS

20 to any other AS.

Advertising