<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2975524&amp;fmt=gif">
BLOG

What's the State of SDN?

June 29, 2017

The state of SDN

It feels like there have been two extremes in software-defined networking (SDN) discussions over the last few years. On one side, you have people who focus on the fact that SDN hasn’t lived up to its early hype. And on the other side, you have people continue to pass out predictions for SDN’s future in 2020 and beyond (us included).

But what about right now? You know that SDN is complicated, but it feels like SDN is finally becoming practical. We’re far from SDN perfection, but the current state of software-defined networking lies squarely in the middle of the two extremes.

SDN Use Cases Are Coming to Life

There was a time when the only real example of software-defined networking we could look at was Google’s internal network. It’s a great example, but Google’s SDN project took multiple years and a bank of resources that most companies can only dream of.

However, coming out of this year’s Interop ITX conference, it seems practical implementation of SDN is heating up. Here are just a few examples of enterprises that are becoming more software-defined:

  • FOX Broadcasting Company: On a panel at Interop ITX, FOX VP of engineering and development Thomas Edwards said that anyone who viewed the Super Bowl on the company’s network watched it over SDN. Because SDN gives the company more granular control over network packets, FOX can more efficiently deliver compressed videos to regional stations around the country.
  • Microsoft: This may seem like a similar scenario as Google, but Microsoft is just starting to dip its toes into SDN. The software giant is running an internal pilot with the OpenDaylight open source controller. Rather than trying to redefine the entire data center, Microsoft is starting with a goal of improving Skype’s end-user experience in branch offices.
  • Gap, Inc: Over 1,300 Gap retail locations have received the software-defined treatment since 2015. By implementing software-defined WAN (SD-WAN) technology, Gap has been able to process credit card transactions more efficiently and securely.

When you look at these three examples, you’ll notice that one isn’t like the others. While FOX and Microsoft have moved forward with traditional SDN, Gap is taking a different approach with SD-WAN technology. While both of these approaches fulfill the software-defined concept, they aren’t the same.

>> Download Now: Visibility Architecture in SDN & NFV Environments [Free whitepaper]

SD-WAN Is a Good Introduction to Software-Defined Networking

There are plenty of reasons why SDN isn’t spreading like wildfire throughout enterprise data centers. It can be expensive to implement and requires significant training for networking pros who aren’t familiar with programming languages and how software works.

Rather than diving in headfirst with SDN, you can start smaller with its little brother technology—the software-defined WAN.

While SDN is meant to redefine internal data centers by making them directly-programmable and more scalable, SD-WAN is a technology solution you can purchase from a vendor. You get all the practice with separating the control and data planes without the complicated change and configuration management than comes along with SDN.

Instead, vendors take care of these challenges behind the scenes and you reap the benefits of centralized management and the ability to adjust bandwidth over multiple connections. SD-WAN technology and SDN exist separately, but starting small with SD-WAN can help your networking team lay a foundation that will help deal with more complicated SDN implementation in the coming months and years.

However, just because SD-WAN promises greater accessibility compared to SDN doesn’t mean you can throw architecture best practices out the window.

Double exposure of businessman shows modern technology as concept -2.jpeg

Preparing Your Network to Become Software-Defined

As you look into software-defined technologies, you’ll hear a lot about the benefits of centralized control and network visibility. However, the ability to see and control packets won’t get you very far if you’re dropping packets unknowingly.

Making sure your software-defined connections are carrying every bit, byte, and packet® is essential if you want to realize the potential of SDN (or SD-WAN if you’re starting there).

Looking to add visibility  to your SDN deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do!

SDN and NFV environment visibility architecture

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations

Heartbeats Packets Inside the Bypass TAP

If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.

If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.

While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.

Some of you may have noticed a flaw in the logic behind this solution!  You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.

Glossary

  1. Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.

  2. Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.

  3. Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.

NETWORK MANAGEMENT | THE 101 SERIES