No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - IP Unicast Routing

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring BGP Load Balancing

Configuring BGP Load Balancing


On large networks, there may be multiple valid routes to the same destination. BGP, however, advertises only the optimal route to its peers. This may result in unbalanced traffic on different routes. Configuring BGP load balancing enables traffic to be load balanced and network congestion to be reduced.

Equal-cost BGP routes can only be generated for traffic load balancing when the first eight route attributes described in "BGP Route Selection Policies" are the same. Change load balancing rules by adjusting some configurations, for example, ignoring the comparison of the AS_Path attribute. When adjusting these configurations, ensure that these configurations do not result in routing loops.

Local cross routes and routes imported between public network and VPN instances do not support load balancing.

If BGP load balancing is configured, the local device changes the next-hop address of routes to its address when advertising routes to IBGP peer groups, regardless of whether the peer next-hop-local command is used.


  1. Run system-view

    The system view is displayed.

  2. Run bgp { as-number-plain | as-number-dot }

    The BGP view is displayed.

  3. Enter the corresponding address family view based on network type to configure BGP devices on networks.

    • Run ipv4-family { unicast | multicast }

      The IPv4 address family view is displayed.

    • Run ipv6-family [ unicast ]

      The IPv6 address family view is displayed.

  4. Run maximum load-balancing [ ebgp | ibgp ] number [ ecmp-nexthop-changed ]

    The maximum number of BGP routes to be used for load balancing is set.

    By default, the maximum number of BGP routes to be used for load balancing is 1, indicating that load balancing is not implemented.

    • On a public network, if the routes to the same destination implement load balancing, the system will determine the optimal route type. If the optimal routes are IBGP routes, only IBGP routes carry out load balancing. If the optimal routes are EBGP routes, only EBGP routes carry out load balancing. This means that load balancing cannot be implemented among IBGP and EBGP routes with the same destination address.

    Configuring BGP not to compare the AS_Path attributes of the routes to be used for load balancing may cause routing loops.

  5. (Optional) Run load-balancing as-path-ignore

    BGP is configured not to compare the AS_Path attributes of the routes to be used for load balancing.

    By default, BGP compares the AS_Path attributes of the routes to be used for load balancing.

Updated: 2019-12-27

Document ID: EDOC1000174069

Views: 188973

Downloads: 316

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next