Out-of-band Configuration Change Reconciliation in Network Management Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network management systems (NMS) face challenges in maintaining synchronization across multiple network devices due to out-of-band (OOB) changes, leading to configuration conflicts and integrity issues, especially when high-level service model changes impact numerous device configurations.
Innovation Solution
The NMS employs techniques to detect and resolve OOB changes by translating low-level configuration changes to high-level changes, applying them uniformly across devices, and using reverse mapping functions to reconcile services while preserving semantic integrity, along with a recommendation system for automatic conflict resolution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If administrators apply out-of-band changes directly to network devices to enable quick configuration modifications, then the flexibility and speed of configuration changes improve, but the network management system loses synchronization with the actual device configurations, leading to configuration conflicts and integrity issues
Solution Approach 1:
The system implements a feedback mechanism where configuration changes made out-of-band are detected through device state monitoring. The NMS receives notifications about configuration changes and automatically initiates reconciliation processes to restore synchronization, ensuring the management system reflects the actual device state without preventing administrative flexibility
Solution Approach 2:
The system enables self-service by automatically detecting out-of-band changes and triggering reconciliation workflows without requiring administrator intervention. The NMS autonomously identifies configuration drift, analyzes conflicts, and applies corrections to restore synchronization, reducing manual overhead while maintaining reliability
2Ease of operation
If the NMS translates high-level service model changes to low-level device configurations, then the ease of service management improves, but a single high-level change impacts numerous device configurations, increasing system complexity and potential for conflicts
Solution Approach 1:
The system segments the configuration management process into distinct phases: high-level service definition, translation to device-specific configurations, and individual device application. This segmentation allows the NMS to manage services at an abstract level while handling device-specific complexities separately, reducing the propagation burden
Solution Approach 2:
The system performs preliminary actions by pre-translating high-level service changes into device-specific configuration instructions before actual device application. The NMS prepares reconciliation workflows in advance, analyzing potential conflicts and planning correction steps, which simplifies the actual configuration propagation process
3Reliability
If the NMS maintains detailed tracking of all device configurations to ensure synchronization, then the configuration integrity improves, but the computational overhead and time required for detection and resolution increase
Solution Approach 1:
The system extracts and monitors only the critical configuration parameters that are essential for service functionality. Rather than tracking every configuration detail, the NMS focuses on key state variables that indicate synchronization status, reducing computational overhead while maintaining sufficient integrity monitoring
Solution Approach 2:
The system implements event-driven monitoring that skips continuous polling and only activates detailed configuration tracking when changes are detected. When out-of-band changes occur, the NMS rapidly rushes through the detection and reconciliation process for affected configurations, minimizing time loss while ensuring integrity
Data Source
AI summary
In one example, a network management system (NMS) device manages a plurality of network devices. The NMS device includes one or more interfaces to communicatively couple the NMS device to the plurality of network devices, and a processor, implemented using circuitry, configured to determine that a low-level configuration of a first network device of the plurality of network devices has been changed by an out-of-band (OOB) change, translate the OOB change to a high-level configuration change, determine whether to apply the high-level configuration change to the plurality of network devices, and in response to determining to apply the high-level configuration change to the plurality of network devices, apply, via the one or more interfaces, the OOB change to low-level configurations of the plurality of network devices.