Software Defining Networking

SOFTWARE-DEFINED NETWORKING (SDN)

A Seminar Report submitted in partial fulfillment of the requirement for the award of
the degree of

BATCHELOR OF TECHNOLOGY
in
ELECTRONICS & COMMUNICATION ENGINEERING

by

Chinna Manturu Sravani

21215a0413

Under the esteemed guidance of

Mr. J. Kishore
Assistant Professor

B V Raju Institute of Technology

(UGC Autonomous, affiliated to JNTUH, Accredited by NAAC with A+ Grade &
NBA), Vishnupur, Narsapur, Medak, Telangana State, India, 502313.
2023-2024

ECE Department, BVRIT I

 Software Defining Networking

CERTIFICATE

This is to certify that Seminar Report entitled “TITLE OF THE PROJECT” is being

submitted by Ms. CM. Sravani (21215a0413), in partial fulfilment of the requirement for the award

of the degree of B.Tech in Electronics and Communication Engineering by Jawaharlal Nehru

Technological University (JNTU), Hyderabad is a record of bonafide work carried out by him/her

under my guidance and supervision from 2023 to 2024.

The summary and findings presented in this Seminar Report have been verified and found to be

satisfactory

INTERNAL GUIDE HEAD OF THE DEPARTMENT

Mr. J. kishore, M.Tech(Ph.D) Dr. B.R.Sanjeev Reddy, Ph.D, MIEEE
Assistant Professor Professor & HOD.
Department of ECE. Department of ECE.

EXTERNAL EXAMINER

ECE Department, BVRIT II

 Software Defining Networking

SPECIAL LAB CERFICATE

DEPARTMENT OF ELECTRONICS AND COMMUNICATION
ENGINEERING
CENTRE FOR EMBEDDED SYSTEMS DESIGN

CERTIFICATE
This is to certify that Chinna Manturu Sravani bearing Roll number 21215a0413 has successfully

submitted my seminar report titled “SOFTWARE-DEFINED NETWORKING (SDN)” in

Embedded Automation Laboratory, Electronics and Communication Engineering, BV Raju Institute of
Technology, Narsapur during the period 2023 to 2024

COORDINTOR Head of the Department

Mr. Anirudh Reddy, Ph.D/ M.Tech(Ph.D) Dr.B.R.Sanjeev Reddy,Ph.D, MIEEE
Assistant Professor Professor & HOD.
Department of ECE

ECE Department, BVRIT III

 Software Defining Networking

ACKNOWLEDGEMENTS
(Contact your guide for whom you need to acknowledge)
We take this opportunity to express our indebt gratitude to the persons who contributed for our work,

for being our inspiration and guide which led to the successful completion of the Seminar Report.

We are grateful towards our College Management and our beloved Principal Dr. Sanjay Dubey, Ph.D,

for providing us the necessary infrastructure and facilities that ensured smooth and satisfactory

execution of the Seminar Report

We would like to express our profound gratitude to our head of the department Dr.B R. Sanjeev

Reddy, Ph.D, Professor & HOD, Department of Electronics and Communication Engineering, for his

encouragement, inspiration, close monitoring and guidance he gave meduring the execution of the

Seminar Report

We express our sincere thanks to Mr. J. Kishore (Ph.D), Assistant Professor, /Dept. of ECE, our guide,

for his valuable suggestions and motivation in successful completion of the major project. We also

wish to express our thanks to all the faculty members and laboratory staff that were helpful both

directly and indirectly for the completion of our Seminar Report

Regards
CM.Sravani (21215a0413)

ECE Department, BVRIT IV

 Software Defining Networking

DECLARATION

We hereby declare that the Seminar entitled “SOFTWARE-DEFINED NETWORKING (SDN)”

submitted to B V Raju Institute of Technology, affiliated to Jawaharlal Nehru Technological
University (JNTU), Hyderabad, for the degree of Bachelor of Technology (B.Tech) in Electronics and
Communication Engineering (ECE) is a result of original project work done by us/me.

It is further declaring that the Seminar Report on any part, therefore, has not been previously submitted

to any University or institute for the award of degree or diploma.

Ms. Chinna Manturu Sravani

