Software defined network
Download as PPTX, PDF4 likes766 views
This document outlines a presentation on Software Defined Networking (SDN), which separates the data and control planes to improve network management. Key components discussed include the OpenFlow protocol, Procera as a network control framework, and the challenges faced in configuring networks dynamically. The conclusion emphasizes the benefits of SDN for network operators in managing event-driven policies effectively.
Software defined network
- 2. Presentation Outline • Abstract • Introduction • Implementing Network • Why SDN? • SDN and openflow • Open Flow • Procera and Architecture • Conclusion • References
- 3. Abstract • Network Management is really hard and challenging goal • Software Defined Networking (SDN), advocates separating the data plane and the control plane • Problems focused on o Enabling frequent changes to network conditions and state. o Providing support for network configuration o Providing better visibility and control over tasks
- 4. Introduction • Networks typically comprise a numerous types of middle boxes • Network configuration remains incredibly difficult • Network operators are responsible for configuring the network to enforce various high-level policies, and to respond to the wide range of network events (e.g., traffic shifts, intrusions) that may occur.
- 5. Implementing Network • Network policies low-level, are not well equipped to react to continually changing network conditions • State-of-the-art network configuration methods can implement a network policy that deals with a single snapshot of the network state.
- 6. What is SDN? • Software Defined Networking (SDN) is a paradigm where a central software program, called a controller, dictates the overall network behavior. • SDN has two planes • Data plane • Control plane • This paradigm shift brings two benefits compared to legacy methods. • Network wide traffic forwarding decisions in a logically single location, the controller, with global knowledge of the network state.
- 7. Contnd..
- 8. SDN and Openflow • Openflow is one of the most common southbound SDN interfaces. • Open Network foundation • There are a variety of OpenFlow controllers, for example, NOX, Floodlight, and Maestro • There are two interfaces o southbound o northbound
- 9. Component of Open Flow
- 10. Flow Table Rule (exact & wildcard) Action Statistics Rule (exact & wildcard) Action Statistics Rule (exact & wildcard) Action Statistics Rule (exact & wildcard) Default Action Statistics • Flow table in switches, routers, and chipsets Flow 1. Flow 2. Flow 3. Flow N.
- 11. Flow Entry • A flow entry consists of • Match fields • Match against packets • Action • Modify the action set or pipeline processing • Stats • Update the matching packets Match Fields StatsAction In Port Src MAC Dst MAC Eth Type Vlan Id IP Tos IP Proto IP Src IP Dst TCP Src Port TCP Dst Port Layer 2 Layer 3 Layer 4 1. Forward packet to port(s) 2. Encapsulate and forward to controller 3. Drop packet 4. Send to normal processing pipeline 1. Packet 2. Byte counters
- 12. Procera • Procera is a network control framework that helps operators express event-driven network policies that react to various types of events using a high-level functional programming language. • Procera effectively serves as a glue • Procera offers a set of control domains
- 14. Future Work • Demonstrate the feasibility of Procera, but more evaluation on performance and scalability is required • It is not hard to extend Procera to support more control domains; definition and implementation of how a new event will arrive at Procera, and along with what kind of information would make it possible to support more control domains • Procera also supports allow and drop packets
- 15. Conclusion • Network operators and management, have designed and implemented an event driven network control framework on SDN • We use the OpenFlow protocol to communicate between the Procera controller and the underlying network switches. • Network operators use 4 domains
- 16. References • Kim H., and Feamster N., Georgia Institute of Technology, “Improving Network Management with Software Defined Networking”, IEEE communication Magzine, feb 2013, pp 114-119 • <http://www.openflow.org/
- 17. Thank You
Editor's Notes
- #11: 10