EVPN Debugging with Intent Graphs for Network Anomaly Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing EVPN debugging methods rely on device-level consistency checking, which is resource-intensive and requires extensive administrator knowledge, especially in large networks with diverse vendor implementations, leading to inefficiencies in identifying network anomalies.
Innovation Solution
A network management system (NMS) uses intent graph data to collect and compare endpoint information from network devices, such as MAC address tables, to identify network anomalies, performing automated diagnosis and reducing resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device-level consistency checking is performed for EVPN debugging, then network anomaly detection capability is improved, but resource consumption and system complexity increase significantly
Solution Approach 1:
The patent introduces an intermediary approach by using intent graph data as a mediator between network devices and the debugging process. Instead of directly performing resource-intensive consistency checking at each device level, the system uses intent graph data to identify anomalies at a higher abstraction layer, thereby reducing resource consumption while maintaining detection capability.
Solution Approach 2:
The patent transitions from device-level checking to intent graph-level analysis, adding a new dimensional perspective. By representing network devices and their relationships in an intent graph structure, the system can perform anomaly detection in this higher-dimensional space, which is more efficient than traditional device-level checking.
2Reliability
If device-level consistency checking is performed, then network anomaly detection capability is improved, but administrator knowledge requirements and operational complexity increase
Solution Approach 1:
The system performs self-service by automatically using intent graph data to identify network anomalies without requiring extensive administrator intervention or specialized knowledge. The intent graph structure inherently captures the necessary relationships and configurations, allowing the system to autonomously perform consistency checking and anomaly detection.
Solution Approach 2:
The patent changes the fundamental parameters of how consistency checking is performed by using intent graph data structures instead of traditional device-level configuration data. This parameter change transforms the checking mechanism into something that is both more reliable and easier to operate, as the intent graph abstracts away the complexity of individual device configurations.
3Measurement precision
If comprehensive vendor implementation knowledge is required for EVPN debugging, then debugging accuracy is improved, but system complexity and time requirements increase
Solution Approach 1:
The patent applies universality by creating a vendor-agnostic intent graph data structure that can represent EVPN configurations across different vendor implementations. This universal structure allows the same debugging mechanism to work across multiple vendors without requiring specialized knowledge of each vendor's specific implementation details, thereby reducing system complexity while maintaining accuracy.
Solution Approach 2:
The system creates a simplified copy or representation of the complex vendor-specific EVPN configurations in the intent graph format. This copied representation captures the essential relationships and configurations needed for anomaly detection without requiring the full complexity of original vendor implementations, enabling accurate debugging with reduced system complexity.
Data Source
AI summary
A system includes a storage device configured to store intent graph data associated with a plurality of virtual networks and a plurality of network devices and processing circuitry in communication with the storage device. The intent graph data identifies a subset of the plurality of virtual networks associated with each network device. The processing circuitry is configured to determine whether the intent graph data indicates a first network device and a second network device are configured for a common virtual network, in response to determining that the graph indicates the first network device and the second network device are configured for the common virtual network, determine a network anomaly based on a comparison of first endpoint information obtained from the first network device and second endpoint information obtained from the second network device, and output an indication of the network anomaly.


