Network Controller Debug Table Segmentation for Packet Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication networks face challenges in efficiently managing and debugging networks with multiple switches from different vendors due to incompatibilities in operating systems and control protocols, making it difficult to pinpoint packet loss or routing inefficiencies.
Innovation Solution
A controller is implemented to provide debug table entries to switches, which are separate from flow tables, allowing the controller to monitor counter values and perform debugging operations by incrementing counters and forwarding packets to identify issues such as elephant flows, load balancing, and path changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If a controller monitors all network packets to debug routing issues, then debugging capability is improved, but network traffic load increases and processing efficiency decreases
Solution Approach 1:
The patent segments packet processing into two separate paths: a fast path for normal packet forwarding that maintains high efficiency, and a debug path for monitoring specific packets that requires detailed analysis. The flow table and debug table are separated, allowing independent optimization of each function without compromising the other.
Solution Approach 2:
The patent introduces an intermediary mechanism (the debug table with counters) that selectively monitors packets based on matching criteria without requiring the controller to examine every packet. This intermediary layer filters and counts packets of interest while allowing other packets to flow through the efficient forwarding path unchanged.
2Device complexity
If debug tables are integrated with flow tables, then system complexity is reduced, but debugging operations interfere with packet forwarding performance
Solution Approach 1:
The patent divides the table structure into two independent components: flow tables for packet forwarding decisions and debug tables for monitoring operations. This segmentation ensures that debugging operations do not interfere with forwarding performance, as each table type handles its specific function without mutual interference.
Solution Approach 2:
Different parts of the switching system are given different qualities: the flow table is optimized for high-speed forwarding with simple match-and-forward operations, while the debug table is optimized for monitoring with counter increment operations. Each table structure is tailored to its specific function, improving overall system reliability.
3Difficulty of detecting and measuring
If the controller analyzes network traffic in real-time to identify packet loss, then troubleshooting capability is improved, but controller processing load increases
Solution Approach 1:
The patent enables switches to perform self-service monitoring by maintaining local counters in debug tables that automatically increment when packets match specific criteria. This distributes the monitoring workload from the controller to the switches themselves, reducing controller processing load while maintaining comprehensive packet loss detection capability across the network.
Solution Approach 2:
The controller receives feedback in the form of counter values from switches, which provide information about packet matching and potential loss without requiring the controller to directly analyze individual packets. This feedback mechanism allows efficient troubleshooting by aggregating monitoring data at the switch level and reporting summaries to the controller.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A controller implemented on computing equipment may control switches in a network. The controller may provide flow tables that implement network policies to the switches to control packet forwarding through the network. The controller may provide debug table entries to the switches for use in a debug table that is separate from the flow table. The debug table entries may match incoming network packets and increment corresponding counters on the switches. The controller may retrieve count information from the counters for performing debugging operations on the network. For example, the controller may identify conflicts between fields of a selected flow table entry, determine whether elephant packet flows are present between switches, determine whether desired load balancing is being performed, determine whether a network path has changed, determine whether packet loss has occurred, and/or determine whether network packets are taking undesired paths based on the retrieved count information.