The Nokia Multiprotocol Label Switching (MPLS) router with Resource Reservation Protocol - Traffic Engineering (RSVP-TE) enabled must be configured with message pacing or refresh reduction to adjust the maximum number of RSVP messages to an output queue based on the link speed and input queue size of adjacent core routers.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-283860 | NOKI-RT-000420 | SV-283860r1203829_rule | CCI-001095 | low |
| Description | ||||
| RSVP-TE can be used to perform constraint-based routing when building label-switched path (LSP) tunnels within the network core that will support quality of service and traffic engineering requirements. RSVP-TE is also used to enable MPLS Fast Reroute, a network restoration mechanism that will reroute traffic onto a backup LSP in case of a node or link failure along the primary path. When there is a disruption in the MPLS core, such as a link flap or router reboot, the result is a significant amount of RSVP signaling, such as "PathErr" and "ResvErr" messages that need to be sent for every LSP using that link. When RSVP messages are sent either hop by hop or with the router alert bit set in the IP header. This means that every router along the path must examine the packet to determine if additional processing is required for these RSVP messages. If there is enough signaling traffic in the network, an interface could receive more packets for its input queue than it can hold, resulting in dropped RSVP messages and slower RSVP convergence. Increasing the size of the interface input queue can help prevent dropping packets; however, there is still the risk of having a burst of signaling traffic that can fill the queue. Solutions to mitigate this risk are RSVP message pacing or refresh reduction to control the rate at which RSVP messages are sent. RSVP refresh reduction includes the following features: RSVP message bundling, RSVP Message ID to reduce message processing overhead, reliable delivery of RSVP messages using Message ID, and summary refresh to reduce the amount of information transmitted during every refresh interval. | ||||
| STIG | Date | |||
| Nokia Service Router OS 25.x Router Security Technical Implementation Guide | 2026-06-15 | |||
Details
Check Text (C-283860r1203829_chk)
Review the Nokia router configuration to verify the router has been configured to prevent a burst of RSVP traffic engineering signaling messages from overflowing the input queue of any neighbor core router.
Use the command below and verify "Message Pacing" is enabled:
- show router rsvp status | match "Message Pacing" post-lines 1
Message Pacing : Enabled Pacing Period : 200 msec
Max Packet Burst : 200 msgs Refresh Bypass : Disabled
If the router with RSVP-TE enabled does not have message pacing configured based on the link speed and input queue size of adjacent core routers, this is a finding.
Fix Text (F-88330r1203828_fix)
Ensure all routers with RSVP-TE enabled have message pacing configured that will adjust maximum burst and maximum number of RSVP messages to an output queue based on the link speed and input queue size of adjacent core routers.
Configure to enable message pacing for RSVP with a specified number of RSVP messages in the max-burst command, as shown in the example below:
- configure router rsvp msg-pacing max-burst 200
- configure router rsvp msg-pacing period 200