How can the AR router forward RSVP-TE Path packets on the MPLS network

2

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.

Other related questions:
How are RSVP-TE path messages forwarded on the MPLS network
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.

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.

Which status do MSTP interfaces of an AR router have and how do they process packets
MSTP interface status: - Forwarding: In this state, an interface forwards user traffic. Only the root interface or a specified interface can be in this state. - Learning: This is a transitional state. In this state, a switch will build a MAC address table according to the user traffic it receives (but not forward the user traffic). That is why this state is referred to as a learning state. - Discarding: In this state, an interface blocks packets and does not learn MAC addresses.

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

What are functions of RSVP
The Resource Reservation Protocol (RSVP) is designed for the integrated services model, and reserves resources for nodes along a path. This bandwidth reservation capability makes RSVP-TE a suitable signaling protocol for establishing MPLS TE paths. RSVP supports the following resource reservation styles: - Fixed Filter (FF) style: creates an exclusive reservation for each sender. A sender does not share its resource reservation with other senders, and each CR-LSP on a link has a separate resource reservation. - Shared Explicit (SE) style: creates a single reservation for a series of selected upstream senders. CR-LSPs on a link share the same resource reservation. RSVP key authentication can prohibit an unauthorized node from setting up the RSVP neighbor relationship with the local node and prevent packet spoofing. Key authentication cannot prevent replay attacks. Authentication enhancements are used to prevent replay attacks. RSVP authentication enhancements add the authentication lifetime, handshake, and message window mechanisms to enhance RSVP security. The enhancements also improve RSVP's capability to verify neighbor relationships in a harsh network environment, such as a congested network.

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