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

Reminder

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

upgrade

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).
Configuring Principles for Using Equal-Cost IPv6 IS-IS Routes

Configuring Principles for Using Equal-Cost IPv6 IS-IS Routes

Context

If there are redundant IS-IS links, multiple routes may have an equal cost.

Configure load balancing for equal-cost IS-IS routes so that traffic will be evenly balanced among these links. This mechanism increases the link bandwidth usage and prevents network congestion caused by link overload. However, this mechanism may make traffic management more difficult because traffic will be randomly forwarded.

Procedure

  • Configure equal-cost IS-IS routes to work in load-balancing mode.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run ipv6 maximum load-balancing number

      The maximum number of load-balancing equal-cost IPv6 IS-IS routes is set.

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

      NOTE:
      When the number of equal-cost routes is greater than number specified in the ipv6 maximum load-balancing command, valid routes are selected for load balancing based on the following criteria:
      1. Route preference: Routes with higher preferences are selected for load balancing.
      2. Interface index: If routes have the same priorities, routes with higher interface index values are selected for load balancing.
      3. Next hop IP address: If routes have the same priorities and interface index values, routes with larger IP address are selected for load balancing.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 55126

Downloads: 62

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