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.


Configuration Guide - IP Unicast Routing

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.
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).
Setting the Maximum Number of Equal-Cost Routes

Setting the Maximum Number of Equal-Cost Routes


A CloudEngine 8800, 7800, 6800, and 5800 series switches supports load balancing among equal-cost routes. That is, you can configure multiple routes, which have the same destination and preference.


  1. Run system-view

    The system view is displayed.

  2. Run ospf [ process-id ]

    The OSPF process view is displayed.

  3. Run maximum load-balancing number

    By default, load balancing is supported and a maximum of 32 equal-cost routes on the CE5800 series switches excluding CE5880EI and CE6810LI, 128 equal-cost routes on the other modules can participate in load balancing.

    When the number of equal-cost routes is greater than the number specified in the maximum load-balancing command, OSPF selects valid routes for load balancing according to the following criteria:
    1. Route preference: Routes with higher preferences are selected for load balancing.
    2. Interface index: If routes have the same preference, routes with larger interface indexes are selected for load balancing.
    3. Next-hop IP address: If routes have the same preference and same interface index, routes with larger next-hop IP addresses are selected for load balancing.

  4. Run commit

    The configuration is committed.

Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 55168

Downloads: 62

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next