(21215a0413)

ABSTRACT

ECE Department, BVRIT V

 Software Defining Networking

In a traditional network, each switch has its own data plane as well as the control plane. The control
plane of various switches exchange topology information and hence construct a forwarding table that
decides where an incoming data packet has to be forwarded via the data plane. Software-defined
networking (SDN) is an approach via which we take the control plane away from the switch and
assign it to a centralized unit called the SDN controller. Hence, a network administrator can shape
traffic via a centralized console without having to touch the individual switches. The data plane still
resides in the switch and when a packet enters a switch, its forwarding activity is decided based on the
entries of flow tables, which are pre-assigned by the controller.

The tables dictate the path of incoming data packets through the
respective data planes. However, SDN revolutionizes this structure by
centralizing the control plane within an entity known as the SDN controller,
removing it from individual switches. This centralized control hub empowers
network administrators to orchestrate traffic flow through a unified interface,
eliminating the need for manual adjustments on each switch.

Within an SDN framework, the data plane remains housed within the
switches. As packets traverse the network and reach a switch, their forwarding
trajectory is determined by predefined entries in flow tables. These tables are
programmed and managed by the SDN controller, imparting a dynamic and
responsive nature to the network's behavior. This separation of control and data
planes introduces a level of flexibility and adaptability previously unattainable in
traditional networking architectures.

The pivotal aspect of SDN lies in its ability to abstract and centralize network
intelligence. By consolidating control, administrators gain granular control over
traffic management, quality of service (QoS), and security policies. This
abstraction fosters agility and scalability within networks, allowing for swift
adjustments and optimizations without requiring manual reconfiguration of
individual switches.

Keywords: Networking, administrator, centralize, controller.

ECE Department, BVRIT VI

 Software Defining Networking

CONTENT
CERTIFICATE II

SPECIAL LAB CERTIFICATE III

ACKNOWLEDGEMENTS IV

DECLARATION V

ABSTRACT VI

CONTENTS VII

LIST OF FIGURES VII

LIST OF TABLES VII

1. INTRODUCTION 01

01

ECE Department, BVRIT VII

 Software Defining Networking

ECE Department, BVRIT VIII

 Software Defining Networking

ECE Department, BVRIT IX

 Software Defining Networking

INTRODUCTION:

The definition of Software Defined Networks SDN by the Open Network

foundation (ONF) is the most acceptable. In the SDN architecture, the control
and data planes are decoupled, network intelligence and state are logically
centralized and the underlying network infrastructure is abstracted from the
application. SDN focuses on separation of the control plane from the data
plane, centralized controller and view of the network, open interfaces
between the devices in the control plane (controllers) and those in the data
plane and programmability of the network by external applications.

Legacy data and communications networks are complex and difficult

to manage. They involve different equipment that run complex distributed
control software that is closed and proprietary. Traditional IP networks are
vertically integrated, that is, they have the control and data plane bundled
together. The goal of Software Defined Networks, SDN is to make
networks more programmable. [3]. The programmability of the network is
achieved by means of software applications which run on top the network
operating system (NOS) SDN separates the control and data plane and it
promotes logical centralization of network control and introduces the ability
to program the network. SDN also makes it easier to create and introduce
new abstractions in networking, simplifying network management and
facilitating network evolution. In addition, SDN breaks vertical integration
by separating the two planes; The control plane – which decideshow to
handle network traffic, and the data plane – which forwards traffic
according to the decisions made by the
control plane.

The data plane on the other hand forwards traffic based on rules as
dictated by control plane logic like forward, filter, buffer, rate-limit and
measure packets. Some of the benefits of separating the data and control
plane (SDN) are:

1. Global network view- the controller can see the status of

all routes and switches quickly deciding the best route
2. Horizontal Integration- Separate and independent growth
of hardware and software and flexibility in choosing
hardware and software by customer.
3. Elimination of Middleboxes (Middleboxes are devices
that manipulate traffic for purposes other than packet
forwarding e.g. firewalls, server load balancers, network
address translators etc.)
4. Easier deployment of new network services and prot

ECE Department, BVRIT 1

 Software Defining Networking

