Light Reading

3 Barriers to SDN Adoption

Mitch Wagner
7/2/2014
50%
50%

While SDN makes sense on technological merits, it faces major barriers to adoption. And those barriers aren't technical.

One major barrier to SDN adoption is cultural. Carrier network engineers are currently hardware operators. They deal with dedicated, physical boxes that need to be transported, hooked up, configured with a command-line interface and occasionally visited in situ. SDN will turn carrier networking upside-down; engineers will become software developers, configuring networks using graphical software and writing code in interactive development environments. The only time they'll get up on their feet is if they have treadmill desks.

The job of being a network operator will change. It requires a lot of retraining and redrawing the lines, circles, and boxes on the org chart. (See The Three Faces of SDN and SDN Faces a Human Hurdle .)

Which leads to the second barrier: Power politics. Many network engineers will be simply unable to make the transition to software networking, and they'll be out of work. People resist being put out of jobs. Even tougher for SDN advocates: Some of these people will be upper management who've built their careers around hardware-defined networks. Many of these people are going to see the shift to software networks as a threat to their position within the company. They see the transition to software networks as a death-struggle, and they'll fight against it with every iota of their being.

Sure, hardware-defined networking has its issues. But people whose job it is to solve problems have a strong vested interest in preserving those problems. (I wish I could remember who said that -- it's brilliant.) If your job is to clean the hair out of the shower drain, you're going to fight like a Klingon against any attempt to eliminate shower-drain-hair as a problem.

But what of the benefits? Software-defined networks are more easily maintained, less expensive in capex and opex (allegedly), and more flexible, permitting the deployment of new services faster to customers.

That all appears to be true, but it's difficult to prove -- which is the third barrier to SDN adoption. SDN exists down deep at the bottom of the network, while financial benefits become obvious high up in the application layers. SDN requires foundational network changes whose benefits are indirect and difficult to quantify immediately.

So what's an SDN advocate to do? Start small, deploying SDN in new services. Do fast projects with quick, demonstrable financial return. Enlist allies in the organization where you can find them, and do your best to navigate around opponents without confronting them.

NFV, often mentioned in the same breath as SDN, represents a way to get SDN in the back door of network operators. Virtualizing a network application like a load-balancer or firewall, particularly if it's customer premises equipment, can be a small, local project with immediate financial benefit. Do enough of those and somebody's going to see that virtualizing the underlying network architecture is a great idea too.

As to the managers and senior VPs who fight SDN as a threat to their survival: Some will come around, some will be proven wrong and sidelined, and for others, you may just have to wait for them to retire. Putting arsenic in their coffee, tempting though it may be, will get you the wrong kind of attention.

— Mitch Wagner, Circle me on Google+ Follow me on TwitterVisit my LinkedIn profileFollow me on Facebook, West Coast Bureau Chief, Light Reading. Got a tip about SDN or NFV? Send it to wagner@lightreading.com.

(9)  | 
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
SDNAT
50%
50%
SDNAT,
User Rank: Light Beer
7/10/2014 | 1:45:27 PM
SDN adoption barriers
As the article says, Yes, SDN make sense, it is inevitable in the future, and certainly brings lot of benefits. 

In my opinion, some of the key barriers are

1. Risk apetite for new technology:  SDN in general perceived to be for Data Centers. DC is where many of key enterprise apps are hosted. With SDN, multiple changes will be made for DC architecture from technology as well as from overall org perspective. All put together enterprises' perceived risk seems higher. 

2. Fear of unknown: Lack of knowledge about SDN among network engineers/operators/managers etc keeps them away from adopting sooner than later. 

3. Lack of standard: Since different vendors are offering different types of solutions for network agility but are all calling them as SDN the customers are confused and not sure which way the technology is heading. So, enterprises want to wait & watch mode.

4. Currently invested (paid off) network solution is working: Currently deployed network architecture and solution are working fine for the most part and business is functioning. So, no immediate urgency for adopting SDN solution. 

 

 
rvrambo
50%
50%
rvrambo,
User Rank: Light Beer
7/8/2014 | 1:00:54 PM
Re: Hyrbid
To be frank much better than the original article.  We need absolute and concrete proof of.

1. OPEX savings (  not slides  )

2. Scalability of the solutions to large carrier networks.

 

SDN adoption is by natute disruptive to the extent that it can effect the company earnings. So any higher ups of the publicly traded carrier networks would think multiple times before signing up on the dottted lines to approve.

Having said that, SDN adoption has to start at a small scale , may at the edge and prove itself  before it can get to core and/or complex services.

 

If you tell some one that, you can exactly the SAME thing using different set of tools with a great promise of the CAPEX but no OPEX to show for in the next 12-24 months.. that's a bound to fail or rejected at the highest levels.

 

For example, they said the same kind of things about reconfigurable optical transport few years back and we all know what happened.

 
Mitch Wagner
50%
50%
Mitch Wagner,
User Rank: Lightning
7/3/2014 | 12:37:23 PM
Re: Hyrbid
Good points. Resistance to SDN isn't foolish, coming from people who demand proof it's ready for prime time before deploying it.
futurephil
50%
50%
futurephil,
User Rank: Light Sabre
7/2/2014 | 7:38:57 PM
Re: and now some specifics...
The word "here" is linked. That doesn't show up on this board, though.
VictorRBlake
50%
50%
VictorRBlake,
User Rank: Moderator
7/2/2014 | 5:03:20 PM
Re: Hyrbid
self editing here, I meant "serious problems" Gotta hate those autocorrect things...
sam masud
0%
100%
sam masud,
User Rank: Light Sabre
7/2/2014 | 4:01:59 PM
Re: Hyrbid
If a well understood and popular technology--Ethernet--took a fair amount of time to develop into a carrier-grade service, then we can expect SDN, which is far more complex, will take much longer to be established in carrier networks. But it will be deployed because its capex advantages are hard to ignore.
sam masud
50%
50%
sam masud,
User Rank: Light Sabre
7/2/2014 | 3:58:06 PM
Re: and now some specifics...
Did you intend to provide a link in your post?
futurephil
50%
50%
futurephil,
User Rank: Light Sabre
7/2/2014 | 2:42:16 PM
and now some specifics...
To sort of pick up where this post leaves off, here are a couple of technical barriers that telcos really are talking about and some advice on overcoming them.
victorblake
100%
0%
victorblake,
User Rank: Lightning
7/2/2014 | 10:49:29 AM
Hyrbid
First -- I have to say that while you make great points about the challenges to adopting SDN, you do not point out all of the shortcomings of SDN and you exaggerate some of the "claims" or benefits of SDN. No matter how much the controllers do people are still going to have to put fiber or copper in the ground or up on poles. I'm pretty sure that won't be done by software. So I think you've neglected about 1/2 of the challenge of the telecom industry and by capex probably something like 80% to 90% of the capital cost of telecoms. Changing the routers, switches, and OSS to even 100% of SDN -- is perhaps like changing the transmission on a car from a mechanical transmission to a software controlled transmission (much as we did with electrical power control on solar race cars I used to work on). You do not eliminte the need for tires, a frame, and the rest of the "hardware" that makes for a car.

Second, like most technologies I think we are likely to see a hybrid approach where SDN will evolve by at first offering APIs into existing forwarding methods (like MPLS and VPLS VPNs) -- and then latter a variety of hyrbird approaches.

Third, even in the long run, SDN has series problems tha have not been addressed. Not the least of these is that centralized control is very very vulnerable -- in fact it is the exact opposite of IP's distributed architecture and would be subject to the same kind of vulnerability of any other centralized control scheme (like SS7). There's always the swing of the pendulum, but to think it will swing fully to centralized and stay there is to ignore all of telecom history.

While you make many great points, your article implies that senior telecom folks are resisting SDN because it is new or software. I don't think that's the case at all. They are resisting it because it has gaping holes, inconsistencies, immaturity, and -- not least of all because if they tried to build a 100% SDN network today -- they could not -- the products and technology just are not there yet. Despite what you think there are many very senior telecom execs with a strong background in CS -- who have taken the industry to where we are with advanced automation. The number of people required per (any measure such as Tbs) has been on a continuous decline. That's due to the efforts of the people you are claiming don't know about software.
More Blogs from Column
What are the main steps that CSPs need to take in order to compete on the digital playing field?
The industry is at an inflection point, and one of the looming disruptors is 5G.
Network architects aiming to upgrade their networks to support agile, open, virtualized services in the 21st century need to consider new criteria when choosing between technology suppliers.
Cable companies still dominate the scene at INTX, the event formerly known as The Cable Show.
What is the best way to support both layer 2 and layer 3 services at the edge of the network that incorporates virtual network functions?
Flash Poll
From The Founder
Last week I dropped in on "Hotlanta," Georgia to moderate Light Reading's inaugural DroneComm conference – a unique colloquium investigating the potential for drone communications to disrupt the world's telecom ecosystem. As you will see, it was a day of exploration and epiphany...
LRTV Documentaries
Cable Eyeing SDN for Headend, Home Uses

5|26|15   |   05:57   |   (1) comment


CableLabs is looking at virtualizing CMTS and CCAP devices in the headend, as well as in-home devices, says CableLabs' Karthik Sundaresan.
LRTV Documentaries
Verizon's Emmons: SDN Key to Cost-Effective Scaling

5|22|15   |   03:53   |   (0) comments


For Verizon and other network operators to ramp up available bandwidth cost effectively, they need to move to SDN and agree on how to do that.
LRTV Documentaries
Lack of Universal SDN a Challenge

5|21|15   |   04:51   |   (3) comments


Heavy Reading Analyst Sterling Perrin talks about how uncertainty about SDN standards and approaches may be slowing deployment.
LRTV Custom TV
Steve Vogelsang Interview: Carrier SDN

5|20|15   |   05:02   |   (0) comments


Sterling Perrin speaks to Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, about the new Carrier SDN-enabling Network Services Platform and the operator challenges it solves.
LRTV Custom TV
Carrier SDN: On-Demand Networks for an On-Demand World

5|20|15   |   20:52   |   (0) comments


Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, talks about requirements and benefits of Carrier SDN during the keynote address at the Light Reading Carrier SDN event May 2015.
LRTV Documentaries
The Security Challenge of SDN

5|19|15   |   02:52   |   (0) comments


CenturyLink VP James Feger discusses concerns that virtualization could create new vulnerabilities unless network operators build in safeguards.
LRTV Custom TV
NFV Elasticity – Highly Available VNF Scale-Out Architectures for the Mobile Edge

5|18|15   |   5:50   |   (0) comments


Peter Marek and Paul Stevens from Advantech Networks and Communications Group talk about their NFV Elasticity initiative and the company's latest platforms for deploying virtual network functions at the edge of the network. Packetarium XL and the new Versatile Server Module: 'designed to reach parts of the network that other servers cannot reach.'
LRTV Huawei Video Resource Center
Bay Area Spark Meetup 2015

5|14|15   |   3:54   |   (0) comments


Developed in 2009, Apache Spark is a powerful open source processing engine built around speed, ease of use and sophisticated analytics. This spring, Huawei hosted a meetup for Spark developers and data scientists in Santa Clara, California. Light Reading spoke with organizers and attendees about Huawei's code contributions and long-term commitment to Spark.
LRTV Custom TV
The Transport SDN Buzz

5|12|15   |   06:01   |   (1) comment


Sterling Perrin, senior analyst at Heavy Reading, speaks with Peter Ashwood-Smith of Huawei and Guru Parulkar of ON.Lab about the evolution of transport SDN and the integration of technologies.
LRTV Custom TV
Next-Generation CCAP: Cisco cBR-8 Evolved CCAP

5|5|15   |   04:49   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explained the innovation design of Cisco's cBR-8, the industry's first Evolved CCAP, including DOCSIS 3.1 design from ground-up, distributed CCAP with Remote PHY and path to virtualization. Cisco's cBR-8 Evolved CCAP is the platform that will last through the transitions.
LRTV Custom TV
Meeting the Demands of Bandwidth & Service Group Growth

5|1|15   |   5:35   |   (0) comments


Jorge Salinger, Comcast's Vice President of Access Architecture, explains how DOCSIS 3.1 and multi-service CCAP can meet the demands of the bandwidth and service group growth.
LRTV Custom TV
DOCSIS 3.1: Transforming Cable From Hardware-Defined Network to Software-Defined Network

4|29|15   |   03:48   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explains how DOCSIS 3.1 can transform cable HFC network to a more agile software-defined network.
Upcoming Live Events
June 8, 2015, Chicago, IL
June 9, 2015, Chicago, IL
June 9-10, 2015, Chicago, IL
June 10, 2015, Chicago, IL
September 29-30, 2015, The Westin Grand Müchen, Munich, Germany
October 6, 2015, The Westin Peachtree Plaza, Atlanta, GA
October 6, 2015, Westin Peachtree Plaza, Atlanta, GA
All Upcoming Live Events
Infographics
Procera has gathered facts, stats and customer experience feedback from a survey of 540 users from across the globe.
Hot Topics
10 Alternate Uses for Tablets
Eryn Leavens, Copy Desk Editor, 5/22/2015
Bidding War for TWC Looks Likelier
Alan Breznick, Cable/Video Practice Leader, 5/22/2015
Charter Seals Deals for TWC, Bright House
Mari Silbey, Senior Editor, Cable/Video, 5/26/2015
Eurobites: Alcatel-Lucent Trials 400G in Czech Republic
Paul Rainford, Assistant Editor, Europe, 5/26/2015
Comcast Targets 6 New Gigabit Markets
Mari Silbey, Senior Editor, Cable/Video, 5/21/2015
Like Us on Facebook
Twitter Feed
BETWEEN THE CEOs - Executive Interviews
On May 29th 10 AM ET, Steve Saunders, founder and CEO of Light Reading, will be drilling into the "pains and gains" of NFV with Saar Gillai, SVP & GM for NFV at Hewlett-Packard Co. (NYSE: HPQ) (HP). He has defined a four-step NFV model describing a sequence of technology innovation. It's a must-read doc for any network architect looking to get to grips with their NFV migration strategy. Join us for the interview, and the chance to ask Saar your NFV questions directly!
With 200 customers in 60 countries, Stockholm-based Net Insight has carved out a solid leadership position in one of the hottest vertical markets going in comms right now: helping service providers and broadcasters deliver video and other multimedia traffic over IP networks. How has Net Insight managed to achieve this success in the face of immense competition from the industry giants?
My ongoing interview tour of the leading minds of the telecom industry recently took me to Richardson, Texas, where I met with Rod Naphan, CTO and SVP, Solutions, ...
Cats with Phones
Too Fluffy to Talk Click Here
Elmer found that his bountiful fur got in the way of meaningful conversation.