OpenDayLight Load Balanced Switching
- 1. -PRESENTED BY MANASA N KULKARNI “Dynamic Load Balancing on Software Defined Network Managed by OpenDayLight Controller”
- 2. AGENDA Preface Traditional Network v/s SDN Static load balancing v/s Dynamic load balancing Problem Statement Detail view about SDN Detail view on Open Day Light (ODL) controller Overview on network tools Implementation Performance Analysis Conclusion
- 3. PREFACE Traditional networking architectures have many significant limitations that must be overcome to meet modern IT requirements. To overcome these limitations; The Software Defined Networking (SDN) is taking place as the new networking approach. The traditional network system has the control plane and data plane together. Whereas the SDN approaches to build a computer network which separates and abstracts the network into control and data plane. The data plane does an operation of transferring the packets through the network. The control plane with its intelligence are able to instruct the data planes over the network.
- 5. PREFACE CONTINUED... The control plane is a software or logical entity, which processes all the routing decisions taken by the data plane OpenFlow is the most common protocol used in SDN networks which are used to communicate the controller with all the network elements (NE). WHY WE NEED TO LOAD BALANCE? In order to increase the : available bandwidth, maximize throughput, add redundancy, & minimize the latency.
- 7. STATIC V/S DYNAMIC LOAD BALANCING Static load balancing modes do not use node performance information to make distribution decisions. For example, Round Robin is a static load balancing mode that load balances connections between available nodes without measuring the relative performance of those nodes. Dynamic load balancing modes use node performance information to make load balancing decisions. For example, Least Connections is a dynamic load balancing mode that examines the ratio of open connections to nodes through Virtual Servers, and then sends the connection request to the node with the least number of concurrent connections.
- 9. PROBLEM STATEMENT OBJECTIVE Emulate a Software Defined Network (SDN) with emerging technologies like Open Flow and SDN using tools Mininet and Open Daylight Controller. WHAT IS THE PROBEM? There is need for dynamic management of network resources for high performance and low latency of data transmission in a network.
- 10. WHY OTHER APPROACH IS NOT GOOD & WHY DO WE THINK OUR APPROACH IS BETTER? Traditional network of TCP or UDP, use static switches, i.e. load balancing across paths are based on hash calculations of packets. Issue with this approach is that each packet of such a flow follows the single pre-defined path through the network. In case of discrepancy in the path, like a switch breakdown or physical layer damage, packets tend to drop or the other switches need to be manually configured for choosing a different path. This becomes a cumbersome task, as the network grows. Also, disadvantage of hashing is that all links gets the same percentage of hash value.
- 11. Even if the network is hard coded to work in as multipath network, because of the equal capacity issue, efficient load balancing might not be achieved. An alternative solution for this issue is Software Defined Networking (SDN). SDN is a concept where a central controller makes the decision for packet traversal and not the switches. Controller dynamically detects the topology by listening to the switches and calculates available path with less load. Controller then directs the switches with forwarding entries needed for the paths thus efficiently balancing the load with every flow.
- 12. INTRODUCTION TO SDN (SOFTWARE DEFINED NETWORKS) It is one of the approach to the Cloud Computing that facilitates network management and enables efficient network configuration in order to improve network performance and monitoring. It is one of the architecture which aims to make networks agile and flexible. The goal of the SDN is to improve network control by enabling enterprises and service providers to respond quickly to changing business requirements.
- 14. In SDN, a network engineer can shape the 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 are needed. Typically, an SDN controller is an application in a software defined networking architecture that manages flow control for improved network management and application performance. The SDN controller platform typically runs on a server and uses protocol to tell switches where to send packets.
- 15. SDN ARCHITECTURE It comprises of three layers: 1. Application layer 2. Control layer 3. Infrastructure layer In SDN architecture, there are API’S that are usually SDN REST API’S which are used to communicate between the SDN controllers and services and the applications running over the network. Northbound API- it enables the communication between the higher-level components. While the traditional networks, use firewall/load balancer to control data plane behaviour. Southbound API-it enables the communication between the controllers and switches and other network nodes, which is a lower-level components. It further lets the router to identify the network topology.
- 16. LAYERS EXPLANATION APPLICATION LAYER: It contains the typical network applications, which can include detection system, load balancing/firewall. CONTROL LAYER: It represents the centralized SDN controller software, that acts as the brain of the SDN. This controller, resides on a server and it manages policies and the flow of traffic throughout the network. INFRASTRUCTURE LAYER: It is made up of the physical switches in the network. These three layers communicate using respective northbound and southbound API’S. Example: applications talk to the controller through its northbound interface, while-the controller and switches communicate using southbound interfaces.
- 17. HOW SDN WORKS? It is the heart and brains of the network, SDN Controllers provides a centralized view of the overall network, and enable network administrators to pass information (networking rules and polices) to the underlying systems (infrastructure layer - VMs, Virtual Routers & Switches) It encompasses several types of technologies, including- functional separation, network virtualization and automation through programmability. Originally, a SDN technology is focused solely on the separation of the network control plane and data plane. Control Plane- makes the decision about how the packets should be in the network. Data Plane- actually moves the packets from place-to-place.
- 18. BENEFITS OF THE SDN Lower operating costs Centralized network provisioning Cloud abstraction Guaranteed content delivery Less downtime Consideration of end-to-end path Congestion control Dynamic adaptation to topological changes
- 21. WHAT IS OPENDAYLIGHT CONTROLLER?? It is one of the open source SDN project aimed at enhancing software-defined-networking which is hosted by Linux Foundation. It is offering a community-led and industry- supported framework for ODL controller which has been renamed as “Open Daylight Platform”. ODL is implemented solely in software and is kept within its own Java Virtual Machine (JVM). It is open to anyone, including the end users and customers and it provides a shared platform for those with SDN goals to work together to find new solutions. Basically, it is exposed on the northbound APIs, which are used by the applications.
- 22. TOOLS USED: WireShark Python iPerf Mininet OpenFlow Xterm Gnuplot
- 23. MININET Mininet is a network emulator which creates a network of virtual hosts, switches, controllers, and links. Mininet is a software emulator for prototyping a large network on a single machine. Mininet can be used to quickly create a realistic virtual network running actual kernel, switch and software application code on a personal computer. Mininet allows the user to quickly create, interact with, customize and share a software-defined network (SDN) prototype to simulate a network topology that uses Openflow switches.
- 24. OPENFLOW It is an open standard that provides a standardized hook to allow researchers to run experiments, without requiring vendors to expose the internal workings of their network devices. While SDN is the architecture dividing the layers, OpenFlow is just a protocol proposed to convey the messages from the control layer to the network elements.
- 25. HOW IT IS ACHIEVED? Initially, a network topology is to be decided and we decided to be fat-tree topology. To emulate this topology, we have used Mininet, which is an open source network virtualization emulator. We have used another open source software called Open Daylight as OpenFlow controller. Connection between Mininet and Open Daylight can be established and shown in GUI using eclipse API.
- 26. We have written scripts to emulate the Mininet for our requirement. Design an algorithm for Open Daylight API and considering to have an end-to-end controlled network. To generate traffic in network we have used Iperf and by this we measured bandwidth and quality of network link like latency time and performance. After traffic generation, our main motto is to monitor the flows, with respect to port statistics and schedule new flows. Finally, we would like to compare dynamic load balancing (DLB) with static load balancing (SLB) .
- 27. PERFORMANCE ANALYSIS First Scenario Second Scenario Trying to measure the performance at the Aggregation layer Trying to measure the performance at the Core layer This scenario focuses on TCP This scenario focuses on UDP In this scenario, host H1 and H4 have been chosen to perform the load balancing between the hosts. Here, the servers H1 and H6 are chosen to perform the load balancing between them. There is a remarkable increase in the packet flow after running the load balancing script. Jitter reduces to half after implementing load balancing. Also, there is a significant improvement in packet loss making the network perform reliability over data transmission.
- 28. Results of First Scenario Results after Second Scenario LOAD BALANCING THROUGHPU T(Mbits) JITTER(ms) PACKET LOSS(%) LATENCY(ms ) BEFORE 219.2 3.9856 47.6% 0.5293 AFTER 24345.72 0.3663 40.4% 0.4807 LOAD BALANCING THROUGHPU T (Mbits) JITTER(ms) PACKET LOSS(%) LATENCY(m s) BEFORE 201.9 2.0018 39% 0.5151 AFTER 268.9 0.0834 7.8% 0.1372
- 29. CONCLUSION This research creates a base of load balancing experimentation for the SDN research community inspiring more researchers to contribute by improving the performance of diversified networking conditions. load balancing can improve throughput up to 20 percent, reduce the packet loss to 7.8% and 4 times reduced jitter and latency. These results inspire the network industry to implement load balancing for each and every congested networking architecture to obtain optimum resource utilization while the demand for networking is increasing in multiple folds in recent years.