How to configure RSVP TE?

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.

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.

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.

To configure the Control Plane Committed Access Rate (CPCAR), perform the following operations: 1. Run the cpu-defend policy policy-name command to create an anti-attack policy. 2. Run the packet-type packet-type rate-limit rate-value command in the anti-attack policy view to control the rate for delivering packets to the CPU and set thresholds. 3. Run the cpu-defend-policy policy-name [ global | slot slot-id ] command to apply the anti-attack policy.