HISTORY:
The roots of Software-Defined Networking (SDN) trace back to the early
2000s when networking researchers began exploring the concept of
separating the control plane from the data plane. One of the seminal works
that laid the foundation for SDN was the development of the "OpenFlow"
protocol, introduced by researchers at Stanford University in collaboration
with companies like Google and NEC. OpenFlow emerged as a pivotal protocol
enabling the programmability and centralized control of network devices, a
hallmark of SDN.

In 2008, the Open Networking Foundation (ONF) was formed,

comprised of industry leaders, network operators, and vendors, with the
mission to standardize and promote the adoption of SDN. This consortium
played a significant role in fostering the development and widespread
acceptance of SDN technologies by creating open standards and
specifications that allowed interoperability among various vendors'
equipment.

The commercial interest in SDN gained momentum around 2011 when

major tech companies and networking giants started investing in and
exploring SDN's potential. Companies like Cisco, VMware, and Juniper
Networks began offering SDN solutions and incorporating SDN principles into
their networking products and architectures.

As SDN gained traction, its applications expanded beyond data centers

and enterprise networks. Telecommunication service providers sought to
leverage SDN to increase the flexibility and efficiency of their networks,
leading to the development of concepts like Network Functions Virtualization
(NFV). NFV, in conjunction with SDN, aimed to virtualize network services and
functions traditionally performed by dedicated hardware, further enhancing
network agility and cost-effectiveness.

The evolution of SDN continued with the introduction of Software-

Defined Wide Area Networking (SD-WAN), which revolutionized how
organizations manage and optimize their wide-area networks. SD-WAN
brought centralized management, dynamic traffic routing, and improved
performance to geographically dispersed networks, enhancing connectivity
and reducing operational complexities.

ECE Department, BVRIT 2

 Software Defining Networking

Throughout its history, SDN has undergone continual refinement and

innovation. Its transformative capabilities have reshaped network
architectures, enabling greater flexibility, scalability, and agility. As
technologies evolve and networking requirements continue to grow in
complexity, SDN remains at the forefront, continually evolving to meet the
dynamic demands of modern networking landscapes.
The evolution of SDN extended beyond data centers to other
networking domains. SD-WAN emerged as a prominent application, offering
centralized management and intelligent routing for wide-area networks. This
technology revolutionized how distributed enterprises managed their
networks, providing improved connectivity, cost savings, and enhanced
performance across geographically dispersed locations.
Architectural Framework:

Within SDN's architectural framework, the centralized control plane stands as

the nexus of intelligence and decision-making. This control plane, embodied
by the SDN controller, exercises overarching authority over the network.
Through southbound APIs, the controller communicates directives and
policies to the data plane elements, such as switches and routers. This
separation liberates the network infrastructure from the constraints of
individual device configurations, allowing for uniform management and
dynamic adjustments across the network. The southbound APIs facilitate the
controller's ability to disseminate instructions, employing protocols like
OpenFlow, NETCONF to establish communication with network devices. By
doing so, the controller manipulates traffic flows, implements quality-of-
service measures, and enforces security policies, all in response to real-time
network conditions or specific application demands.

Simultaneously, the northbound APIs serve as the bridge between the SDN
controller and the diverse spectrum of applications operating atop the
network. These applications, ranging from traffic optimization tools to
advanced security suites, utilize the northbound APIs to communicate their
requirements or receive updates on network status. This flexibility allows for
the development and integration of a wide array of software applications,
fostering innovation and adaptability within the network ecosystem.

ECE Department, BVRIT 3

 Software Defining Networking

Moreover, architectural models such as centralized, distributed, and hybrid

SDN configurations offer varying degrees of control and scalability. While the
centralized model places all intelligence within a single controller, distributed
and hybrid models distribute control functionalities across multiple controllers
or combine traditional networking elements with SDN-enabled components,
accommodating diverse network architectures and scaling requirements. This
architectural framework encapsulates the essence of SDN, showcasing its
ability to centralize network control, decouple software intelligence from
hardware limitations, and facilitate a more responsive, adaptable, and
programmable networking environment that aligns with the dynamic needs of
modern digital ecosystems.

SDN Protocols and Standards:

In the realm of Software-Defined Networking (SDN), protocols and standards

play a pivotal role in enabling communication, control, and interoperability
within the network infrastructure. Several key protocols and standards have
emerged to facilitate the functionalities and interactions essential to the SDN
environment. At the forefront stands OpenFlow, a foundational protocol that
gained prominence for its role in separating the control plane from the data
plane. OpenFlow operates as a communication interface between the SDN
controller and network devices, enabling the controller to dictate the
forwarding paths and behaviors of switches and routers. This standardization
of communication allows for centralized network control, dynamic

ECE Department, BVRIT 4

 Software Defining Networking

configuration, and efficient traffic management across diverse networking

equipment, irrespective of vendors.

Complementing OpenFlow is the Network Configuration Protocol (NETCONF)

along with Yet Another Next Generation (YANG) data modeling language.
NETCONF provides a standardized mechanism for configuring network
devices, allowing the controller to remotely manage configurations and
collect device state information. YANG, on the other hand, serves as a
language for modeling the configuration and state data manipulated by
NETCONF, ensuring consistency and coherence in device configuration across
the network. Furthermore, additional protocols like Border Gateway Protocol
(BGP), Multiprotocol Label Switching (MPLS), and Locator/Identifier Separation
Protocol (LISP) contribute to the evolution of SDN functionalities. BGP, a
widely used exterior gateway protocol, has found adaptation within the SDN
landscape, aiding in the exchange of routing information between different
autonomous systems. MPLS, known for its traffic engineering capabilities,
integrates with SDN to enable efficient path selection and provisioning in
network environments. Meanwhile, LISP facilitates scalable routing
architectures by separating IP addresses into location and identifier
components, enhancing mobility and scalability within networks.

These protocols and standards collectively form the backbone of SDN,

fostering interoperability, flexibility, and uniformity across heterogeneous
network environments. Their standardization empowers organizations to
deploy and manage SDN solutions effectively, fostering innovation and
adaptability while mitigating the complexities often associated with diverse
networking infrastructures and vendor-specific implementations. As SDN
continues to evolve, these protocols serve as the foundation upon which new
innovations and advancements are built, driving the transformation of
modern networking paradigms.

Components of Software Defining Networking (SDN):

 SDN Controller: The SDN controller serves as the core component of the
architecture, acting as the centralized brain that oversees and manages
network behavior. It communicates with network devices using protocols like
OpenFlow and provides a centralized point for configuring, controlling, and
monitoring the network. The controller implements network policies, defines
traffic forwarding rules, and orchestrates the flow of data across the network
based on application requirements and network conditions. It abstracts the
control plane from the underlying hardware, allowing for programmability and
automation of network tasks.

Southbound APIs: These interfaces enable communication between the SDN

controller and network devices, such as switches, routers, and access points.
Protocols like OpenFlow, NETCONF, and Open v Switch Database
Management Protocol (OVSDB) are commonly used as southbound APIs. They
allow the controller to instruct the forwarding devices on how to handle and

ECE Department, BVRIT 5

 Software Defining Networking

forward network traffic based on the policies and rules defined by the
controller.

Northbound APIs: Northbound APIs serve as the interface between the SDN
controller and higher-layer network management applications or
orchestration systems. These APIs enable external applications to interact
with the SDN controller to retrieve network information, implement network
policies, and request specific network services. Northbound APIs facilitate
integration with applications for network analytics, security, orchestration,
and other management functions, allowing for enhanced programmability and
automation.

Network Devices (Forwarding Elements): These devices include switches,

routers, access points, and other networking hardware that form the data
plane of the network. In an SDN architecture, these devices operate based on
instructions received from the SDN controller through the southbound APIs.
They forward traffic according to the rules and policies defined by the
controller, allowing for centralized control and management of network traffic
flow.

SDN Applications: SDN applications are software programs that leverage

the programmable nature of the SDN architecture to provide specific network
services or functionalities. These applications can range from network
monitoring and analytics tools to security applications and traffic optimization
solutions. SDN applications interact with the SDN controller through
northbound APIs to utilize network information, implement policies, and

ECE Department, BVRIT 6

 Software Defining Networking

enhance network functionality based on specific business or operational

needs.

SDN-enabled Infrastructure: This encompasses the physical and virtual

networking infrastructure that supports SDN capabilities. It includes hardware
devices that are compatible with SDN principles, such as OpenFlow-enabled
switches or routers, as well as virtualized network functions that can be
dynamically orchestrated and managed by the SDN controller.

Models of SDN:

There are several models, which are used in SDN:

Open SDN
SDN via APIs
SDN via Hypervisor-based Overlay Network
Hybrid SDN
1. Open SDN: Open SDN is implemented using the OpenFlow switch. It is a straightforward
implementation of SDN. In Open SDN, the controller communicates with the switches using
south-bound API with the help of OpenFlow protocol.

ECE Department, BVRIT 7

 Software Defining Networking

2. SDN via APIs: In SDN via API, the functions in remote devices like switches are invoked
using conventional methods like SNMP or CLI or through newer methods like Rest API. Here,
the devices are provided with control points enabling the controller to manipulate the remote
devices using APIs.

3. SDN via Hypervisor-based Overlay Network: In SDN via the hypervisor, the configuration of
physical devices is unchanged. Instead, Hypervisor based overlay networks are created over the
physical network. Only the devices at the edge of the physical network are connected to the
virtualized networks, thereby concealing the information of other devices in the physical network.

ECE Department, BVRIT 8

 Software Defining Networking

4. Hybrid SDN: Hybrid Networking is a combination of Traditional Networking with software-

defined networking in one network to support different types of functions on a network.

ECE Department, BVRIT 9

 Software Defining Networking

Working Of Software Defining Networking (SDN)

At the core of SDN lies the SDN controller, a centralized software platform that acts as the brain
of the network. Through standardized protocols like OpenFlow or NETCONF, the controller
communicates with network devices, such as switches and routers, utilizing southbound APIs.
This communication allows the controller to collect network information, define policies, and
instruct forwarding elements on how to handle incoming traffic.

Upon receiving network state information from these devices, the SDN controller constructs a
comprehensive view of the network topology. It leverages this global visibility to make informed
decisions regarding traffic management, routing, and policy enforcement across the network.
Using sophisticated algorithms and policies, the controller dynamically configures forwarding
tables on the switches or routers, dictating how packets are forwarded based on predefined rules.

The southbound APIs enable the controller to push these forwarding rules and configurations to
the network devices in real-time. This approach provides agility and flexibility, allowing the
network to adapt quickly to changing traffic patterns, application requirements, or network
conditions. Additionally, it centralizes policy enforcement, ensuring consistent application of
security policies, Quality of Service (QoS) settings, and other network-wide rules.

Meanwhile, the northbound APIs of the SDN controller facilitate communication with higher-
layer applications or management systems. These APIs allow external applications to interact
with the SDN controller to retrieve network information, implement network policies, or request
specific services. This interaction enables integration with various applications for network

ECE Department, BVRIT 10

 Software Defining Networking

analytics, monitoring, security, and orchestration, enhancing the overall functionality and
extensibility of the SDN architecture.

By separating the control logic from the underlying hardware, SDN enables network
programmability, automation, and abstraction. It offers administrators unprecedented flexibility in
managing and optimizing their networks, abstracting complexities, and simplifying network
management tasks. The programmable nature of SDN fosters innovation by allowing the
development of custom applications and services that utilize the centralized intelligence of the
SDN controller to address specific network requirements or business needs. SDN operates on a
flow-based forwarding model. When a packet enters a network device (such as a switch), it is
inspected by the device. If the packet matches an existing flow entry in the device's flow table, it
is forwarded according to the predefined instructions associated with that flow entry. If no match
is found, the packet is sent to the SDN controller for decision-making. The controller, based on
network policies and rules, determines the appropriate action for the packet and installs a new
flow entry in the device's flow table. This process of dynamic flow management allows for
efficient packet forwarding and traffic control.

SDN enables dynamic and on-the-fly network reconfiguration. Administrators can modify
network behavior, implement new policies, or reroute traffic in real-time by interacting with the
SDN controller. This dynamic configuration capability simplifies network management, allowing
for rapid adjustments to accommodate changing business requirements or network conditions
without manually reconfiguring individual devices.

