Switch Configuration Synchronization via Unique Row ID Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods for synchronizing network switch configurations face challenges in reversing changes, especially when multiple changes are made simultaneously, due to ordering dependencies, which can prevent certain configuration changes from being reversed.
Innovation Solution
A switch configuration synchronization system that generates unique identifiers for database rows, creates mappings between primary and peer databases, and synchronizes changes, allowing for easy rollback and reducing dependency issues by identifying and addressing missing references.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If text file configuration synchronization is used between switches, then configuration backup is achieved, but reversing changes becomes difficult when multiple changes are made simultaneously due to ordering dependencies
Solution Approach 1:
The patent segments the configuration synchronization process into discrete transactional units with unique identifiers. Each configuration change is treated as an independent transaction that can be individually tracked, identified, and reversed without affecting other changes. This segmentation eliminates the ordering dependency problem where reversing one change required reverting all preceding changes.
Solution Approach 2:
The patent implements a feedback mechanism through the synchronization system that tracks configuration changes bidirectionally between primary and peer switches. The system provides feedback about which changes are synchronized, their status, and their unique identifiers, enabling selective reversal of specific changes while maintaining knowledge of the overall synchronization state.
2Productivity
If multiple configuration changes are made simultaneously, then configuration updates are efficient, but dependency issues prevent certain changes from being reversed
Solution Approach 1:
The patent applies preliminary action by assigning unique identifiers to configuration changes before they are synchronized between switches. This pre-identification allows the system to track and manage multiple simultaneous changes independently, reducing the complexity of managing dependencies among concurrent configuration updates.
3Adaptability or versatility
If traditional text file configuration methods are used, then compatibility with existing systems is maintained, but modern protocols like REST cannot be effectively supported
Solution Approach 1:
The patent implements a universal configuration synchronization system that can handle multiple protocols including traditional text file methods and modern REST protocols. The transactional framework with unique identifiers and bidirectional synchronization is protocol-agnostic, allowing the same core mechanism to serve both legacy and modern configuration management needs without sacrificing ease of operation for programmable interfaces.
Data Source
Figure 1A~1B
Figure 2
Figure 3
AI summary
Examples disclosed herein relate to a method comprising generating a first and a second set of unique identifiers for each row in each table of a first and second database, respectively. The first and second database may be configured to operate a first and second switch operating traffic on a network, respectively. The first switch and the second switch may be configured to operate traffic on the network. The method may also include creating a mapping between the first set of unique identifiers and the second set of unique identifiers and determining that a first row of the first database is marked to be synchronized, the first row corresponding to a first unique row ID. The method may also include retrieving, from a second row of the second database corresponding to a second unique row ID mapped to the first unique row ID and updating the second row.