Stacking System Configuration Rollback Without Device Reboots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current stack merging and joining technologies in networking require device reboots, leading to prolonged operational delays and increased complexity, especially in large or complex systems, due to the reliance on hardware and software-controlled reboot methods.
Innovation Solution
A method that involves determining a change in the master device, rolling back processes to a pre-configuration stage, and loading configuration information from the changed master device, eliminating the need for device reboots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device reboots are performed during stack merging or joining, then configuration consistency is ensured, but operational delays are prolonged and system complexity increases
Solution Approach 1:
The system performs preliminary actions by saving configuration data to a database before the reboot process begins. This allows the configuration to be preserved and restored afterward, ensuring consistency without requiring the device to remain down for extended periods. The configuration is prepared in advance and can be quickly reinstated after reboot, reducing operational delays while maintaining reliability.
Solution Approach 2:
The invention creates a copy of the configuration data from the master device and stores it in a database on member devices. This copying mechanism ensures that configuration consistency is maintained across the stacking system without requiring all devices to be rebooted simultaneously. The copied configuration can be restored on individual devices as they come back online, reducing overall system downtime while ensuring configuration integrity.
2Stability of the object's composition
If device reboots are performed during stack merging or joining, then system stability is maintained, but deployment complexity and costs increase
Solution Approach 1:
The system implements self-service by automatically saving configuration data to a database and restoring it after reboots without requiring manual intervention. The stacking system autonomously manages the configuration persistence and restoration process, reducing deployment complexity and manual costs while maintaining system stability. The devices themselves handle the configuration management, eliminating the need for external assistance during the stack merging or joining process.
3Reliability
If configuration information is loaded from master device, then stacking system consistency is maintained, but manual interventions are required increasing deployment time
Solution Approach 1:
The system implements feedback by automatically detecting when configuration changes occur on the master device and triggering the save-to-database and restore processes on member devices. This automated feedback loop ensures stacking system consistency is maintained without requiring manual intervention to load configuration information. The system self-monitors and self-corrects, maintaining reliability while improving deployment speed by eliminating manual configuration loading steps.
Data Source
AI summary
The disclosure provides a device and a method. The device of a stacking system includes: a memory; and one or more processors operatively coupled to the memory, the one or more processors configured to: determine that a master device managing the device of the stacking system has changed; roll back a process to a stage prior to loading configuration information; obtain configuration information of a changed master device; and load the configuration information of the changed master device.