The document discusses the challenges and myths surrounding Software-Defined Networking (SDN) adoption, highlighting that only 15% of organizations have implemented SDN. It emphasizes the strategic and functional barriers that need to be addressed, as well as the importance of professional services in facilitating smoother adoption. The key takeaways include the need for clear SDN goals, breaking down organizational silos, and assessing vendor expertise beyond technology attributes.

1. SDN Adoption Challenges
SDN Precon @ ITEXPO Miami
Vimal N Suba
Services Product Manager, Cisco Advanced Services
January 28, 2014

3. Agenda
 State of SDN
 SDN Adoption Challenges
 Easing the Adoption Resistance

4. SDN Myths
A magical wand ...
... that helps achieve NIRVANA
Myth 1:
Software + Cheap Hardware +
Open Source = Lower Cost
Myth 2:
Overnight Revolution
Myth 3:
SDN = Automation
Myth 4:
I don’t need SDN
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
4

5. SDN spending to grow to $35B by 2018.
This represents ~40% of overall
networking spend, and is largely
“substitutive.”
Source: SDN Central, April 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
5

6. Ignoring SDN presents significant risk to
both IT organizations and IT professionals.
…Ignoring SDN will put their company
at a Competitive Disadvantage.
Source: Dr. Metzler at Aston, Metzler & Associates, Dec 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
6

7. SDN Reality
Only 15% of
organizations
have deployed
or are in pilot
with SDN
Source: GigaOm, Aug 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
do not understand
the benefits of SDN
say they have no
clear business
use case
Many have difficulty understanding
and articulating how SDN
technologies will improve
networking in their organization
Cisco Confidential
7

8. SDN & Gartner Hype Cycle
Visibility
SDN is at the peak of inflated expectations*
Peak of
Inflated
Expectations
Plateau of
Productivity
Trough of
Disillusionment
Slope of
Enlightenment
Technology
Trigger
www.gartner.com/technology/research/methodologies/hype-cycle.jsp
*Gartner Networking & Communications Hype Cycle, July 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Maturity
Cisco Confidential
8

9. Are you ready to
ride down this
trough?

10. SDN Adoption Challenges
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
10

11. The Strategic Barriers…
Why
What
How
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
•
•
•
•
Why do I need SDN?
Quantify risk if SDN not embraced
Quantify TCO impact with increased agility
Can SDN help me add revenue generating services?
•
•
•
•
•
What SDN use cases to prioritize?
Kind of SDN app’s should I write?
Impact to infrastructure, operations, etc.?
What if the Control Plane app is broken?
What if the SDN controller is compromised?
•
•
•
•
•
How do I start small and test waters?
Integrate with existing non-SDN infrastructure?
Hire/retrofit right resources for DevOps?
Who will support multi-vendor environment?
Provide expert assistance for apps?
Cisco Confidential
11

12. The Functional Barriers…
•
•
How do I prioritize SDN projects vs.
short term needs?
What SDN scope should I start, and
what success metrics I should define?
Business
•
What SDN architecture is fit for our
network needs?
Application demands
Latency vs. Throughput
Troubleshooting and telemetry
Localized vs. Distributed
Technology
Organizational
•
•
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Does SDN demand new operational
processes?
How to break organizational silos to
embrace SDN?
Cisco Confidential
12

13. “We have 700 applications, with
different owners. They all work with
their business stakeholders. They
are not thinking about the other
guys.” ~CIO
Source: Cisco SDN Focus Groups, 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
13

14. “We use an QoS-specific application
to fix problems, but different regions
and sites run QoS differently. It’s a pain
point for us.”
~ Sr. Technical Decision Maker
Source: Cisco SDN Focus Groups, 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
14

15. Easing the adoption resistance
…Riding down the “trough”
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
15

16. SDN is a potentially disruptive technology
transition; the formulation of best practices for
professional services is nascent yet required for
success
Source: IDC, March 2013
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
16

17. Organizational Due Diligence
…Right Questions to Ask Your Team
Problem definition & Use Cases
Do we have the “right”
stakeholders in the room?
Care-abouts: technology, outcomes,
best-of-breeds, or vendor expertise?
Expertise for Architecture Design or
operational processes?
Who will provide global, 24x7 support
for a multi-vendor SDN solution?
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Where do we need the most
assistance? Which Vendor has
breadth and depth?
Cisco Confidential
17

18. External Due Diligence
…Right Questions to Ask Your Vendor(s)
Can you help us quantify cost vs.
benefits vs. risks? TCO vs. ROI?
Solution impact on team’s working
relationships? New skills needed?
New resources?
Integration w/ existing network?
Expertise for architecture
design? Application
development?
Can you provide an hands-on pilot
in our lab? Is there a reference
design available?
Capabilities do validation testing
with our existing infrastructure?
Support model? For multi-vendor
infrastructure? For SDN applications?
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
18

19. Where Do You Need the Most Assistance?
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
19

20. Top Takeaways…
• SDN is evolutionary, transformative, substitutive and here to stay
• Leverage professional services early to make the best out of SDN
• Clearly define your SDN goals and outcomes
• Experiment and validate your hypotheses
• Break internal silo's; perform through vendor due diligence
• Assess Vendor expertise beyond technology attributes
• Think about who can help “absorb” & “support” new capabilities, at Scale
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
20

21. Thank you.