Licensing Requirements and Limitations for MPLS TE

Other network elements are not required.

MPLS TE is a basic feature of a switch and is not under license control.

Only the following switch models support MPLS TE:

S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731S-H, S5732-H, S6720-EI, S6720-HI, S6720S-EI, S6730S-H, and S6730-H

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

When configuring MPLS TE on the switch, pay attention to the following points:

In V200R003 and earlier versions, only VLANIF interfaces support MPLS TE. In V200R005 and later versions, both VLANIF interfaces and Layer 3 Ethernet interfaces support MPLS TE.
On the S5720-EI switch, if hardware support for MPLS is displayed as NO in the output of the display device capability command, the switch does not support MPLS. In this case, you need to pay attention to the following points:
- MPLS cannot be enabled on the S5720-EI switch. If the switch has been added to a stack, MPLS cannot be enabled on the stack.
- The S5720-EI switch cannot be added to a stack running MPLS.

When configuring TE FRR on the switch, pay attention to the following points:

Dynamic TE tunnels using bandwidth reserved in Shared Explicit (SE) style support TE FRR, but static TE tunnels do not.
For the S5720-EI, S6720-EI, and S6720S-EI, if TE FRR is enabled in a scenario where MPLS TE tunnels transmit VPN services, you must configure PHP when the MP node is the egress node of the primary CR-LSP.
In V200R005 and earlier versions, TE FRR can be performed during the RSVP GR process. This protects traffic on the primary tunnel and speeds up troubleshooting in the situation where a traffic switchover or a reboot is triggered after a fault occurs on a PLR, the PLR's upstream node, an MP, or the MP's downstream node, while the outbound interface of a primary tunnel on the PLR fails. During the RSVP GR process, FRR switching is triggered if the outbound interface of a primary tunnel on the PLR goes Down.

When configuring tunnel protection groups on the switch, pay attention to the following points:

A tunnel protection group works in either 1:1 or N:1 mode. The 1:1 mode enables a protection tunnel to protect only one working tunnel. The N:1 mode enables a protection tunnel to protect multiple working tunnels. In a tunnel protection group, a maximum of 16 primary tunnels can be protected.
Tunnel-specific attributes in a tunnel protection group are independent from each other. For example, a protection tunnel with the bandwidth 50 Mbit/s can protect a working tunnel with the bandwidth 100 Mbit/s.
Besides configuring a tunnel protection group to protect the working tunnel, you can configure TE FRR on the working tunnel in the protection group for dual protection to the working tunnel.

A tunnel protection group and TE FRR cannot be configured simultaneously on the ingress node of a primary tunnel.
A protection tunnel cannot be protected by other tunnels or be enabled with TE FRR.

When configuring BFD for MPLS TE on the switch, pay attention to the following points:

BFD can detect faults in static and dynamic CR-LSPs.
BFD for LSP can function properly even if the forward and backward forwarding modes are different. (For example, the forward path is an LSP and the backward path is an IP link.) The forward path and the backward path must be established over the same link; otherwise, if a fault occurs, BFD cannot identify the faulty path. Before deploying BFD, ensure that the forward and backward paths are over the same link so that BFD can correctly identify the faulty path.