Shadow Configuration Database for Network Device Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network infrastructure devices face challenges in safely and efficiently implementing configuration changes due to the risk of unintended network failures from improper configuration updates, especially when multiple devices are affected simultaneously, and existing AAA mechanisms struggle to process non-CLI format configuration change requests.
Innovation Solution
The implementation of a shadow configuration database that allows for a 'dry-run' testing of changes without affecting the production environment, combined with generating a differential CLI command set to ensure proper authorization and accounting for configuration changes, regardless of the request format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If configuration changes are applied to multiple network devices simultaneously, then productivity is improved, but reliability deteriorates due to increased risk of network failures
Solution Approach 1:
The patent applies preliminary action by creating a shadow configuration database that replicates the production configuration before changes are applied. This allows configuration changes to be tested and validated in advance in a non-production environment, ensuring reliability before simultaneous deployment across multiple network devices, thus resolving the contradiction between fast deployment and network stability.
2Reliability
If a shadow configuration database is created for testing changes, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent uses copying by creating a shadow configuration database that is a replicate of the production configuration database. This shadow copy allows safe testing and validation of configuration changes without affecting the actual production system. The copying approach improves reliability by enabling pre-validation while keeping the complexity manageable through standardized database replication techniques.
3Adaptability or versatility
If differential CLI command sets are generated for non-CLI format changes, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent applies the intermediary principle by introducing a translation layer that converts non-CLI format configuration change requests into differential CLI command sets. This intermediary processing mechanism enables the system to accept various configuration formats while translating them into the standardized CLI format that the shadow configuration database can process, thereby improving adaptability without significantly increasing overall system complexity.
Data Source
AI summary
A technique to manage a configuration database (CDB) for a network device is disclosed. Network devices may receive a configuration change request as a configuration change object. To process that request, a current configuration CLI set representative of the current CDB may be generated. The network device creates a shadow CDB initially corresponding to the current CDB and processes the change request against the shadow CDB. An updated configuration CLI set may then be generated from the updated shadow CDB. A differential CLI set indicating the difference between the first CLI set and the second CLI set may be generated to represent a set of CLI commands to transition from one CDB to the other (e.g., implement the request). Authorization of the user to execute the CLI commands of the differential CLI dataset may be verified. Upon verification, the current CDB may be replaced with the updated shadow CDB.