peer load-balancing (BGP-IPv4 multicast address family view) (group)

Function

The peer load-balancing command enables MBGP peer group based load balancing.

The undo peer load-balancing command restores the default configuration.

By default, MBGP load balancing is not enabled.

Format

peer peerGroupName load-balancing [ as-path-ignore | as-path-relax ]

undo peer peerGroupName load-balancing [ as-path-ignore | as-path-relax ]

Parameters

Parameter Description Value
peerGroupName

Specifies the name of an MBGP peer group.

The value is a string of 1 to 47 case-sensitive characters, spaces not supported.

as-path-ignore

Prevents the router from comparing AS_Path attributes when selecting routes for load balancing.

-

as-path-relax

Configures the device to ignore comparing the AS_Path attributes of the same length when selecting routes for load balancing.

-

Views

BGP-IPv4 multicast address family view

Default Level

2: Configuration level

Task Name and Operations

Task Name Operations
bgp write

Usage Guidelines

Usage Scenario

On large networks, there may be multiple valid routes to the same destination. MBGP, however, advertises only the optimal route to its peers. This may result in unbalanced traffic on different routes. To prevent this problem, configure load balancing.

After the peer load-balancing command is run, BGP peer-based load balancing is implemented only when the following conditions are met:

  • The routes are received from the specified peer or peer group.
  • The optimal route and optimal equal-cost routes exist.
  • The AS_Path attribute is the same as that of the optimal route, or as-path-ignore or as-path-relax is specified in the peer load-balancing command.
  • a.If as-path-ignore is specified, the device ignores comparing AS_Path attributes when selecting routes for load balancing. In this case, routes can participate in load balancing even if their AS_Path attributes are different.
  • b.If as-path-relax is specified, the device ignores comparing the AS_Path attributes of the same length when selecting routes for load balancing. In this case, routes cannot participate in load balancing if their AS_Path attributes are of different lengths. For example, the AS_Path attribute of route A is 10, and the AS_Path attribute of route B is 10, 20. Because the two AS_Path attributes are of different lengths, the two routes cannot participate in load balancing.

Precautions

The maximum load-balancing and the peer load-balancing commands are mutually exclusive.

Example

# Enable MBGP route load balancing based on peer groups test1 and test2.
<HUAWEI> system-view
[~HUAWEI] bgp 100
[*HUAWEI-bgp] group test1 internal
[*HUAWEI-bgp] group test2 internal
[*HUAWEI-bgp] ipv4-family multicast
[*HUAWEI-bgp-af-multicast] peer test1 enable
[*HUAWEI-bgp-af-multicast] peer test2 enable
[*HUAWEI-bgp-af-multicast] peer test1 load-balancing
[*HUAWEI-bgp-af-multicast] peer test2 load-balancing
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >