An Introduction to Software Defined Networking

2. An Introduction to Software Defined Networking Paul Unbehagen Chief Architect Avaya Networking @punbehagen

3. It’s On! • A friendly competition among presenters • Help @punbehagen win • Easy to remember name • @randy_cross? Too forgettable • Tweet this session with #AvayaATF and #SDN • You could win a iPad Mini… • If you don’t have a twitter account… • Get one, you can delete after the show • Help me WIN by coming to my other sessions (and Tweeting!) • Demystifying Fabrics (#Fabrics) • Deployment Option for Avaya VENA DToR (#dToR)

4. Software defined networking (SDN) is an approach to building computer networks that separates and abstracts elements of these systems. — Wikipedia http://en.wikipedia.org/wiki/Software-defined_networking

5. Technology Evolution Software-Defined Networking is a work-in-progress… Fabrics SDN Which has a long way to go to prove successful

6. Software-Defined Networking • Few, big early adopters, deploying in specific scenarios • Google, et al, that are exercising the privilege of their position to experiment • No clear consensus for the Enterprise on what SDN will ultimately bring, or why • Broad expectation is to deliver ‘network agility’, supporting Cloud-based resource sharing initiatives • Ideally, an Enterprise-class solution would deliver • Automation; bringing the promise of integration • Integration; bringing the promise of agility • Agility; bringing the promise of business advantage

7. Controller What is OpenFlow • Offload the management of network elements to a Central Controller. • Download forwarding state (FIB) from the controller using special protocol • Must provide all the functions of an existing set of networking protocols • And do them at sub-second failover Out of Band Control Plane Download FIB Openflow’s objective is to separate the control plane from the dataplane

8. "The problem is, we actually got it – OpenFlow – wrong, and I think a lot of the industry hasn't realized how wrong it was…” — Martin Casado Founder of Nicira, & co-inventor of OpenFlow http://searchnetworking.techtarget.com/news/2240174517/Why-Nicira-abandoned-OpenFlow-hardware-control OpenFlow networking will require significant changes to your network operations and management. Without a killer app, why change? -CurrentAnalysis

9. What is an SDN? SDN OpenFlow • Many historical examples • Old idea, reintroduced as something “new”. • Powerful, but dangerous • E.g. sweetest of honey pots, target for hacking

10. Early Promoters Where do you fit into this picture...?

11. …when it comes to network virtualization in the data center, OpenFlow for control of hardware forwarding is the wrong way to go — Martin Casado Founder of Nicira, & co-inventor of OpenFlow http://searchnetworking.techtarget.com/news/2240174517/Why-Nicira-abandoned-OpenFlow-hardware-control

12. Data Center Automation Fully realize the possibilities of virtualization… • Network has lagged behind the virtualization of compute and storage • Direct, automated integration with VM administration tools • Seamlessly integrate a holistic virtualization solution • Extend with enhanced automation and optimization

13. SDN will continue to evolveCompeting Solutions available and more appearing [network programmability] ..are important parts of the overall SDN solution, but it’s not aligned with where buyers are today. Programmability could be used to improve network management, but it really doesn’t have any impact on the first two options: simplification of architecture and reduction of hardware costs. - Zeus Kerravala http://www.networkworld.com/community/blog/software-defined-networking-more-just-programmability

14. @punbehagen