Sdn Networking
Download as PPTX, PDF0 likes91 views
The document summarizes the history and principles of software-defined networking (SDN). It discusses how SDN evolved from separating the control plane and data plane in telephone networks. The Internet Engineering Task Force later proposed standards to apply this concept to data networks, including the OpenFlow protocol. SDN aims to centralize network intelligence in a controller to make the network more programmable and flexible. It separates the network into three layers - the application, control, and infrastructure layers connected through APIs. The centralized controller directs traffic flow without touching individual switches, allowing administrators to shape traffic from a software-based control plane.
Sdn Networking
- 1. Operating Systems And Network MCS (Master Computer Science) Mhd Khaled Alhalabi
- 2. THE HISTORY OF SDN The history of SDN principles can be traced back to the separation of the control and data plane first used in the public switched telephone network as a way to simplify provisioning and management well before this architecture began to be used in data networks. The internet engineering task force (IETF) began considering various ways to decouple the control and forwarding functions in a proposed interface standard published in 2004 appropriately named "forwarding and control element separation" (forces ).The forces working group also proposed a companion SOFTROUTER architecture .Additional early standards from the ietf that pursued separating control from data include the LINUX NETLINK as an ip services protocol and a path computation element (PCE)-based architecture. The open networking foundation was founded in 2011 to promote SDN and OPENFLOW. At the 2014 interop and tech field day, software-defined networking was demonstrated by AVAYA using shortest path bridging (IEEE 802.1AQ)and OPENSTACK as an automated campus, extending automation from the data center to the end device, removing manual provisioning from service delivery.
- 3. SOFTWARE-DEFINED NETWORKING (SDN) Technology is an approach to network management that enables dynamic, programmatically efficient network configuration in order to improve network performance and monitoring making it more like cloud computing than traditional network management. SDN is meant to address the fact that the static architecture of traditional networks is decentralized and complex while current networks require more flexibility and easy troubleshooting. SDN attempts to centralize network intelligence in one network component by disassociating the forwarding process of network packets (data plane) from the routing process (control plane). The control plane consists of one or more controllers which are considered as the brain of SDN network where the whole intelligence is incorporated. However, the intelligence centralization has its own drawbacks when it comes to security, scalability and elasticity and this is the main issue of SDN.
- 5. In a traditional network, the data plane tells your data where it needs to go. the control plane is located within a switch or router. The location of the control plane is particularly inconvenient because administrators don’t have easy access to dictate traffic flow / In traditional network, individual network devices make traffic decisions based on their configured routing tables. Traditional networks rely on physical infrastructure such as switches and routers to make connections and run properly.
- 6. In SDN, an administrator can shape traffic from a centralized control console without having to touch individual switches in the network. The centralized SDN controller directs the switches to deliver network services wherever they're needed, regardless of the specific connections between a server and devices. A software-based network allows the user to control the allocation of resources at a virtual level through the control plane. Rather than interacting with physical infrastructure, the user is interacting with software to provision new devices.
- 8. A typical representation of SDN architecture comprises three layers: the application layer, the control layer and the infrastructure layer. SDN architecture separates the network into three distinguishable layers, connected through northbound and southbound APIs. Northbound API’s connect application layer with control layer while southbound API’s connect control layer with infrastructure layer. The application layer, contains the typical network applications or functions organizations use, which can include intrusion detection systems, load balancing or firewalls. The control layer represents the centralized SDN controller software that acts as the brain of the software-defined network. This controller resides on a server and manages policies and the flow of traffic throughout the network. The infrastructure layer is made up of the physical switches in the network.
- 14. 14 Data Path (Hardware) Control Path OpenFlow OpenFlow Controller OpenFlow Protocol (SSL/TCP) OpenFlow/SDN tutorial, Srini Seetharaman, Deutsche Telekom, Silicon Valley Innovation Center
- 15. 15 Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * 00:1f:.. * * * * * * * port6 Firewall * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * * * * 22 drop OpenFlow/SDN tutorial, Srini Seetharaman, Deutsche Telekom, Silicon Valley Innovation Center Routing * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * 5.6.7.8 * * * port6
- 16. 16
- 17. Message Layer State Machine System Interface Configuration Data Model 17
- 21. Less Downtime
Editor's Notes
- #15: Open Flow is a Standard based Layer 2 Communication protocol used between Controller and Switch
- #17: Generally, Open Flow is mixed with SDN. But this is not true, SDN is not Open Flow. Open Flow is a subset of SDN.
- #18: 1. Message Layer: The message layer is the core of the protocol stack. It defines valid structure and semantics for all messages. A typical message layer supports the ability to construct, copy, compare, print, and manipulate messages. 2. State Machine: The state machine defines the core low-level behavior of the protocol. Typically, it is used to describe actions such as: negotiation, capability discover, flow control, delivery, etc. 3. System Interface: The system interface defines how the protocol interacts with the outside world. It typically identifies necessary and optional interfaces along with their intended use, such as TLS and TCP as transport channels. 4. Configuration: Almost all aspects of the protocol have configurations or initial values. Configuration can cover anything from default buffer sizes and reply intervals to X.509 certificates. 5. Data Model: Another way to consider the OpenFlow protocol is to understand its underlying data model. Each switch maintains a relational data model that contains the attributes for each OpenFlow abstraction. These attributes either describe an abstractions capability, its configuration state, or some set of current statistics.