Demystifying Software Defined Networking (SDN)
•
2 likes•691 views
A presentation on SDN given at Barcamp Huntsville on August 23, 2014. This is a high-level overview of one of the tenants of SDN, that of the controller based manipulation of traffic.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Demystifying Software Defined Networking (SDN)
Similar to Demystifying Software Defined Networking (SDN) (20)
More from Matt Bynum
More from Matt Bynum (10)
Recently uploaded
Recently uploaded (20)
Demystifying Software Defined Networking (SDN)
- 1. Demystifying Software Defined Networking BARCAMP HUNTSVILLE 2014 Matt Bynum, CCIE #21753
- 3. Overlays Openflow ASIC’s SDK’s Controllers Orchestration Virtualization and more…
- 4. The network as we have known it… Data PlaneControl Plane Forwarding Path Forwarding Decision Store Information L2/L3 forwarding tables Build Information ARP, routing protocols, MAC Learning Port 1 Port 2 Port 3
- 6. What problem is SDN really trying to solve?
- 11. In 2008, created the Clean Slate Program. “…explore what kind of Internet we would design if we were to start with a clean slate and 20-30 years of hindsight.” Programmable Mobile Internet Mobile Social Networking Stanford Experimental Data Center Lab Internet Infrastructure cleanslate.standford.edu Software Defined Networking &
- 12. Server Switch Openflow Controller Architecture Openflow Controller S/W Northbound API App #1 App #2 App #3 Openflow S/W Agent Southbound API Southbound API opennetworking.org
- 13. TL;DR Software Defined Networking (SDN) Data Plane Forwarding Path Control Plane Forwarding Decision Store Information L2/L3 forwarding tables Build Information ARP, routing protocols, MAC Learning Port 1 Port 2 Port 3 OpenFlow API’s OpenFlow API’s
- 14. The Openflow End Goal Controller orchestrating the network devices Openflow Controller S/W App #1 App #2 App #3 O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW Network Device Network Device Network Device Network Device Network Device
- 15. Old School Networking Major Business App ASIC HW ASIC HW ASIC HW ASIC HW ASIC HW ASIC HW Users Users Users Switches Control Control Control Control Control Control
- 16. OpenFlow in Action Openflow Controller S/W Major Business App O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW O/F Agent ASIC HW Northbound API Southbound API Integration with Controller Users Users Users
- 18. opendaylight.org An Open Source Controller
- 19. Smells like OpenStack. Cisco Brocade Citrix Ericsson IBM Juniper Red Hat Microsoft NEC VMWare A10, Adva, Arista, Ciena, Contexstream, Coriant, Cyan, Dell, Fujitsu, Guavus, HP, Huawei, In Cybe Technologies, Intel, Midokura, Nuage, Pantheon, Plexxi, Plumgrid, Qosmos, Radware, Versa, ZTE Platinum SilverGold
- 20. If you are a networking nerd: • Learn the SDN architecture and concepts • Maybe learn some Python and/or Java • Play around with Puppet for orchestration • Download and install Open Daylight • Don’t worry, programmers aren’t replacing you
- 21. If you are a cloud application developer: • Learn the SDN architecture and concepts • Dig into the Openflow API’s • Download and install Open Daylight • Don’t be mean to the network nerds…pretty please
- 22. If you are an IT Manager/Director/Bossman • Ask your application providers if they are planning to support SDN, and if so, which vendor • Ask your networking vendor/partner what they are planning with SDN • Have your Network nerds and developers learn SDN architecture concepts
Editor's Notes
- The time-honored approach of link oversubscription to provision scalability is not effective with the dynamic traffic patterns in virtualized networks—a problem that is even more pronounced in service provider networks with large-scale parallel processing algorithms and associated datasets across an entire computing pool.
- Adding or moving devices and implementing network-wide policies are complex, time-consuming, and primarily manual endeavors that risk service disruption, discouraging network changes.
- Lengthy vendor equipment product cycles and a lack of standard, open interfaces limit the ability of network operators to tailor the network to their individual environments.