We Believe It's Time for Some Straight Talk

  • Published on
    16-Jul-2015

  • View
    564

  • Download
    0

Embed Size (px)

Transcript

<ul><li><p> 2013 Juniper Networks, Inc.</p><p>WHEREAS the world is filled with voices shouting the glories of Software Defined Networks (SDNs)1 AND WHEREAS IDC expects the SDN market to grow to $3.7 billion by 2016 ... </p><p>YET 57 percent of enterprises surveyed dont know what SDN is2 </p><p>Its time for a clear look at capabilities, considerations </p><p>and questions to ask your network vendor when </p><p>evaluating hardware for your SDN journey. And yes, its </p><p>time that journey began. Why is that?</p><p>THE OPPORTUNITY FOR SDN IS HUGE (FOR THOSE WHO UNDERSTAND IT).</p><p>What makes SDN so exciting is the promise of what it </p><p>can do. Let us begin with a common truth:</p><p>Businesses are looking for flexibility in the way they </p><p>build and deploy their applications. Business is </p><p>uncertain and changeable. Companies know that they </p><p>must move quickly and devote themselves to building </p><p>killer applications and services to succeed. </p><p>They look to the network to support them. But too </p><p>often, it falls short.</p><p>SDN is the answer. It promises to solve these issues </p><p>and deliver genuine agility to the enterprise and to </p><p>service providers with:</p><p>AUTOMATED PROVISIONING ACROSS YOUR </p><p>CLOUDS. Do not let your virtualized environment limit </p><p>you automate provisioning across public and private </p><p>clouds.</p><p>AGILE DEPLOYMENT OF SERVICES. Deliver faster, </p><p>right to the network edge.</p><p>DYNAMIC TRAFFIC ENGINEERING. Take command </p><p>of traffic flow cross the Wide Area Network (WAN).</p><p>HOLISTIC MANAGEMENT. Simplify management </p><p>of campus network policies for wired and wireless </p><p>devices.</p><p>WE BELIEVE ITS TIME FOR SOME </p><p> STRAIGHT TALK.</p><p>THE BENEFITS OF SDN ARE BIGGER THAN THE NETWORK (SDN IS FOR BUSINESS).</p><p>SDN changes the whole equation for the network, </p><p>turning it from a faceless utility into a powerful driver </p><p>of business agility. It changes our expectations of </p><p>network hardware, and how businesses can and will </p><p>react to the challenges of the future. </p><p>It should not be approached lightly. A solid strategy </p><p>may require 23 years to map out, but this is no reason </p><p>to wait on the sidelines. Real changes that will yield </p><p>immediate results can begin today. This is our call for </p><p>clarity on what to consider, what to look for, and the </p><p>questions you should ask. We say this with a clear </p><p>voice and a clear conscience. Hit us with your hardest </p><p>questions, and judge us by the fairness and truth of our </p><p>answers.</p><p>Q: WHAT WILL NETWORK MANAGEMENT BE LIKE?</p><p>A: EASIER. Users want to manage all of their infrastructure elements including compute, storage </p><p>and the network, all from a single pane of glass. </p><p>Open source initiatives such as OpenStack10 are </p><p>gaining momentum, and commercial options such as </p><p>VMware11 already have an important place in many </p><p>data centers. This enhances the ability of the network </p><p>to adapt dynamically to applications and other </p><p>components of the IT infrastructure.</p><p>Q: WHAT DO YOU SAY TO OVERLAYS?</p><p>A: YES. Overlay networks are increasing in popularity. In looking at how these overlays provide management </p><p>simplification, users have realized that certain </p><p>operational benefits can be achieved for greater </p><p>agility. Because of this benefit, overlays have become </p><p>especially interesting to enterprise customers.</p><p>THE IMPLICATIONS FOR NETWORK OPERATORS ARE CLEAR.</p><p>THERE IS MUCH TO BE DONE. You still need to </p><p>design, provision, manage, operate and troubleshoot </p><p>the network. But an SDN world also requires new </p><p>skills and knowledge. Here are just a few of the </p><p>subjects to study before executing your plan for SDN </p><p>implementation:</p><p>NEW PROTOCOLS AND TECHNOLOGIES. </p><p>Make sure the infrastructure investment you make </p><p>is flexible enough to last.</p><p>OVERLAYS. The new network will be a hybrid </p><p>model which will depend on your choice of </p><p>applications. Very few enterprise apps are 100 </p><p>percent virtualized. A mix of overlay technology </p><p>and physical networks will be the reality for most </p><p>data centers. Network operators will have to </p><p>understand the relationship between the two. </p><p>ORCHESTRATION SYSTEMS. As the </p><p>management of networks shifts away from CLI </p><p>and towards orchestration platforms, the network </p><p>interfaces and integration points (APIs) need to </p><p>be clearly defined, and must deliver automation </p><p>and agility. Examples include network interfaces </p><p>for server, sys-admin, application developers and </p><p>higher-level orchestration systems.</p><p>THE BUYERS JOURNEY: WHEN, HOW AND WHERE TO BEGIN.</p><p>NOW WOULD BE GOOD. Even if your SDN </p><p>implementation will not begin until 2016 or beyond, </p><p>you need to make critical infrastructure decisions </p><p>now. Server refreshes happen. Bring Your Own Device </p><p>(BYOD) is taxing most enterprises. Big Data is both a </p><p>challenge and an opportunity. You can start making </p><p>infrastructure decisions to address today while </p><p>looking forward to the SDN future. Its not about rip-</p><p>and-replace. But its not about waiting for an SDN </p><p>shake out either. The exact future of SDN may </p><p>not be known, but it starts now. Heres how:</p><p>1. INVEST IN THE RIGHT ARCHITECTURE</p><p>Why? The network buying decisions that you make </p><p>today are driven by specific projects such as adding </p><p>scale and capacity, building new applications and </p><p>services, and IT consolidation. SDN wont change that. </p><p>So base your decision on network architectures that </p><p>deliver the features and capabilities you are looking </p><p>forwith a focus on simplified management. </p><p>Why now? The right architecture reduces OpEx for </p><p>managing the physical network (topology, power </p><p>consumption, space and cabling requirements) while </p><p>delivering key features and application performance </p><p>thats reliable and predictable. Just like the foundation </p><p>1 451 SDN research survey42 percent of enterprise have heard of SDN, but not familiar with the details2 IDC/Juniper Nov 20123 OpenStack, OpenStack Grizzly Release, APRIL 4, 20134 Gartner analyst in March of 2013: http://www.channelregister.co.uk/2013/03/19/gartner_virtualisation_market_overview5 GartnerHype Cycle for Networking and Communications, 20126 GartnerPredicts 2013: IT and OT Alignment Has Risks and Opportunities7 451 Research/Juniper Networks SDN Use Case Survey, November 20128 GartnerHype Cycle, ibid9 GartnerPredicts 2013, ibid10 OpenStackGrizzly Release, ibid11 Gartner analyst, ibid12 OpenStackGrizzly Release, ibid</p><p> Copyright 2013 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks </p><p>logo, Junos, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United </p><p>States and other countries. All other trademarks, service marks, registered marks, or registered service </p><p>marks are the property of their respective owners. Juniper Networks assumes no responsibility for </p><p>any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer or </p><p>otherwise revise this publication without notice.</p><p>Q: WHERE ARE WE WITH SDN TODAY?</p><p>A: EARLY. There are SDN implementations in production at some large service providers and mega- </p><p>data centers, but those are currently the exceptions </p><p>and many of the use cases are in pilot phases. </p><p>You may have heard of OpenFlow, one of the first </p><p>SDN protocols. Gartner refers to OpenFlow as </p><p>emerging and predicts broad adoption is still at </p><p>least two years away.8 They also estimate that only </p><p>10 percent of enterprise customers will be using SDN </p><p>implementations to manage their cloud and network </p><p>infrastructures by 2016.9</p><p>Q: WHAT HAPPENS TO MY OLD NETWORK?</p><p>A: IT EVOLVES. Certain physical characteristics of your network will remain relevant even in an SDN </p><p>world. Network operators will still need to operate and </p><p>manage the network. But management approaches </p><p>will evolve from silos to more converged and </p><p>integrated systems for broader orchestration. But how </p><p>seamlessly your network evolves will be determined </p><p>by the choices you make today.</p><p>A physical network thats not complex and thats easy to manage</p><p>Standard and open APIs for integration, interoperability and certification </p><p>Purpose-built, programmable ASICs on core networking platforms</p><p>User experienceReduced OpExSuperior performance</p><p>Agility via integration Automated network </p><p> provisioning</p><p>User experienceFeature velocityCustomizable for your </p><p>environment</p><p>Simplified integration and troubleshooting in SDN environments</p><p>Flexibility and freedom of choice</p><p>Investment protection means no hardware replacement</p><p>Architecture</p><p>Open interfAces</p><p>prOgrAmmAbility</p><p>whAt it is benefits tOdAyincrementAl benefits fOr sdn</p><p>of your house, you dont want to change the </p><p>architecture every couple of years. You have to live </p><p>with your decisions for a long time.</p><p>Why is this important for SDN? Youll have a network </p><p>architecture thats easier to integrate with SDN </p><p>controllers and less cumbersome to troubleshoot. As </p><p>you move forward in your SDN implementation, you </p><p>will still maintain the benefits of OpEx reduction.</p><p>2. THINK IN OPEN STANDARDS</p><p>Why? SDN is no excuse to compromise on the </p><p>characteristics that are currently delivered by </p><p>your network architecture. Look for products (and </p><p>suppliers) that are building towards open interfaces, </p><p>interoperability, certifications, and support for </p><p>protocols and management tools that are prevalent in </p><p>the SDN world. Be sure to ask your network vendor if </p><p>they support:</p><p> OpenFlow protocol</p><p> VXLAN protocol</p><p> NVGRE protocol</p><p> Integration with VMware vCenter</p><p> Integration with VMware vCloud Director</p><p> Integration with NSX</p><p> OpenStack integration</p><p> CloudStack integration</p><p> Puppet and Chef IT automation tools</p><p>Depending on your current infrastructure and your </p><p>expected needs, you may not need all of these. </p><p>But since SDN is still unfolding, the more of these </p><p>you have, the more options youll maintain as SDN </p><p>marches toward its full promise.</p><p>Why now? Commitment in these areas is a clear </p><p>indicator that your network vendor understands how </p><p>to deliver better agility and automation for your </p><p>network. It also ensures they wont lock you into a </p><p>proprietary approach or a protocol solution that may </p><p>become sub-optimal as SDN evolves. </p><p>Why is this important for SDN? You want </p><p>flexibility and choice for management methods </p><p>and tools, along with a clear path for supporting </p><p>SDN controllers in the future. </p><p>3. SEEK FLEXIBLY PROGRAMMABLE HARDWARE</p><p>Why? Remember, its EARLY. New protocols, features </p><p>and orchestration systems may emerge with benefits </p><p>that may be too hard to ignore. And you wont want to </p><p>rebuild your network again. Devices built with flexible </p><p>programmability have the ability to support new </p><p>features and protocols. For example, programmable </p><p>ASICs at the core of the network can enable SDN </p><p>customers to customize their network </p><p>for their needs as SDN evolves.</p><p>Why is this important now? Superior performance, </p><p>ability to scale and power efficiencies are crucial in </p><p>parts of the network such as the data center, campus </p><p>core and WAN edge. Programmable ASICs can provide </p><p>performance for todays requirements and flexibility </p><p>for what may come.</p><p>Why is this important for SDN? Flexible </p><p>programmability is important to protect your </p><p>investment and reduce CapEX in the wake of new </p><p>SDN protocols and encapsulation technologies, and </p><p>allows even more flexibility for customization.</p><p>SDN OFFERS MUCH. THE RIGHT MOVES NOW CAN SET YOU UP FOR THE FUTURE</p><p>Whether youre starting to implement SDN today or </p><p>evaluating it for sometime in the future, be sure to </p><p>ask the types of questions youve seen outlined here. </p><p>We bet youll find that Juniper Networks has the only </p><p>complete strategy and business modelone that can </p><p>ensure the investment decisions you make TODAY are </p><p>the right choices for the FUTURE.</p><p>For more information on SDN and related </p><p>technologies, visit http://www.juniper.net/SDN</p><p>The SDN Chasm Ahead</p><p>15% only</p><p>1% 10% </p><p>of Enterprises are very familiar with SDN5</p><p>market penetration6</p><p>will have SDN deployments by 20167</p><p>56%</p><p>75%more OpenStack developers3</p><p>of virtualization customers use VMware4</p><p>Emergence of Orchestration</p><p>Land of (Overlay) Confusion</p><p>Likely to deploy overlay within 3 years</p><p>80%Unlikely or needmore information12</p><p>VXLAN</p><p>NVGRE</p><p>STT MPLS</p><p>OTV</p><p>OPEN FLOWQinQ</p><p>VPLS</p><p>SPB</p><p>TRILL 20%</p><p>The Right Architecture</p><p>CONTROLLER</p><p>Simple ArchitectureComplicated Architecture</p><p>CONTROLLER</p></li></ul>