Supervisor Switchover History Tracking Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network devices lack a mechanism to track the history of switchovers between active and standby supervisors, limiting the ability to maintain consistency and provide accurate records of role changes, protocols, and reasons for switchover events.
Innovation Solution
Implementing a switchover history tracking system where each supervisor generates local and remote switchover record files, including details like previous and current roles, protocols, and reasons, which are then processed by a switchover logger agent to update a switchover history file and network device state database, with reconciliation processes to resolve any record conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional network devices operate with active and standby supervisors without tracking mechanisms, then device simplicity is maintained, but the ability to track switchover history and maintain record consistency is lost
Solution Approach 1:
The patent implements preliminary action by having supervisors generate switchover record files before actual switchover events occur. The election manager is pre-configured to create local and remote switchover record files that document the previous role, current role, protocol, timestamp, and reason for switchover. This proactive record generation ensures that switchover history is captured immediately when events happen, preventing information loss without requiring complex real-time tracking systems.
Solution Approach 2:
The patent applies the copying principle by creating remote switchover record files that are sent to and stored on the standby supervisor. Each supervisor maintains copies of switchover records, with the active supervisor generating local records and sending remote records to the standby supervisor. This copying mechanism ensures that switchover history information is preserved and available even if one supervisor fails, without requiring a centralized complex tracking system.
2Reliability
If supervisors coordinate to maintain switchover history consistency, then accurate switchover records are provided, but system complexity and coordination overhead increase
Solution Approach 1:
The patent implements feedback through the switchover logger agent that continuously monitors and compares switchover records between the active and standby supervisors. When a switchover event occurs, the election manager generates records and the switchover logger agent verifies consistency by comparing local and remote records. This feedback mechanism ensures accurate switchover history maintenance through automated verification rather than complex manual coordination procedures.
Solution Approach 2:
The patent applies self-service by enabling supervisors to automatically generate, store, and verify their own switchover records without external intervention. The election manager autonomously creates switchover record files, and the switchover logger agent automatically performs consistency checks and updates records. This self-service capability ensures reliable switchover tracking while minimizing the need for complex external coordination mechanisms.
3Loss of information
If detailed switchover information is recorded including roles, protocols, and reasons, then operational transparency is enhanced, but data storage and processing requirements increase
Solution Approach 1:
The patent applies segmentation by dividing switchover information into structured record files with distinct fields for different types of data. Each switchover record file contains segmented information including previous role, current role, protocol, timestamp, and reason for switchover. This segmentation allows detailed operational transparency to be maintained while organizing data in a compact, efficient format that minimizes storage requirements and facilitates easy processing and retrieval.
Data Source
AI summary
A method for managing a switchover between an active supervisor and a standby supervisor executing on a network device includes initializing a switchover logger agent executing on the supervisor responsive to the switchover, wherein after the switchover, the supervisor is in an active state, wherein prior to the switchover, the supervisor is in a standby state and the second supervisor is in the active state, and wherein the supervisor assumes management of controlled devices on the network device when in the active state, based on the initialization, obtaining a local switchover record file corresponding to the switchover by the supervisor, updating, by the supervisor, a switchover history file based on the local switchover record file, and updating, by the supervisor, a network device state database instance based on the local switchover record file.