Explore chapters and articles related to this topic
Managing Mobility with SDN: A Practical Walkthrough
Published in Hrishikesh Venkatarman, Ramona Trestian, 5G Radio Access Networks: Centralized RAN, Cloud-RAN, and Virtualization of Small Cells, 2017
Xuan Thuy Dang, Manzoor Ahmed Khan
Other solution-specific functions are also placed in the controller platform. They provide application-specific APIs to the northbound interface and make use of network information from the southbound interface. However, these services interact and rely on the base network functions for common network operations and implement a more intelligent control logic to be applied to the infrastructure. For example, VTN Manager, OVSDB Neutron provides the specific APIs required by a virtual network and OpenStack applications.
SDN and NFV
Published in Dijiang Huang, Ankur Chowdhary, Sandeep Pisharody, Software-Defined Networking and Security, 2018
Dijiang Huang, Ankur Chowdhary, Sandeep Pisharody
The unified control plane of an SDN setup consists of one or more SDN controllers that use open APIs to exert control over the underlying vSwitches or forwarding devices. In addition to pushing forwarding rules to the vSwitches, the controllers also monitor the environment; thereby giving the controllers ability to have forwarding decisions integrated with real time traffic management. The controllers interact with the rest of the SDN infrastructure using three communication interfaces, commonly called the southbound, northbound and east/westbound interfaces. The separation in their functions is as follows: Southbound interface allows the controller to communicate, interact and manage the forwarding elements. While other proprietary solutions exist, OpenFlow is, by far, the most common implementation of the southbound interface. Amongst the proprietary solutions with non-trivial market share are onePK (Cisco) and Contrail (Juniper Networks). An alternate IETF standard, ForCES failed to gain much traction or adoption.Northbound interface enables applications in the application layer to program the controllers by making abstract data models and other functionalities available to them. The northbound interface can alternately be considered an API into the network devices. Unlike OpenFlow for southbound interfaces, there is no overwhelming market leader or accepted standard for northbound interfaces.East/Westbound interfaces are meant for communication between groups or federations of controllers. Similar to the northbound interfaces, there is yet to be a universally accepted standard.
Load balancing for software-defined network: a review
Published in International Journal of Computers and Applications, 2022
Vivek Srivastava, Ravi Shankar Pandey
The basic architecture of SDN is shown in Figure 1. The complete architecture of the SDN is considered into the following parts. Management plane: this part of the SDN architecture is responsible for defining various rules and policies for a network like traffic monitoring, load balancing, application of security.Control plane: This part of the SDN architecture is called the brain of the network. The controller which has the complete view of the network resides on this plane and controls all the data forwarding devices (switches and routers) present in the network.Data forwarding plane: Physical network framework is characterized in this aspect of the design. All the sending devices are interconnected by either wired or remote medium.Northbound interface: The controller at the control plane is connected with different applications present at the management plane; which instruct the controller for different work (load balancing, traffic management, routing, security) by northbound interface [35, 36]. A northbound interface is typically software that abstracts the lower-level instruction sets and uses it as a common interface for developing different applications.Eastbound and Westbound interface: This interface is responsible to establish the communication between the controllers present in the control plane.Southbound interface: This interface is characterized as the guidance set of the sending devices which determines the convention for sending and accepting the data between the control plane and sending devices present in the data forwarding plane.