What are the reasons for the static LSP's failure in becoming Up

A static LSP is classified into the common static LSP, static LSP bound to the tunnel, and static CR-LSP bound to the tunnel.

Switches of V200R002C00 or later support MPLS TE.

Each node checks the command configuration of a common static LSP. The common static LSP fails to be configured in any of the following situations:
MPLS is not enabled globally.
The static LSP with the same name exists.
The static LSP with the same destination address and the same outbound interface (next hop) exists.
The static LSP with the same incoming label exists.
The configured next hop address is not the actual next hop address in the routing table.
Each node checks the command configuration of a static LSP bound to the tunnel. The static LSP bound to the tunnel fails to be configured in any of the following situations:
MPLS is not enabled globally.
MPLS TE is not enabled globally.
On the ingress node, the bound tunnel does not exist or is not configured.
The static LSP with the same name exists.
The static LSP with the same destination address and the same outbound interface (next hop) exists.
The static LSP with the same incoming label exists.
The configured next hop address is not the actual next hop address in the routing table.
Each node checks the command configuration of a static CR-LSP bound to the tunnel. The static CR-LSP bound to the tunnel fails to be configured in any of the following situations:
MPLS is not enabled globally.
MPLS TE is not enabled globally.
On the ingress node, the bound tunnel does not exist or is not configured.
The static LSP with the same name exists.
The static LSP with the same destination address and the same outbound interface (next hop) exists.
The static LSP with the same incoming label exists.
The configured next hop address is not the actual next hop address in the routing table.

Scroll to top