What is the difference between the static LSP bound to the tunnel and the static CR-LSP

19

Switches of V200R002C00 or later support the static CR-LSP.

A static LSP is classified into the common LSP and static LSP bound to the tunnel. A static CR-LSP must be bound to the tunnel. A static CR-LSP requires bandwidth while a common static LSP does not require.

Other related questions:
Relationship between the actual setup and holding priorities of CR-LSP tunnels and the priority values
CR-LSP tunnels use the setup priority and holding priority to determine whether to preempt resources. The priority value ranges from 0 to 7. A smaller value allows for a higher priority. The setup priority must be lower than or equal to the holding priority for a tunnel. The priority and the preemption attributes are used together to determine resource preemption among tunnels. If multiple CR-LSP tunnels are to be established, CR-LSP tunnels with higher priorities can be established by preempting resources. When the bandwidth is insufficient, resources of an established LSP tunnel with a lower holding priority may be preempted by an LSP tunnel with a higher setup priority.

How to configure static LSPs on S series switches
For static LSP configuration on S series switches (except the S1700), see "CLI-based Configuration > Configuration Guide - MPLS > Static LSP Configuration > Configuration Examples > Example for Configuring Static LSPs" in S7700&S9700 V200R010C00 Product Documentation. Configurations on different models are the same, and configurations on the S7700 and S9700 are used as examples.

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.

How to import traffic to a TE tunnel on S series switches
For S series switches (except the S1700), use either of the following methods to import traffic to the TE tunnel: - Configure static routes. For example, after you run the ip route-static 10.0.0.0 24 tunnel1/0/0 command, traffic destined for 10.0.0.0/8 is forwarded through Tunnel1/0/0. - Configure auto routes in IGP shortcut mode. After the auto routes are configured in IGP shortcut mode, TE tunnels act as logical links to participate in IGP route calculation and tunnel interfaces are used as the outbound interfaces of the ingress routers, and do not affect the IGP route calculation by other routers.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top