The SDN transition: Understanding SDN vendors, concepts and challenges

Last updated:January 2014

Essential Guide

Browse Sections
  • What's necessary in a software-defined network?
  • What to consider before selecting an SDN platform
  • Quiz your SDN vendor before committing
  • Who's who in the world of SDN
  • Don't dismiss startups when considering an SDN platform
  • How will SDN affect your networking staff?

Editor's note

Software-defined networking is leading to major changes in every part of the network. Using a centralized, highly programmable model that separates the control and data planes from the underlying infrastructure, SDN allows for more granular and automated network management. However, the transition to this type of network can be daunting. From understanding the effects on network staff to operational requirements to vendor selection, the move to SDN takes time and preparation. In this guide, SDN expert Ethan Banks breaks down the transition, detailing how to approach SDN vendors, evaluate SDN platforms and understand the core concepts of software-defined networking. 

1What's necessary in a software-defined network?

Enterprise network engineers with highly virtualized data centers have begun to face the same application deployment challenges that cloud providers do: the need for more automation, rapid deployment and more granular configurations. Orchestration tools offer a solution, but while full SDN orchestration software hasn't become commercially available yet, network vendors are partnering with other types of IT vendors to produce controllers that meet some of these challenges. With network orchestration, as well as centralized control and programmability, the goal is to eventually create an environment that supports network virtualization.