Abstract
Software Defined Networking is an emerging network architecture, which decouples the control plane from the data plane and operates the global network with elaborate abstraction. The flow table plays an important role in an OpenFlow Switch(OFS) and is the key resource to support the SDN/OpenFlow abstraction. To provide wire-speed processing, fast memory(e.g., TCAM, QDR, SRAM) is utilized to form the flow table. Unfortunately, the development of such kind of fast memories is far behind the hungry requirement on its usage, especially for the TCAM. As a result, the flow table installed in OFS has tremendous risk to be overflow, possibly leading to large quantity of Packet-In/Packet-Out messages between OFS and controller. Generally, an incoming packet from a flow is processed according to the action specified in the according flow entry in the flow table(s). If no entry is matched in the flow table, a packet-in message querying how to process the packet will be sent to the controller from the switch. If the number of active flows always touches the maximum number of entries in the flow table, the table-miss events are not avoidable. So that at first we investigate how to mitigate the overhead when occurring table-miss events based on the phenomenon of uneven flow table distribution. The basic idea is to distribute the packets facing table-miss event in heavily loaded switch to other lightly loaded switches instead of triggering packet-in messages always in hot switches. The conceptual simplicity of FTS idea hides two significant challenges. (1) How to select a right port randomly by SDN switch. (2) How to make this progress "pipeline-able" in a general SDN switch without changing its Hardware. The new mechanism proposed in this paper to handle the Table-Miss event is named Flow Table Sharing (FTS). The evaluations have demonstrated that FTS reduces both control messages quantity and RTT time by two orders of magnitude compared to current state-of-the-art OpenFlow Table-Miss handler. We first build a switch in MININET (test environment), and measure the number of control messages generated by setting up a new flow transfer (TCP, UDP) when the flow table of the switch is overflow, as well as the packet loss rate and the average delay. Then, we evaluate the flow table demand in the optimal way that all switches have enough flow table resources and set this result as the control group. Then, on the one hand, we evaluate the additional flow table demand which is required by rebuilding the interrupted flow, when the FTS try to fix the problem caused by the overflow. On the other hand, we evaluate the total flow table consumption which is required by building the new transmission for the first time, after the overflow happened. Even during the flow table overflow period, denial of service for new flows does not happen. We designed an external user switch-computed Group Table select algorithm and show its validity and fastness. It is easy to implement, easy to control and the current state-of-the-art OpenFlow Table-Miss handler is a special case of FTS.
| Translated title of the contribution | A Mechanism of Taming the Flow Table Overflow in OpenFlow Switch |
|---|---|
| Original language | Chinese (Traditional) |
| Pages (from-to) | 2003-2015 |
| Number of pages | 13 |
| Journal | Jisuanji Xuebao/Chinese Journal of Computers |
| Volume | 41 |
| Issue number | 9 |
| DOIs | |
| State | Published - 1 Sep 2018 |
Fingerprint
Dive into the research topics of 'A Mechanism of Taming the Flow Table Overflow in OpenFlow Switch'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver