Frequently Asked Questions

Rate this content:
0 of 5 - 0 votes
Thank you for rating this article.

It is not possible to give a one sentence answer to this great question.  But I will answer it and provide a great video to watch that explain the implications of it - take a deep breath:

In a nut shell, Software Defined Networking, or SDN, is a network manager defined and network manager controlled way to implement networking solutions and configurations for applications, workloads, and services that is focused on scalable, virtualized and non-virtualized environments.

Think of SDN as a layer of control/management that is wedged between todays control and management planes.  In an SDN world we separate Control and Data planes.  The control is removed from individual network nodes (Switches and Routers) and moved to Controllers.  These controllers then use a protocol called OpenFlow to send commands and instructions to the network nodes.

Screen Shot 2014-10-29 at 10.55.23 AMOpenFlow is an implementation of SDN.  OpenFlow is a communications protocol that uses network centric and aware intelligence.  OpenFlow works on controllers placed in the network (they can be in switches and routers, or as stand alone devices) that enable programmability - or software definition.  You can look more deeply into OpenFlow in our article on the subject.

For example, OpenFlow on controllers can create network slices (subnetworks) to be used for particular applications or workloads.  One can imagine a network slice to be used for a particular video collaboration meeting.  Thus, like VMware has abstracted bare metal servers so multiple Operating Systems can run as Virtual Machines simultaneously and more efficiently on an underutilized physical server, OpenFlow abstracts the network routers, switches, and infrastructure so services and applications can be provided simultaneous network connectivity, privacy, and performance better utilizing the physical network capacity.

SDN, then, is the virtualization of the network.  OpenFlow controllers discover the network topology and the inventory of links as well as information within the network nodes (route tables, addresses, etc.).  Network Administrators define policies and services within the OpenFlow configuration and programmability.

A packet is received by the network.  If there is no prior knowledge associated with the packet, the receiving node sends a message to the OpenFlow controller.  If the controller determines, based on programmability and policy, that the packets should be accepted, the controller modifies the node tables and configurations such that the packet receives the appropriate service.  This can include multiple nodes, as well as more information including oath configuration, QoS information, and much more.

I highly recommend watching the following video to explain the potential impact of SDN.  While this occurred in 2011, it still rings true today.

 

 

I hope that helps you to understand a little more about what a Software Defined Network is.

If you would like to take a deeper dive - check out our free SDN Class.

I hope you find this article and its content helpful.  Comments are welcomed below.  If you would like to see more articles like this, please support us by clicking the patron link where you will receive free bonus access to courses and more, or simply buying us a cup of coffee!, and all comments are welcome!

Comments powered by CComment

Did you learn something?
Did I save you time? 

Buy me a coffeeBuy me a coffee!

Find by Tag

4G Networks 5G Networks 6LoWLAN 6LoWPAN 802.11 802.11ah 802.11ax 802.11ay 802.11az ACL Addressing Analysis Ansible Architecture ARP Assessment AToM Backup Bandwidth BGP Biography Bloom's Taxonomy Briefings CBRS CellStream Cellular Central Office Cheat Sheet Chrome Cisco Clock Cloud Computer Consulting CPI Data Center Data Networking Decryption DHCPv4 DHCPv6 Display Filter DNS Documentation dumpcap ECMP EIGRP Ethernet Ethics Flipping the Certification Model Follow Me Fragmentation Git GNS3 Google GQUIC Hands-On History Home Network HTTPS ICMP ICMPv6 IEEE 802.11p IEEE 802.15.4 In A Day Internet IOS Classic IoT IPv4 IPv6 IS-IS L2 Switch L2VPN L3VPN LDP Linux LLN Logging LoL M-BGP MAC MAC OSx Macro Microsoft mininet Monitoring Monitor Mode MPLS Multicast Name Resolution Netflow NetMon netsh Networking Network Science nmap Npcap nslookup Online Learning Online School OpenFlow OSPF OSPFv2 OSPFv3 OSX Parrot PIM Ping Policy POTS POTS to Pipes PPP Profile Profiles Programming Project Management PW3E Python QoS QUIC Requirements RIP Routing RPL RSVP Rural SAS SDN Security Self Certification Service Provider Services Sharepoint Small Business Smartport SONET Speed SSH SSL Subnetting T-Shark TCP TCP/IP Telco Telecom 101 Telecommunications Telephone Telnet Terminal TLS Tools Traceroute Traffic Analysis Traffic Engineering Training Travel Tunnel Utility Video Virtualbox Virtualization VoIP VRF VXLAN Webex Wi-Fi Wi-Fi 6 Wi-Fi 6/6E Windows Wireless Wireless 5G Wireshark Wireshark Tip WLAN ZigBee Zoom

Twitter Feed