Configuring an LDP Entropy Label on the Ingress of an LSP

An LDP entropy label can be configured on the ingress of an LSP to load-balance traffic.

Context

The growth of user networks worsens the load imbalance on transit nodes. To address this problem, the entropy label capability can be configured on the ingress. An LDP entropy label is configured on the ingress of an LSP, and an LDP tunnel with the entropy label capability enabled is negotiated using LDP. Then forwarding entries carry the flag supporting the entropy label capability to implement load balancing.

Procedure

Run system-view
The system view is displayed.
Run mpls ldp
The MPLS-LDP view is displayed.
Run entropy-label enable
An LDP entropy label is configured on the ingress of an LSP.
(Optional) Run entropy-label negotiate primary-lsp-only [ ip-prefix ip-prefix-name ]
LDP is configured to negotiate the entropy label capability only based on the primary LSP.

If there are primary and backup paths, you can perform this step on the ingress or transit node of an LSP to prevent an LDP tunnel entropy label negotiation failure.
Run commit
The configuration is committed.