SDN Packet Tracing via TTL Decrement in Flow Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In complex OpenFlow-based Software-Defined Networks (SDNs), troubleshooting packet drops is challenging due to the large and intricate nature of packet processing pipelines, where identifying errors in flow tables and group tables is difficult and time-consuming.
Innovation Solution
A method involving a first network node sending a packet with a trace bit and Time To Live (TTL) value through a pipeline of flow tables, decrementing the TTL at each table, allowing stepwise tracing of the packet route and identifying potential errors by incrementing TTL upon return, enabling the determination of the route followed by the packet and pinpointing processing errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If packet tracing is performed in complex OpenFlow-based SDN pipelines, then troubleshooting capability is improved, but time consumption and operational complexity increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring flow tables with trace-specific match fields and action instructions before packet tracing is needed. The controller pre-programs the pipeline to recognize trace packets and automatically decrement TTL at each flow table, so that when actual tracing is required, the infrastructure is already in place to execute immediately without manual setup time
Solution Approach 2:
The patent uses an intermediary mechanism by introducing a dedicated trace bit field and TTL counter as mediators between the packet and the flow tables. These intermediaries automatically track packet progression through the pipeline without requiring complex external monitoring systems, enabling efficient tracing while reducing operational complexity
2Measurement precision
If detailed packet route tracing is implemented, then error identification precision is improved, but device complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the packet tracing function into discrete, modular components: individual flow tables each decrement the TTL counter independently, and each table's match fields are separately configured. This modular segmentation allows precise error identification at each pipeline stage while maintaining manageable device complexity through systematic decomposition of the tracing mechanism
3Measurement precision
If TTL decrementing is performed at each flow table, then tracing accuracy is improved, but processing overhead increases
Solution Approach 1:
The patent applies self-service by enabling flow tables to automatically decrement the TTL counter and make routing decisions based on their own local match field evaluations without requiring external controller intervention at each stage. This self-service mechanism achieves high tracing accuracy through systematic TTL decrementing while minimizing processing overhead by eliminating redundant controller communications
Data Source
Figure 1
Figure 2a~2b
Figure 3
AI summary
Methods for tracing a packet in a pipeline (107) comprising a set of tables, in an SDN (10) using OpenFlow. The packet comprises a trace bit, and is provided with a TTL value. A first network node (101) indicates to a second network node (102) to have each flow table decrement the TTL value by 1, based upon the trace bit. The first network node (101) initially sets (303) the TTL to be 1, and then sends (304) the packet to a first table in the second network node (102). The first network node (101) receives (305) the packet, from another table in the set, and for every remaining table, and one table at a time: a) increments (307) the TTL value by 1, and b) repeats (308) the sending (304), and the receiving (305), until a last table is reached or a criterion is met. The first network node (101) then indicates a route followed by the packet.