How are RSVP-TE path messages forwarded on the MPLS network

5

Generally, RSVP-TE Path messages are forwarded on the MPLS network using IP routes. In the scenario where the primary CR-LSP is faulty (that is, the primary CR-LSP is in FRR in-use state) and the TE FRR bypass tunnel is used, RSVP-TE Path messages are forwarded over the TE tunnel.

Other related questions:
How can the AR router forward RSVP-TE Path packets on the MPLS network
Generally, Path messages of RSVP-TE are forwarded based on IP routes on the MPLS network. In the scenario where FRR is used, when the primary CR-LSP is faulty, the system starts the TE FRR bypass tunnel. Path messages are forwarded over the TE tunnel.

How to check the path of an MPLS TE tunnel on S series switches
For S series switches (except the S1700), run the display mpls te tunnel path command to check the path of an MPLS TE tunnel after the mpls te record-route label command is configured in the tunnel view. display mpls te tunnel path Tunnel Interface Name : Tunnel6/0/0 Lsp ID : 23.23.23.23 :2 Hop Information Hop 0 3.23.24.1 Hop 1 3.23.24.2 Label 1024 Hop 2 2.2.2.2

Does an AR support MPLS TE
Support for MPLS TE: - The AR120&AR150&AR160&AR200&AR500&AR510 do not support MPLS TE. - The AR120-S&AR150-S&AR160-S&AR200-S do not support MPLS TE. Other -S models support MPLS TE starting from V200R005C10. - The AR530 and AR550 do not support MPLS TE. - Other models support MPLS TE starting from V200R002C01.

How to configure MPLS TE on S series switches
Multiprotocol Label Switching Traffic engineering (MPLS TE) can prevent congestion caused by improper resource allocation by allocating some traffic to idle links, allowing network traffic to be allocated properly. The MPLS TE configurations on different switch models are the same. For details, see "CLI-based Configuration > Configuration Guide - MPLS > MPLS TE Configuration" in S7700&S9700 V200R010C00 Product Documentation.

Rules to be followed for planning TE explicit paths
Loose and strict explicit paths are usually used in TE path planning. When configuring an explicit path, you can define a node that traffic must pass through or a node that traffic must bypass. Parameter include means that an LSP must pass through a specified node. Parameter exclude means that an LSP cannot pass through a specified node. When configuring a strict explicit path, you must specify the next hop and ensure that the next hop is directly connected to its upstream node. A loose explicit path allows other nodes to exist between the source and sink. In the IP RAN solution, loose explicit paths are usually used to facilitate future node addition or deletion. When planning an explicit path for an LSP, note the following rules: 1. The explicit path must not pass through the destination device. In other words, if you have specified a node that an explicit path must pass through, then the explicit path must pass through this node before reaching the sink. 2. The explicit path must not pass through a path twice. 3. Among multiple paths between two nodes that an LSP must pass through, the explicit path uses the one with the lowest IGP cost. If you do not specify any node for the explicit path to pass through, the explicit path uses the path with the lowest IGP cost between the source and sink. 4. When overlapping is enabled, the primary and secondary paths try their best to avoid sharing the same path, but may share the same node. It is recommended that you use the outbound interface IP address of the source or sink for route restriction. If you want to exclude multiple paths from an LSP, specify the intermediate nodes that need to be excluded besides specifying the outbound interface IP address of the source or sink. When configuring explicit paths, you are also advised to configure overlapping, route re-optimization, and automatic hot-standby backup path computation.

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