Network Node Reconfiguration via Configuration Diff Entity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data network management systems face challenges in efficiently monitoring and implementing configuration changes across multiple nodes, as manual CLI commands are time-consuming, automated scripting is node-specific, and existing solutions often result in redundant reconfiguration and data traffic issues.
Innovation Solution
A method that stores current and desired configuration data to generate a 'Diff' entity representing configuration differences, using a data model for context-aware comparison and CLI command sequence generation, reducing redundant reconfigurations and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual CLI commands are used to reconfigure network nodes, then configuration changes can be implemented, but the process is very time consuming
Solution Approach 1:
The system automatically generates reconfiguration scripts by comparing the current configuration database with the desired configuration database, eliminating the need for manual CLI commands. The NMS system self-services the reconfiguration process by autonomously identifying changes and generating the necessary configuration commands.
Solution Approach 2:
The desired configuration is pre-defined in a database before actual reconfiguration occurs. The system performs preliminary comparison between current and desired configurations to generate scripts in advance, allowing efficient execution without manual intervention during the actual reconfiguration process.
2Extent of automation
If automated scripting is used for remote reconfiguration, then reconfiguration is more automated, but scripts must be individually adapted to different network nodes
Solution Approach 1:
The system uses a universal database schema and comparison mechanism that works across different network node types. The same reconfiguration system can handle multiple node types by storing their specific configuration parameters in a standardized database format, eliminating the need for separate scripting systems for each node type.
Solution Approach 2:
The system manages complexity by parameterizing configuration data in databases rather than hardcoding node-specific logic in scripts. Configuration parameters are stored as structured data that can be dynamically compared and processed, allowing the same automation framework to adapt to different nodes by changing database content rather than script structure.
3Productivity
If configuration data is pushed to all network nodes, then desired configuration changes are implemented, but redundant reconfiguration occurs causing high data traffic
Solution Approach 1:
The system extracts only the differences between current and desired configurations by comparing database entries. Instead of pushing entire configuration sets to all nodes, it identifies and extracts only the specific changes that need to be applied, significantly reducing the amount of data transmitted across the network.
Solution Approach 2:
The system performs partial reconfiguration by applying only the necessary configuration changes identified through database comparison, rather than pushing complete configuration sets to all nodes. This selective approach reduces redundant data transmission while ensuring all necessary changes are implemented.
Data Source
AI summary
The present invention relates to a method for reconfiguring data network nodes (3, 5, 7) in a data network (1), the method comprising the steps of:storing information comprising:a first set of data (25I-25V) representing a current configuration of the data network nodes (3, 5, 7), anda second set of data (27I-27V) representing a desired configuration of the data network nodes (3, 5, 7);generating, from the first set of data (25I-25V) and the second set of data (27I-27V), an information entity (33, 33I-33V) representing a difference between the current configuration and the desired configuration, andreconfiguring at least one of the data network nodes (3, 5, 7) using the information entity (33, 33I-33V).