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

NE40E V800R010C10SPC500 Feature Description - IP Services 01

This is NE40E V800R010C10SPC500 Feature Description - IP Services
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).
ECMP and UCMP

ECMP and UCMP

Route load balancing can be classified as Equal-Cost Multiple Path (ECMP) or Unequal-Cost Multiple Path (UCMP).

ECMP

ECMP evenly load-balances traffic over multiple equal-cost paths to a destination, irrespective of bandwidth. Equal-cost paths have the same cost to the destination.

When the bandwidth of these paths differs greatly, the bandwidth usage is low. On the network shown in Figure 8-7, traffic is load-balanced over three paths, with the bandwidth of 10 Mbit/s, 20 Mbit/s, and 30 Mbit/s, respectively. If ECMP is used, the total bandwidth can reach 30 Mbit/s, but the bandwidth usage can only be 50%, the highest.

Figure 8-7 ECMP networking

UCMP

UCMP load-balances traffic over multiple equal-cost paths to a destination based on bandwidth ratios. All paths carry traffic based on their bandwidth ratios. As shown in Figure 8-8. This increases bandwidth usage.

Figure 8-8 UCMP networking
NOTE:

Trunk load balancing does not have ECMP or UCMP, but has similar functions. For example, if interfaces of different rates, for example, GE and FE interfaces, are bundled into a trunk interface, and weights are assigned to the trunk member interfaces, traffic can be load-balanced over trunk member links based on link weights. This is implemented in a similar way as UCMP. By default, the trunk member interfaces have the same weight of 1. The default implementation is similar to ECMP, but all member interfaces can only have the lowest forwarding capability among all.

Additional Explanation of UCMP

  • Currently, only per-flow load balancing is supported by UCMP. If both UCMP and per-packet load balancing are configured, per-packet load balancing with ECMP takes effect.
  • Among the paths used for UCMP, the bandwidth of each path must be higher than or equal to 1/16 of the total bandwidth; otherwise, the path carries no traffic.
  • The interfaces that support UCMP are Ethernet interfaces, GE interfaces, POS interfaces, IP-Trunk interfaces, Eth-Trunk interfaces, and TE tunnel interfaces.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055041

Views: 11245

Downloads: 50

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