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
- A Critique of Network Coding and Automation - August 16, 2018
- Sierra Wireless Misadventures | Gestalt IT Rundown, August 8, 2018 - August 15, 2018
- The Geek Travel Router - August 14, 2018
- AMD’s Second Generation Threadripper Isn’t Quite EPYC - August 14, 2018
- Alastair Cooke – IT Origins - August 9, 2018
- Slack Buying Hipchat is Good for ChatOps - August 3, 2018
- Transcoding with My Little Cluster - August 3, 2018
- AMD Plays the Long Hygon | Gestalt IT Rundown: July 11, 2018 - July 12, 2018
- AIRI: Converging FlashBlade into an AI Reference Architecture - July 12, 2018
- 2018 MacBook Pros Comes Closer to Earning Their Name - July 12, 2018