Jordan Martin has a problem. The idea of moving the control plane from a device to a central controller sounds like it makes a lot of sense in SDN. I mean, it’s called a control plane, why not move it to a controller? Despite the phonic similarity, this isn’t actually what happens.
Jordan takes the time to actually define what he means by the control plane, and shows why moving it to a controller makes the network less reliable and more inefficient. It’s an insightful breakdown of why something that seems common sense is much more problematic.
Jordan Martin comments:
One of the more popular misconceptions about SDN is that this new model of networking moves the control plane from a device to a controller. As much as it sounds like a network controller would be the control plane for a network, it simply isn’t true. For some, I believe this mistake is simply a lack of attention to terminology. For others, it’s a fundamental misunderstanding of the way that controller based networking works. Either way, it’s important that we, as network engineers, understand the concept as we move into the brave new world of orchestrated networks.
Read more at: Who Moved My Control Plane
- VMware NSX: Going Big with Micro-Segmentation - May 23, 2017
- DNA Storage is Weird - May 23, 2017
- NetApp and Open Source - May 23, 2017
- What is Big Data? The On-Premise IT Roundtable - May 23, 2017
- NAS Effect: 10TB Western Digital Red Drives - May 22, 2017
- Intel NFV, an SD-WAN Cook-Off, and a Missing Control Plane in Gestalt Networking News 17.6 - May 22, 2017
- “Big Data” Isn’t a Thing - May 19, 2017
- Managed Storage with ClearSky Data - May 19, 2017
- Microsoft Opening Data Centers in Africa - May 18, 2017
- Datrium And Open Convergence - May 18, 2017