Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

6 week online course

reserve a seat
back to overview

The Biggest Problem of SDN

A few weeks ago I decided to join the SDN group on LinkedIn and quickly discovered the biggest problem of SDN – many people, who try to authoritatively talk about it, have no idea what they’re talking about. Here’s a gem (coming from a “network architect”) I found in one of the discussions:

The SDN local controller can punt across to remote datacenters using not only IP, but even UDP over MPLS

Do I have to explain how misguided that statement is?

Focus on fundamentals

Regardless of what people want to believe, the N in SDN still stands for Networking, so it might help to have a good understanding of networking fundamentals before trying to understand what SDN is all about.

Also, most packet forwarding in SDN world still involves a hardware component – even with software-only packet forwarding (example: x86 server using DPDK), the actual packet transmission happens in hardware (Ethernet NIC) – so we cannot just willy-nilly reinvent the protocol stacks; we have to work with whatever the hardware is capable of receiving, forwarding and sending. Oh, and you also cannot change the laws of physics or speed of light.

Don’t repeat the sound bytes

I hate it when intelligent people with years of networking experience parrot sound bytes like “SDN is separation of control and data planes” without realizing that doesn’t make much sense, or understanding the difference between centralized control and centralized control plane or the nuances involved.

Please don’t be one of them. Take your time to understand the intricacies of these concepts, or at least don't spread other people's misunderstandings.

Shameless plug: you can dig through my SDN-related blog posts, or start with free SDN webinars, continue with my SDN books, and dive deeper with advanced SDN training or SDN workshops.

The best place to start your journey is my SDN resources page.

All that glitters is not gold (or software-defined)

Do realize that (A) plenty of the software-defined magic is a rehash of old concepts and (B) you don’t need SDN just because.

Here’s another gem I found in that same SDN group: “You cannot have NFV without SDN,” which is yet again a total misconception. Some production NFV deployments (like Deutsche Telekom Terastream project) have very simple transport networking requirements – IPv6 on CPE-facing VLAN and IPv4 on Internet-facing VLAN – and need no software-defined magic to get the job done.

If you want to do complex per-tenant VNF deployment, then you do need service insertion capabilities, and the best way to implement their orchestration is through an SDN controller, but that does not mean you MUST have an SDN controller to get NFV up and running. You’ll learn more about these concepts in my NFV webinar.

Finally, on the topic of glittering magic, this is what one of my journalist friends had to say about Software Defined WAN after doing tons of research: “The more I learn about SD-WAN, the less convinced I am that the "software-defined" means anything at all in this context.”

8 comments:

  1. Just want to point out that most of the links in post are mailto urls. :/

    ReplyDelete
    Replies
    1. Yes, I'm an idiot :( Fixed, thank you!

      Delete
  2. Abhishek Verma19 August, 2015 17:16

    Not sure i understand why the post is titled "The biggest Problem of SDN". I was looking at something really insightful. What i found instead was a general rant on how clueless some folks are when they speak about SDN -- This really isnt a problem of SDN. Would you agree?

    ReplyDelete
    Replies
    1. Well, the title was a bit tongue-in-cheek ;)

      On a more serious note, I do think that all the BS that is circulating around does more harm to SDN than anything else (including ideas that are obviously faulty like "centralized control plane"), particularly if it's propagated by people who are supposed to know better.

      For more insightful content, do browse my other SDN-related posts. There are currently almost 230 of them and I'm positive you'll find one or two interesting.

      Kind regards,
      Ivan

      Delete
  3. Whatever is in powerpoint is SDN and what is production is NOT SDN :-)

    ReplyDelete
  4. LinkedIn reminds me of Internet in the late 90's - early 00's when it was finally reaching the broader audience and before spam filters were invented - when anyone could just send any email to anyone else or join a mailing group and start spamming there and no one wanted to do anything about it. Good articles on LinkedIN are like rare gems amongst a sh*tstorm of marketing fud, recruiter ads and pandemic new job congratulations. i feel like going there and endorsing someone for their 'IP' skill.

    ReplyDelete
  5. Can we say centralized some of control plane functions in the place of centralized control plane? I

    ReplyDelete
    Replies
    1. That would make way more sense, but unfortunately that doesn't seem to be where most controller development effort is spent.

      Delete

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Sidebar