The load-balance unequal-cost weight command sets a weight for a link before unequal cost multiple path (UCMP) is carried out among links.
The undo load-balance unequal-cost weight command restores the default weight for a link.
By default, the UCMP weight of each link is 0 after UCMP is enabled globally.
Usage Scenario
On an existing MPLS network, devices in the core area support TE, and devices in other areas use LDP. LDP over TE applies and allows a TE tunnel to function as a hop on an entire LDP LSP. On MPLS VPNs where LDP is widely used, LDP over TE is used to prevent VPN traffic congestion on some nodes. If multiple tunnels on a transit node have the same downstream node, load balancing can be configured on the transit node. This allows each link to carry traffic based on the proportion of the specific weight to the total weight.
Prerequisites
The load-balance unequal-cost enable command has been run to enable UCMP globally before any UCMP-associated commands are used.
Configuration Impact
The load-balance unequal-cost weight command takes effect 10 minutes after being run.
Precautions
Note the following issues when configuring UCMP weights:
<HUAWEI> system-view [~HUAWEI] mpls [*HUAWEI-mpls] mpls te [*HUAWEI-mpls] quit [*HUAWEI] load-balance unequal-cost enable [*HUAWEI] interface Tunnel 10 [*HUAWEI-Tunnel10] tunnel-protocol mpls te [*HUAWEI-Tunnel10] load-balance unequal-cost weight 12