RSVP Path Error Signaling for Network Device Reboot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for handling a restarting network device lead to traffic outages due to the consumption of computing and networking resources when a single link is utilized for traffic, causing bandwidth reduction and customer complaints, as LSPs are not effectively managed during the reboot process.
Innovation Solution
A network device receives RSVP path request messages, generates an RSVP path error message with an overload error code and timeout period after coming online, causing core network devices to wait until the device is fully online before resending requests, thereby delaying RSVP LSP signaling and preventing overloading of links.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If RSVP path request messages are immediately processed after network device restart, then LSP signaling is faster, but network resources are overloaded and traffic outages occur
Solution Approach 1:
The network device performs preliminary actions by setting up an event-driven architecture before normal operation. The event listener is pre-configured to monitor for restart events, and the timeout mechanism is pre-established. When a restart event occurs, the system immediately activates the delayed signaling response without requiring complex real-time decisions, thus preventing resource overload while maintaining reliable LSP establishment.
2Reliability
If RSVP path request messages are delayed after network device restart, then network resources are conserved, but LSP setup time increases
Solution Approach 1:
The system dynamically adjusts its behavior based on the operational state of the network device. During restart, signaling is delayed using a timeout mechanism to conserve resources. Once the device is fully online and stable, the system transitions to normal operation where LSP signaling proceeds without artificial delays. This dynamic state-based approach optimizes both resource conservation and signaling efficiency at different operational phases.
3Adaptability or versatility
If all LSP paths are established simultaneously after reboot, then resource distribution is fair, but computing and networking resources are overwhelmed
Solution Approach 1:
The system implements periodic action through a timeout-based rate limiting mechanism. Instead of processing all RSVP path request messages simultaneously, the system spaces out the processing of LSP signaling over a defined timeout period. This periodic approach ensures that computing and networking resources are not overwhelmed while still establishing all necessary LSP paths, achieving a balance between resource conservation and complete path establishment.
Data Source
AI summary
A network device may receive RSVP path request messages from an upstream ingress network device, and may generate an RSVP path error message, with an overload error code and a timeout period, after the network device is online within the configured timeout period. The network device may provide the RSVP path error message to the ingress network devices to cause the ingress network devices to wait for expiration of the timeout period, after the network device is fully online, until resending the RSVP path request messages. The network device may receive new RSVP path request messages from the ingress network devices after expiration of the timeout period after the network device is fully online, and may establish, based on the new RSVP path request messages, label-switched paths from the ingress network devices.