Processor Configuration Synchronization During Software Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In systems with redundant processors, such as network routers, software upgrades can lead to configuration mismatches between Active and Standby processors running different operating system versions, causing potential service disruptions during switchover, as commands may succeed on one version but fail or produce different results on another.
Innovation Solution
Implementing configuration synchronization methods, including bulk synchronization and line-by-line synchronization processes, to ensure that both processors understand and execute the same commands, with error handling and user notification for resolving mismatches, and utilizing lists like Mismatched Ignore List and Don't Care to Sync List to manage incompatible commands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software upgrade is performed on redundant processors, then system adaptability is improved, but configuration consistency deteriorates
Solution Approach 1:
The patent applies preliminary action by performing bulk synchronization before software upgrades. The Standby processor is updated to the new software version first, configured with the new command set, and then the Active processor is updated. This preliminary configuration of the Standby processor prevents configuration mismatches during switchover.
Solution Approach 2:
The patent segments the software upgrade process into distinct phases: bulk synchronization phase (where the Standby processor is updated first), line-by-line synchronization phase (where configuration consistency is maintained), and switchover phase. This segmentation allows configuration consistency to be maintained while still enabling software upgrades.
2Adaptability or versatility
If different OS versions are run on Active and Standby processors, then system adaptability is improved, but command compatibility deteriorates
Solution Approach 1:
The patent introduces an intermediary mechanism - a translation layer or compatibility layer that allows commands from the new OS version to be interpreted and executed correctly on the old OS version. This intermediary enables the Standby processor running the new version to understand and respond to commands in a manner compatible with the Active processor running the old version.
Solution Approach 2:
The patent implements universality by designing the command set to be multi-version compatible. The new OS version on the Standby processor is configured to understand both the new command set and the legacy command set, allowing it to function universally across different software versions and maintain compatibility with the Active processor.
3Stability of the object's composition
If configuration synchronization is implemented, then configuration consistency is improved, but system complexity increases
Solution Approach 1:
The patent segments configuration synchronization into two distinct modes: bulk synchronization (performed during software upgrades) and line-by-line synchronization (performed during normal operation). This segmentation reduces the complexity of the overall synchronization mechanism by handling different synchronization needs through specialized, simpler sub-mechanisms.
Solution Approach 2:
The patent implements self-service through automatic configuration synchronization mechanisms that operate without manual intervention. The system automatically detects configuration changes, performs bulk synchronization when needed, and maintains line-by-line synchronization, reducing the operational complexity for system administrators.
Data Source
AI summary
A method of establishing and maintaining a consistent configuration state of a first processor, running on a first version of operating software, and a second processor, running on a second version of operating software, is described. The method involves determining a current configuration state of the first processor, where the configuration state comprises a list of configuration commands. The method also involves performing a syntax check for each command in the current configuration, using the second processor and the second version of operating software, with the syntax check resulting in a pass or a fail result. For every command which results in a fail result, an entry is added to a mismatched configuration list (MCL). Embodiments of this invention can be utilized to keep the configurations consistent during an upgrade or downgrade of the operating software.