Few believe that SDNs provide 100% completely new technologies. It had to derive its features from somewhere however, the difference with an SDN is that it implements features better by being more efficient and easier to manage. Lets take a look.
- Less Expensive: Blah! You can buy a less expensive switch today but, many of us don’t. This is because we want to invest in a reputable vendor with robust features that help optimize the end user experience and assist with securing the infrastructure. Often times, vendor specific feature sets are worth the extra money. Who wants an enterprise class switch without flow exporting capabilities, SNMP, VLANs, 802.1X, load balancing, priority queuing or port mirroring? Sure, you’ll be able to purchase cheap switches to expand your SDN network but, at what cost?
- Software Based: Software Defined Networks are no more software based than traditional networking. This means that we may not have to replace anything. In some cases, customers will not have to replace existing switches and routers because software upgrades could add the SDN features the business needs. Network administrators may not even replace the Network Management Station (NMS). SDN technology is emerging which means that the existing NMS could take on the role of ‘Controller’ in a Software Defined Network. This is especially true if the switches themselves assume much of the forwarding decision logic.
- See the YouTube video on “What is a Software Defined Network”.
- Spend some time to learn more about the SDN Controller and Data Plane responsibilities.
- Fault Tolerance: Most of us have had redundancy built in to the architecture for years and we don’t plan on going without it. How SDNs implement fault tolerance however appears to be an improvement. SDNs claim to maintain better end-to-end visibility into how an outage will impact active connections. When a link goes down, SDNs can intelligently reroute high priority traffic one way and lower priority traffic another in multi-vendor environments. Some vendor implementations claim to do it instantly. Yes, your network might be able to that today but, will it reroute the traffic 3 or 4 hops back in order to avoid the break and still minimize latency?
- Filtering and Security: Your network will witness abnormalities, attacks and insider threats. SDNs do a better job at thinking about security up front as part of the initial configuration. When suspicious traffic is witnessed, SDNs can reroute or even replicate the traffic to a threat detection appliance for further analysis. Sure, several vendors can reroute traffic today without SDNs however, in many cases you have to buy 100% into their unique solution. Centralization is another key attribute here. Imagine a standardized protocol for configuring policies (i.e. ACLs) in a multivendor environment. This sounds similar to SNMP and MIB-II all over again but, more efficient. Smart!
- More Options: This is probably the most significant of these 5 truths about Software Defined Networks. The way this technology is playing out, you may only have to invest significantly into the controller. It is the control plane that claims to deliver much of the intelligence in an SDN but, as stated above, this could likely come at a cost. If you want to scale the solution because you have a high volume of new connections, you can either purchase more intelligent switches or more controllers. Which will scale better, which will cost more? If you work in an environment that is at high risk for network based attacks, a more pricey but, intelligent switch may be able to stop the infiltration quicker before it can spread.