No relevant resource is found in the selected language.
Your browser version is too early. Some functions of the website may be unavailable. To obtain better user experience, upgrade the browser to the latest version.
CloudEngine 12800 and 12800E V200R005C10 Configuration Guide - IP Unicast Routing
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.
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 IS-IS Routes
Configuring Principles for Using Equal-Cost IS-IS Routes
Context
If there are redundant IS-IS links, multiple routes may have an equal cost. Choose either of the following methods to use these equal-cost IS-IS routes:
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.
Configure preference values for equal-cost IS-IS routes so that only the route with the highest preference will be used and the others function as backups.
This configuration facilitates traffic management and improves the network reliability, without the need to change original configurations.
Procedure
Configure equal-cost IS-IS routes to work in load-balancing mode.
Run system-view
The system view is displayed.
Run isis [ process-id ]
The IS-IS view is displayed.
Run maximum load-balancingnumber
The maximum number of load-balancing equal-cost IS-IS routes is set.
By default, load balancing is supported and a maximum of 128 equal-cost routes can participate in load balancing.
When the number of equal-cost routes is greater than number specified in the maximum load-balancing command, valid routes are selected for load balancing based on the following criteria:
Route preference: Routes with higher preferences are selected for load balancing.
Interface index: If routes have the same priorities, routes with higher interface index values are selected for load balancing.
Next hop IP address: If routes have the same priorities and interface index values, routes with larger IP address are selected for load balancing.
Run commit
The configuration is committed.
Configure preference values for equal-cost IS-IS routes.
Run system-view
The system view is displayed.
Run isis [ process-id ]
The IS-IS view is displayed.
Run nexthopip-addressweightvalue
A preference value is configured for an equal-cost IS-IS route.
By default, no preference is set for equal-cost IS-IS routes. A smaller value indicates a higher priority.