Virtualization has become an irresistible trend in data center networks and enterprise networks. Having the ability to abstract vast amounts of resources and manage multiple environments from one single controller means the network is going to be more agile and flexible. Software-defined networking (SDN) is one of the key technologies that make it real. Internet service providers and business owners try to benefit from this technology; at the same time, vendors and manufacturers release new products that can be used in SDN environments in succession, which include one of the key components – SDN switches. What is an SDN switch? Is it more complicated than normal Ethernet switches? This article aims to demystifying the concepts and applications of SDN switches.
Figure 1: High-performance SDN switches supporting OpenFlow v1.3.
An SDN switch is a software program or hardware device that forwards packets in an SDN environment. It must support SDN protocols. The earliest as well as the most commonly known SDN protocol is OpenFlow. Therefore, an SDN switch is often called OpenFlow switch as well. There are also some other SDN protocols that are developed by SDN switch vendors, such as OpFlex, NETCONF, BGP (Border Gateway Protocol), XMPP (Extensible Messaging and Presence Protocol), etc.
Using the earliest protocol defined in SDN environment, OpenFlow switches have evolved from OpenFlow v1.0. to v1.3. So the latest SDN switches that utilize OpenFlow are supposed to support OpenFlow v1.3. For example, FS.COM SDN switches are all compatible with OpenFlow v1.3.11, so as to deliver enhanced SDN performance. Here is the information the four FS.COM SDN switches for your reference.
|Model||Ports||Switching Chip||CPU||Switch Capability||Price|
|N5850-48S6Q||48*10GbE+6*40GbE||Trident 2 BCM56854||Intel Rangeley C2538 2.4Ghz 4-core||1.44Tbps Full-duplex||US$ 4,419.00|
|N8000-32Q||32*40GbE||Trident 2 BCM56850||2.56Tbps Full-duplex||US$ 5,819.00|
|N8500-32C||32*100GbE||Tomahawk BCM56960||6.4Tbps Full-duplex||US$ 9,199.00|
|N8500-48B6C||48*25GbE+6*100GbE||Broadcom Tomahawk+||Broadwell-DE 2.2Ghz 2-core||3.6Tbps Full-duplex||US$ 6,199.00|
Whether it is a virtual (hypervisor-based) switch or a physical switch, an SDN switch only keeps the data plane (packet forwarding) in itself. The control plane (high-level routing) is decoupled from the SDN switch hardware but implemented in the SDN controller (an application running on the server or somewhere), which lies between network devices and applications. Every SDN switch in the SDN model is programmable by the SDN controller through SDN protocols. And communications between applications and devices are achieved by going through the SDN controller.
Figure 2: Communications between SDN switches, SDN controller and applications.
An SDN switch consists of ports and tables. Packets arrive and leave the switch through ports. Tables consist of rows containing a classifier and set of actions. When an SDN switch receives a packet which it does not have a match row in the table, it will communicate with the SDN controller and ask what to do with this packet. The controller can download a flow to the switch, which includes the first classifier that best matches the packet and the actions. Actions administer the treatment of the packet, which can be forwarding it to the port(s), encapsulating and forwarding it to the controller, dropping the packet, or sending it to the normal processing pipeline. Once the flow is downloaded to the switch table, it will switch similar packets at wire speed. This automated process makes it easier to integrate and manage different applications.
Some users have had many early-stage switches in use that are non-SDN but still want to enjoy the benefits of SDN environment. So they may ask if their “old” switch can be used as SDN switch. In fact, there has been experimentation on bringing early-stage switches into use in SDN environment. One possible approach is to use Ternary Content Addressable Memory (TCAM) with OpenFlow v1.0. By using TCAM, early hardware vendors can insert a flow from an SDN controller into the switch forwarding table for subsequent flow lookups of a flow. But TCAM is not the most efficient recipe for switch hardware search lookups, because it is power hungry, expensive and takes up quite a bit of silicon space. There might be some better ways to retro-fit the conventional switches to accommodate to the SDN environment in the future.
One general advantage of using SDN switch is easier flow control and configuration. With SDN switches, you do not need to go to the locations of the switch and login to the command line to configure it. You can remotely control and program multiple switches through one single SDN controller that uses SDN protocol and provides API (Application Program Interface) for SDN switches. Other benefits are that it will be easier to do load-balancing even at high data rates, and the traffic can be isolated without the need for VLANs, since the SDN controller functions to refuse certain connections.
In the SDN environment, network performance has become more delighting and network management has become more convenient in data centers and enterprises, of which SDN switch is one typical product of this technology. SDN switch using protocols like OpenFlow well meets the requirements of network virtualization in an open networking environment. Its wide deployment in different network infrastructures is not hard to see in the foreseeable future.
Copyright © 2002-2018. All Rights Reserved.