Backtrace Tool for Software Defined Network Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Debugging software-defined networks is challenging due to the complexity of network virtualization platforms, where multiple components must collaborate, making it difficult for developers to identify and diagnose configuration issues effectively, as traditional ad-hoc log entry approaches are laborious and often lead to misidentification of the culprit component.
Innovation Solution
A backtrace tool that generates a correlated view of network configuration entities across the software-defined network by parsing network control event messages, programmatically diagnosing issues by identifying missing or erroneous events and interactions, and tracing them back to the source component.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional ad-hoc log entry approaches are used for debugging, then individual components can be monitored, but the overall system diagnosis becomes laborious and time-consuming
Solution Approach 1:
The patent combines multiple log files from different network components into a single correlated view that shows the sequence of events across the entire system. This merging allows developers to see how components interact and identify the root cause of issues without manually searching through multiple separate log files, thereby reducing debugging time while maintaining component-level monitoring accuracy.
Solution Approach 2:
The patent introduces an intermediary tool that correlates events across multiple log files and presents them in a unified sequence. This intermediary processing layer translates scattered log entries into a coherent narrative of system events, making it easier to diagnose issues without losing the detailed component information.
2Loss of information
If developers manually search and correlate messages in log files, then detailed component information can be obtained, but the debugging process becomes laborious
Solution Approach 1:
The patent merges information from multiple log files into a single correlated view that maintains complete component information while presenting it in an easily accessible format. The system preserves all detailed component data but organizes it chronologically and contextually, eliminating the need for manual searching and correlation.
Solution Approach 2:
The patent creates a copied and organized representation of the distributed log data in a unified view. This copied view maintains the integrity of original component information while presenting it in a correlated sequence that is much easier to analyze, effectively separating the complexity of data collection from the simplicity of data analysis.
3Reliability
If multiple log files are examined to debug problems, then comprehensive system view can be achieved, but the process becomes time-consuming
Solution Approach 1:
The patent combines data from multiple log files into a single correlated event sequence that maintains the completeness needed for accurate diagnosis while dramatically reducing the time required to analyze system behavior. The correlated view shows events in chronological order across all components, enabling fast identification of root causes without sacrificing diagnostic reliability.
Data Source
AI summary
A method of diagnosing a software-defined network is provided. The method determines an observed plurality of network control events from a set of network control event messages. Each network control event message includes a unique identifier and is used for configuring a network configuration entity on a network component. The method, from a description of an expected configuration of the network, determines an expected plurality of network control events. The method backtraces the observed control events from the current configuration of the network to determine whether the expected network control events have occurred. The method identifies a network component as the source of fault when the network component receives an input set of network control events that matches a set of expected network events but does not produce a set of output network control events that match a set of network control events.