Network Configuration Comparison for Component-Level Fault Localization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network monitoring technologies fail to accurately identify failing network components and configuration errors, particularly in configuration files, hindering effective network management.
Innovation Solution
A system and method for monitoring network components by generating an expected configuration file based on a network model, comparing it with an actual configuration file, and identifying differences to detect unwanted or unregistered modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network monitoring procedures are executed to assess current network configuration, then configuration errors can be detected, but the location of failing network components cannot be obtained
Solution Approach 1:
The patent segments the network configuration into individual component configurations, each associated with a specific network component. By comparing the current configuration against the expected configuration at the component level, the system can both detect configuration errors and identify the precise location of failing components through the segmented structure.
Solution Approach 2:
The patent introduces an intermediary configuration database that stores both expected and current configuration data. This intermediary structure enables the comparison process to simultaneously detect errors and locate failing components by mapping configuration discrepancies back to specific network components through the database relationships.
2Reliability
If monitoring platforms are used to watch network activities, then performance problems can be identified, but configuration errors in configuration files cannot be identified
Solution Approach 1:
The patent performs preliminary actions by storing the expected network configuration in advance in a configuration database before actual network operations begin. This pre-stored expected configuration serves as a reference baseline that enables subsequent comparison with current configuration state, allowing precise identification of configuration errors in configuration files.
Solution Approach 2:
The patent implements a feedback mechanism where the current network configuration is continuously compared against the stored expected configuration. This feedback loop provides precise identification of configuration errors by highlighting discrepancies between expected and actual states, enabling accurate detection of configuration file errors.
3Measurement precision
If configuration data is parsed and analyzed from various routers, then configuration mistakes can be identified, but unwanted or unregistered modifications cannot be detected
Solution Approach 1:
The patent creates a copy of the expected network configuration and stores it in a configuration database. This copied expected configuration serves as a reference standard that can be compared against the current configuration. By having this pre-established copy, the system can detect both configuration mistakes and unwanted or unregistered modifications through systematic comparison.
Solution Approach 2:
The patent replaces manual configuration analysis with an automated computer-implemented comparison system. Instead of relying on manual parsing and analysis of configuration data, the system uses automated procedures to compare current configuration against the stored expected configuration, enabling reliable detection of both mistakes and unregistered modifications.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system and method for monitoring configuration status of a plurality of network components of a network. The method comprises generating, based on a network object model, a first configuration file indicative of expected configuration status of the plurality of network components, the network model comprising Node objects, Interface objects, evpnEdge objects and Layer objects. The method further comprises receiving a second configuration file indicative of current configuration status of the plurality of network components, the first and second configuration files comprising tagged sections and sub-sections, and comparing the first and second configuration files comprising comparing a first sub-section of the first configuration file with a corresponding second sub-section of the second configuration file based on tags of the first and second sub-sections, the first and second sub-sections comprising configuration commands relative to one of the plurality of network components.