1 / 31

Software-Defined Networking

Software-Defined Networking. Ryan Diller, Thomas Dvorak, Margaret Hoisington, Harry Hubbell, Meghan Weinheimer. Agenda. Need for New Network Architecture Limitations of Current Network Architecture Software Defined Networking OpenFlow Benefits and Cons of OpenFlow Future of SDN

jeb
Download Presentation

Software-Defined Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software-Defined Networking Ryan Diller, Thomas Dvorak, Margaret Hoisington, Harry Hubbell, Meghan Weinheimer

  2. Agenda Need for New Network Architecture Limitations of Current Network Architecture Software Defined Networking OpenFlow Benefits and Cons of OpenFlow Future of SDN SDN Applications Conclusion

  3. Need for New Network Architecture • Networks today are structured in a hierarchical tree, built withlayers of Ethernet switches • This static architecture works well with Client/Server computing • Growing demand for dynamic solutions to computing and storage needs

  4. Need for New Network Architecture • The major trends forcing the need to reexamine current networking technology include: • Changing traffic patterns • The “consumerization” of IT • The rise of Cloud computing • “Big Data”

  5. Changing Traffic Patterns • Shift from “North-South” traffic to “East-West” traffic • Access from any device, anywhere, at any time • Utility Computing Model: • Private, Public, and Combination clouds

  6. The “Consumerization” of IT • The amount of corporate content accessed by personal devices is increasing drastically • IT must accommodate this change while also guarding corporate data and intellectual property and meet compliance mandates

  7. The Rise of Cloud Computing • Substantial growth of Cloud computing services • Provides agility to access applications, infrastructure, and other IT resources • Will require elastic scaling of computing, storage, andnetwork resources

  8. “Big Data” means more Bandwidth • A constant demand for additional network capacity is being fueled by the rise of mega datasets • Requires massive parallel processing on thousands of servers • The result would mean scaling the network to a previously unimaginable size

  9. Limitations of Current Networking Architecture • Static networking protocols • Too complex, closed, and proprietary • Rising capital equipment and operational costs • Root cause: network is built using exceedingly complex devices that implement an increasing number of protocols and use closed and proprietary interfaces

  10. Four Major Limitations 1. Complexity to the point of immobility 2. Inconsistent policies 3. Inability to scale 4. Vendor dependence

  11. Complexity • Absence of fundamental abstraction • IT risks service disruption when adding or removing any device due to the amount of what is affected • Static nature of networks is inefficient with the dynamic nature of today’s server environment

  12. Inconsistent Policies • Expansion of mobile users • Difficult for IT to use a consistent set of access, security, and other policies • Enterprise is vulnerable to security breaches and non-compliance issues with regulation

  13. Inability to Scale • Networks must scale due to demands on the data centers rapidly growing • IT relies on predictable traffic patterns to scale the network, which today are highly dynamic and unpredictable • Network must serve groups of users with different needs

  14. Vendor Dependence • Difficult to respond to changing business needs or user demands • Lack of standard, open interfaces • Limits the customizability of networks to individual environments

  15. Software-Defined Networking (SDN) • Stanford & UC Berkeley 2008 • Treats the network interface as a logical entity through control decoupling • Separates routing from forwarding • SDN is NOT a protocol

  16. How SDN Works • Currently, Physical Routers and Switches are responsible for packet routing and forwarding • SDN uses software to centrally manage what would normally be a hardware responsibility • https://www.youtube.com/watch?v=h7_NJ2KZc5M

  17. SDN - Architecture • Abstraction • Vendor Independence • Agility • Centralized Management

  18. SDN - Abstraction • “Virtual” Networking • Multi-tenancy • Isolated “logical” networks that share the same physical network

  19. Vendor Independence • Open Standards based • Vendor neutral • Network operation instructions through SDN controllers

  20. SDN - Agility • Scalable • Adaptable • Logical networks can be created and torn down at any time • Adjust network-wide traffic flow dynamically • Programmatically configured

  21. SDN - Centralized Management • Global view of network • SDN Controller appears as one logical switch for the entire network • Manage and Optimize network resources on the fly

  22. Applying SDN • Open Networking Foundation • Non-Profit founded in 2011 by Deutsche Telekom, Facebook, Google, Microsoft, Verizon, and Yahoo! • User driven foundation committed to SDN through open standards development • Openflow standard claimed to be the first SDN standard • Manage standards for Openflow, currently on version 1.3.2 as of late 2013 • Cisco, Juniper, VMware all have competing proprietary protocols • However… Both Cisco and Juniper support Openflow in their switches/routers

  23. OpenFlow • Facilitates the communication interface between control and the forwarding layers of an SDN • Moves network control out of the networking switches to logically centralized control software • Openflow protocol is implemented on both sides of the interface • Network Infrastructure devices • SDN control software

  24. OpenFlow Continued • Uses concept of flows to identify network traffic • Flow is a sequence of packets that share header field values • Allows network administrators to define how network traffic should flow through network devices based on patterns, applications, and cloud resources

  25. OpenFlow Protocol • Openflow protocol enables Openflow controller to perform add, update, delete actions within the Openflow switch device • Implemented on top of Secure Socket Layer (SSL) • Openflow protocol supports three types of messages: • Controller-to-Switch - enables configuration and details of flow and group table entries and Packet-out messages • Asynchronous- various status messages to the controller from the switch and Packet-in messages • Symmetric- establishing a connection and maintaining a connection

  26. Benefits of OpenFlow • Higher rate of innovation • Centralized control of multi-vendor environments • More granular network control • Cost-effective • Easy integration with existing networks • Openness • Reduced complexity through automation

  27. OpenFlow Weaknesses • Relatively new software • Standard is still evolving • More integration effort to support multiple vendors day one • Lack of TLS adoption • Denial of service risks • Controller vulnerabilities

  28. The Future of SDN Industry standardsfor SDN solutions Multi-vendor interoperability Hybrid models that combine centralized SDN models with distributed SDN models

  29. SDN Application Cases • Network Analytics • Enables IT to be proactive in meeting application requirements, addressing issues in real time • Web Scaling • For large event-driven traffic volumes enable rapid response to change

  30. Summary • Need for New Network Architecture • Limitations of Current Network Architecture • Software Defined Networking • OpenFlow • Benefits and Cons of OpenFlow • Future of SDN • SDN Applications

More Related