SDN's programmable nature facilitates the development of custom network applications tailored
to specific organizational needs. Using APIs provided by the SDN controller, developers can
create applications that interact with the network infrastructure to automate tasks, optimize
performance, enhance security, or enable innovative services. For instance, applications for traffic
engineering, network slicing, quality of service (QoS) management, or even network-wide
monitoring and analytics are possible in an SDN environment.

SDN allows for network virtualization, enabling the creation of logical network segments or
overlays that operate independently of the physical infrastructure. Virtual networks can be
tailored to specific applications, departments, or user groups, enhancing isolation, security, and
resource utilization. This segmentation capability provides flexibility in network design and
enables multi-tenancy support, particularly useful in cloud environments.

Use Cases and Applications:

 Data Center Networking:

ECE Department, BVRIT 11

 Software Defining Networking

Network Virtualization: Creating multiple virtual networks to optimize resource utilization and
enhance scalability within data centers.
Dynamic Traffic Management: Optimizing traffic flow, load balancing, and Quality of Service
(QoS) for data center applications.

 Wide-Area Networking (SD-WAN):

Traffic Optimization: Dynamically routing traffic across multiple network connections (MPLS,
broadband, cellular) based on application needs and network conditions.
Branch Network Simplification: Centralized control and policy enforcement for managing branch
office networks more efficiently.

 Cloud Networking:

Automated Network Provisioning: On-demand provisioning of network resources to support

cloud-based applications and services.
Multi-Tenancy Support: Creating isolated virtual networks for different tenants or customers in
cloud environments.

 Service Provider Networks:

Network Function Virtualization (NFV): Virtualizing network functions to enhance service

agility, scalability, and cost-effectiveness.
Traffic Engineering and Optimization: Optimizing traffic engineering, load balancing, and
bandwidth allocation across service provider networks.

 Security and Policy Enforcement:

Centralized Security Policies: Consistent and granular application of security policies across the
network to enhance overall security posture.
Segmentation and Isolation: Creating secure segments within the network to control traffic flow
and enhance security.

 IoT and Edge Computing:

Edge Network Management: Centralized management and control in edge computing

environments for efficient connectivity and resource allocation.
Low-Latency Applications: Ensuring efficient traffic routing and prioritization for applications
requiring real-time responsiveness at the network edge.

 5G Networks:

Network Slicing: Creating multiple virtual networks over a shared infrastructure to cater to
diverse 5G use cases (e.g., enhanced mobile broadband, low-latency communications).
 Network Monitoring and Analytics:

Real-time Analytics: Collecting and analyzing network data for proactive management, rapid
troubleshooting, and performance optimization.

ECE Department, BVRIT 12

 Software Defining Networking

 Software-Defined Security:

Dynamic Threat Response: Automated threat detection and response mechanisms based on real-
time network intelligence.

 Content Delivery Networks (CDNs):

Traffic Optimization: Dynamically directing traffic and caching resources to reduce latency and
improve content delivery speeds.

Advantages of SDN:

 Rapidly adapt to changing network needs.

ECE Department, BVRIT 13

 Software Defining Networking

 Control the entire network from a single point.

 Reduce reliance on expensive proprietary hardware

 Seamlessly expand network resources.

 Customize network configurations as needed.

 Dynamically optimize traffic flow and routing.

 Implement consistent security policies across the network.

Disadvantages of SDN:

 Implementing SDN can introduce complexity, especially during initial

setup and integration.

ECE Department, BVRIT 14

 Software Defining Networking

 Centralized control poses potential security risks if the controller

becomes a single point of failure or vulnerability.

 SDN's functionality relies heavily on the underlying infrastructure's

compatibility and support for SDN protocols.

 Improperly configured SDN deployments may lead to performance

bottlenecks or latency issues.

 New technologies may introduce unforeseen bugs or errors that impact

network stability.

 Initial investment and transitioning to SDN might involve significant

costs.

ECE Department, BVRIT 15

 Software Defining Networking

ECE Department, BVRIT 16

 Software Defining Networking

ECE Department, BVRIT i