Client-Server Protocol for NOS Image Compatibility Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed router systems face significant downtime and interruptions due to the need for manual rescheduling of network operating system (NOS) upgrades, which can lead to inconvenient scheduling, human errors, and unexpected network traffic surges, while conventional methods require multiple reboots and version checks during boot sequences, disrupting uptime and throughput.
Innovation Solution
Implementing a client-server transaction protocol that uses software image signatures to verify compatibility of NOS image versions, allowing nodes to boot from local storage or network interfaces based on compatibility determination, reducing the need for forced reboots and minimizing downtime by determining necessary upgrades without interrupting node operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual rescheduling of NOS upgrades is performed, then upgrade scheduling flexibility is improved, but human errors and scheduling delays occur
Solution Approach 1:
The system performs self-service by automatically checking NOS image compatibility through software image signatures during the boot sequence, eliminating the need for manual rescheduling operations and associated human errors
Solution Approach 2:
The compatibility verification is performed in advance during the boot sequence before the NOS image is fully loaded, allowing the system to determine boot source requirements beforehand and avoid scheduling delays
2Reliability
If multiple reboots and version checks are performed during boot sequences, then NOS image compatibility is verified, but uptime and throughput are disrupted
Solution Approach 1:
The patent extracts the compatibility verification process from the traditional multiple-reboot sequence and integrates it into a single boot sequence operation, using software image signatures to determine boot source requirements without requiring multiple reboots
Solution Approach 2:
The system skips unnecessary reboot cycles by determining compatibility upfront through software image signature verification, rushing through the boot sequence efficiently once compatibility is confirmed
3Reliability
If forced reboots are implemented to verify compatibility, then NOS image compatibility is ensured, but downtime increases
Solution Approach 1:
The software image signature verification is performed preliminarily during the boot sequence to determine compatibility before full NOS image loading, ensuring compatibility assurance while minimizing the time the system remains in a non-operational state
Data Source
AI summary
This disclosure describes techniques for verifying compatibility of NOS image versions during startup of one or more hardware modules of a distributed router system. A client-server transaction protocol is executed between a communication server and a communication client configured according to the protocol to run on hardware modules of a distributed router system. A communication client discovers a communication server through a handshake transaction and sends a software image signature of an NOS image version. The communication server forwards the software image signature to an NOS verification server to determine whether the software image signature is compatible. Further, the communication server instructs the communication client to cause the hardware module hosting the communication client to boot either from a network interface or from local storage, at least in part on the determination of compatibility by the verification server, reducing numbers of reboots and increasing uptime and throughput of the system.