Topology Engine State Tracking for Network Fault Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current topology engines face challenges in real-time causal analysis and tracking of network topology changes, making it difficult to accurately determine fault conditions and maintain up-to-date topology information across multiple layers and services.
Innovation Solution
A system and method for topology state tracking using a topology engine that includes a processor and computer-readable media with instructions to receive state information from network devices, generate real-time network topology information, detect changes, and provide this information to client devices through a state tracking API, allowing for continuous synchronization and visualization of network topology maps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional topology engines are used to retrieve topology information, then basic topology data can be obtained, but real-time tracking and causal analysis of topology changes cannot be performed
Solution Approach 1:
The system performs preliminary actions by establishing event subscriptions and state tracking mechanisms in advance with network devices. When topology changes occur, the system already has the infrastructure in place to immediately capture and process these changes, eliminating the need for reactive polling and reducing both information loss and response time.
Solution Approach 2:
The system implements continuous feedback loops where topology state information is constantly monitored, compared against previous states, and updated in real-time. This feedback mechanism ensures that any topology changes are immediately detected and propagated to clients, preventing information loss and enabling timely causal analysis.
2Reliability
If frequent polling of network devices is performed to detect topology changes, then real-time topology information can be obtained, but system complexity and resource consumption increase
Solution Approach 1:
Instead of continuous or frequent polling, the system uses event-driven periodic action where topology information is retrieved only when changes are detected through subscriptions. This approach maintains high reliability by capturing all topology changes while significantly reducing system complexity and resource consumption compared to frequent periodic polling.
Solution Approach 2:
Network devices are configured to self-report topology changes through event subscriptions and state tracking APIs. This eliminates the need for external polling mechanisms, reducing system complexity while maintaining reliable and accurate topology information through device-initiated change notifications.
3Measurement precision
If detailed state information is collected from all network devices, then comprehensive topology analysis can be performed, but data processing overhead and storage requirements increase
Solution Approach 1:
The system extracts only the specific state information and topology parameters that are relevant for causal analysis and change detection. By filtering and selecting only the necessary data elements from network devices, the system maintains precise topology analysis capabilities while significantly reducing data processing overhead and energy consumption associated with handling unnecessary detailed information.
Data Source
AI summary
A system for topology state tracking includes a client device requesting network topology information, and a topology engine coupled to one or more network device. The topology engine includes at least one processor, and non-transitory computer readable media having encoded thereon computer software having a set of instructions executable by the at least one processor to perform one or more operations. The set of instructions includes instructions to receive state information associated with at least one network service, generate network topology information based on the state information, determine changes in the network topology for the at least one network service, update the network topology information, provide access to the network topology information by the client device, receive a request for network topology information from the client device, and transmit the network topology information to the client device.