site stats

Break scalability barriers in OpenFlow SDN


During The Last couple of years, device-defined networking (SDN) has emerged as a strong alternative to traditional networking approaches within the areas of WAN, Knowledge heart networks, and network overlay solutions. The Primary benefit realized from SDN, along with open networking, is the ability to speed up service deployments. SDN options The Usage Of OpenFlow deal with advanced problems, including dynamic provisioning, interconnection, and fault administration. Even If the functionality of SDN has developed and matured, the scalability of SDNs in line with OpenFlow has been restricted through OpenFlow’s ties to ternary content-addressable memory (TCAM). OpenFlow with the aid of design was implemented within the TCAM.

The Problem is that Prior swap ASICs like Broadcom’s Trident+ had reasonably small TCAMs, and early versions of OpenFlow (1.Zero through 1.2) may use simplest TCAM for reminiscence. This restricted OpenFlow scalability to someplace between 1,000 and a pair of,000 flows. However today, change ASIC producers are building better TCAMs and OpenFlow developers have provide you with methods to get right of entry to other memory tools to make stronger more flows in nowadays’s change ASICs.

Float necessities

Typical Knowledge heart network infrastructure includes top-of-rack switches, core switches, and aspect switches. Every of those hierarchies needs a special level of Float scalability (Figure 1).

sdn flow scale requirements

Figure 1: Drift scale necessities in Information heart networks.

Given the necessities proven in Figure 1, it’s easy to remember the reluctance to put into effect early variations of OpenFlow. Basically, these limits had been mandated by using OpenFlow’s reliance on TCAM memory gadgets for storage of Go With The Flow routing data.



Supply hyperlink

You must be logged in to post a comment Login

Widgetized Section

Go to Admin » appearance » Widgets » and move a widget into Advertise Widget Zone