Software-Defined Networking

(SDN)
MAHDI ZIAEI
 Software-Defined Networking

INTRODUCTION
Software-defined networking (SDN) is a software-controlled approach to networking
architecture driven by application programming interfaces (APIs). SDN leverages a
centralized platform to communicate with IT infrastructure and direct network traffic.
Companies today are looking to SDN to bring the benefits of the cloud to network
management and deployment. With network virtualization, organizations can achieve
greater efficiency through new tools and technology, such as software as a service (SaaS),
infrastructure as a service (IaaS) and other cloud computing services, as well as integrate
via APIs with their software defined network. SDN also increases flexibility and visibility
into network behavior. In a traditional environment, a router or switch whether in the
cloud or physically in the data center is only aware of the status of network devices next
to it. SDN centralizes this information so that organizations can view and control the entire
network and devices. Organizations can also segment different virtual networks within a
single physical network or connect different physical networks to create a single virtual
network, offering a high degree of flexibility. Simply put, companies are using SDN
because it’s a way to efficiently control traffic and scale as needed. While Software-
Defined Networking (SDN) offers numerous benefits, it also comes with several challenges
and limitations:
• Security Concerns :
o Centralized Control : The centralization of the control plane can become a
single point of failure. If the SDN controller is compromised, the entire
network can be affected.
o New Attack Vectors : SDN introduces new attack vectors, such as attacks on
the controller or the communication channels between the controller and
the network devices.
• Scalability Issues :
o Controller Performance : As the network grows, the performance of the SDN
controller can become a bottleneck. Ensuring that the controller can handle
a large number of devices and flows is crucial.
o Network Latency : The additional layer of control can introduce latency,
especially in large-scale deployments.
• Interoperability Challenges :
o Vendor Lock-In : Despite the promise of vendor neutrality, some SDN
solutions may still lead to vendor lock-in due to proprietary extensions or
lack of standardization.
o Compatibility : Integrating SDN with existing network infrastructure can be
challenging, especially if the legacy devices do not support SDN protocols.
• Complexity in Implementation :
o Learning Curve : Implementing SDN requires a deep understanding of both
networking and software development, which can be a steep learning curve
for traditional network engineers.
o Operational Changes : Transitioning to SDN often requires significant
changes in network operations and management practices.
PAGE 2
 • Cost Considerations :
o Initial Investment : The initial cost of deploying SDN can be high, including
the cost of new hardware, software, and training.
o Ongoing Maintenance : Maintaining an SDN environment can also be costly,
requiring continuous updates and monitoring.
• Reliability and Stability :
o Software Bugs : As with any software-based solution, SDN controllers and
applications can have bugs that affect network performance and reliability.
o Network Downtime : Misconfigurations or failures in the SDN controller can
lead to network downtime, impacting business operations.
• Regulatory and Compliance Issues :
o Data Privacy : Ensuring data privacy and compliance with regulations can be
more complex in an SDN environment, especially when using cloud-based
controllers.
o Legal Challenges : Navigating the legal landscape for SDN, especially in
terms of data sovereignty and cross-border data flows, can be challenging.
Despite these challenges, the benefits of SDN often outweigh the limitations, especially
in environments that require high flexibility, scalability, and automation. Addressing these
challenges typically involves careful planning, robust security measures, and ongoing
training and support. Here are a few notable examples of successful SDN deployments:
• University of Pittsburgh Medical Center (UPMC) : UPMC implemented SDN to
enhance its network agility and efficiency. By using SDN, UPMC was able to
virtualize its network, allowing for more flexible and dynamic resource allocation.
This deployment improved the overall performance and reliability of their network,
supporting critical healthcare applications.
• NTT Communications : NTT Communications deployed SD-WAN, an SDN-based
solution, to provide better connectivity and performance for its global enterprise
customers. This deployment allowed NTT to offer more flexible and cost-effective
network services, improving customer satisfaction and operational efficiency.
• Microsoft : Microsoft used SDN in its Azure data centers to manage and optimize
network traffic. By implementing SDN, Microsoft was able to achieve better
scalability, performance, and security for its cloud services. This deployment also
enabled more efficient use of network resources, reducing operational costs.
• Tribune Media : Tribune Media adopted VMware NSX, an SDN solution, to
virtualize its network infrastructure. This deployment allowed Tribune Media to
automate network management tasks, improve security, and enhance the overall
agility of its network. The use of SDN also facilitated easier integration with cloud
services.
• Verizon : Verizon has leveraged SDN to enhance its network services, providing
better performance and flexibility for its enterprise customers. By using SDN,
Verizon was able to offer more dynamic and programmable network solutions,
improving the overall customer experience.
These examples demonstrate how SDN can be successfully implemented across various
industries to achieve better network performance, flexibility, and cost efficiency.

PAGE 3
How SDN Works
To better understand how SDN works, it helps to define the basic components that create
the network ecosystem. SDN architecture is made up of three layers that communicate
using northbound APIs (interfaces that enable lower-level components to communicate
with higher-level components) and southbound APIs that facilitate communication in the
opposite direction. The three layers are:
• Application layer : The application layer includes network applications and
programs. The application layer communicates with the control layer through its
northbound interface, informing the control layer of application resource needs.
Traditional networks might use a dedicated appliance such as a firewall or load
balancer, but software-defined networks instead use an application layer to control
and manage the data plane.
• Control layer : The control layer serves as the brain, or network operating system
that manages the movement of traffic and data. The control layer plays a key role
in resource allocation throughout the network. It is the central layer that enables
communication between the application layer and the infrastructure layer.
• Infrastructure layer : This layer consists of physical switches and routers that move
data packets and network traffic through the network.

In addition to these layers, software-defined networks are built with components that may
or may not be located in the same physical area. These include:
• Applications : Applications are tasked with relaying information about the network
or requests for specific resource availability or allocation.

• SDN controllers : SDN controllers handle communication with the apps to

determine the destination of data packets. The controllers are the load balancers
within SDN.

• Networking devices : Networking devices receive instructions from the controllers

regarding how to route the packets.

PAGE 4
 • Open-source technologies : Programmable networking protocols, such as
OpenFlow, direct traffic among network devices in an SDN network. The Open
Networking Foundation (ONF) helped to standardize the OpenFlow protocol and
other open source SDN technologies.

By combining these components, organizations get a simpler, centralized way to manage

networks. SDN strips away the routing and packet forwarding functions, known as the
control plane, from the data plane or underlying infrastructure. SDN then implements
controllers, considered the brain of the SDN network, and layers them above the network
hardware in the cloud or on-premises. This lets teams use policy based management a
kind of automation to manage network control directly. SDN controllers tell switches
where to send packets. In some cases, virtual switches embedded in software or hardware
replace the physical switches. This consolidates their functions into a single, intelligent
switch that can check data packets and their virtual machine destinations to ensure there
are no issues before moving packets along.
There are several SDN controllers available, each with its own features and use cases. Here
are some notable ones:
• OpenDaylight(ODL) : An open-source platform that provides a modular controller
framework. It’s widely used in both academic and commercial environments.
• ONOS (Open Network Operating System) : Designed for high availability,
performance, and scalability, ONOS is often used in carrier-grade networks.
• Ryu: A component-based SDN framework written in Python. It’s known for its
simplicity and ease of use, making it popular in research and educational settings.
• Floodlight : An open-source SDN controller developed by Big Switch Networks.
It’s Java-based and supports a wide range of network applications.
• Tungsten Fabric : An open-source network virtualization platform that provides a
comprehensive SDN solution, including a controller, analytics, and orchestration.
• NOX/POX : These are among the earliest SDN controllers. NOX is written in C++,
while POX is a Python-based version.
• OpenKilda : A relatively new open-source SDN controller designed for high-
performance and large-scale networks.
• Project Calico : Focuses on providing secure network connectivity for containers
and virtual machines, often used in cloud environments.
These controllers offer various features and capabilities, so the choice of controller often
depends on the specific requirements of the network environment.

What is OpenFlow?
OpenFlow is a key protocol used in Software-Defined Networking (SDN) that allows the
control plane to interact with the data plane of network devices like switches and routers.
OpenFlow is a communications protocol that provides access to the forwarding plane of
a network switch or router over the network. It enables network controllers to determine
the path of network packets across a network of switches. This separation of the control
plane from the forwarding plane allows for more sophisticated traffic management than
traditional methods.
PAGE 5
Key Components of OpenFlow :
• Controller : The central brain of the network that makes decisions about where
traffic should be sent. It communicates with the switches using the OpenFlow
protocol.
• Switches : These are the devices that forward packets based on the rules set by
the controller. They have flow tables that store these rules.
• Flow Tables : Each switch maintains flow tables that contain rules for handling
packets. These rules include match fields (e.g., IP address, MAC address), actions
(e.g., forward, drop, modify), and counters (e.g., number of packets).
How OpenFlow Works:
• Packet Matching : When a packet arrives at a switch, the switch checks its flow
tables to see if there is a matching rule. If a match is found, the switch performs
the specified action (e.g., forward the packet to a specific port).
• Controller Interaction : If no match is found, the switch forwards the packet to
the controller. The controller then decides how to handle the packet and updates
the switch’s flow table with a new rule.
• Rule Installation : The controller can add, modify, or delete rules in the switch’s
flow tables. This allows for dynamic and flexible network management.
Example of OpenFlow in Action :
Imagine a scenario where a network administrator wants to prioritize video conferencing
traffic over regular web browsing traffic. Here’s how OpenFlow can help:
• Define Policy : The administrator defines a policy in the controller to prioritize
video conferencing traffic.
• Install Rules : The controller installs rules in the switches to match video
conferencing packets (e.g., based on IP address or port number) and assign them
a higher priority.
• Traffic Management : When video conferencing packets arrive at the switches,
they are forwarded with higher priority, ensuring better performance for video
calls.

OpenDaylight (ODL)
OpenDaylight (ODL) is an open-source platform for Software-Defined Networking (SDN)
that provides centralized, programmatic control and network device monitoring. It’s
designed to accelerate the adoption of SDN and Network Functions Virtualization (NFV)
by offering a flexible and modular framework.
Key Features of OpenDaylight :
• Modularity : OpenDaylight is highly modular, consisting of over 50 projects that
extend its capabilities. Each project can be independently developed and
integrated, allowing for a customizable and scalable solution.
• Open Protocols : It supports various open protocols, including OpenFlow,
NETCONF, BGP, and PCEP, enabling interoperability with a wide range of network
devices.

PAGE 6
 • Community-Driven : Hosted by the Linux Foundation, OpenDaylight is a
collaborative project with contributions from a large community of developers and
major networking vendors like Cisco and Brocade.
• Network Automation : It provides tools for automating network configuration
and management, reducing the complexity and operational costs associated with
traditional networking.
How OpenDaylight Works :
• Controller : The core of OpenDaylight is the SDN controller, which acts as the
central brain of the network. It communicates with network devices using
southbound APIs and provides network services to applications via northbound
APIs.
• Southbound APIs : These APIs allow the controller to interact with the network
devices. OpenDaylight supports multiple southbound protocols, including
OpenFlow, NETCONF, and SNMP.
• Northbound APIs : These APIs enable applications to interact with the controller.
Developers can create custom applications to manage and optimize network
behavior.
• Service Abstraction Layer (SAL) : This layer abstracts the underlying network
infrastructure, providing a unified interface for network applications.
Example Use Case :
Imagine a data center that needs to dynamically allocate bandwidth to different
applications based on their requirements. Here’s how OpenDaylight can help:
• Define Policies : Network administrators define bandwidth allocation policies
using a network application.
• Controller Implementation : The OpenDaylight controller receives these policies
and translates them into specific instructions for the network devices.
• Dynamic Allocation : The controller communicates with the switches and routers
to dynamically allocate bandwidth based on the defined policies.
• Monitoring and Adjustment : The controller continuously monitors network
performance and adjusts the bandwidth allocation as needed to ensure optimal
performance.
Getting Started with OpenDaylight :
To start using OpenDaylight, you can follow these steps:
• Download and Install : Download the latest version of OpenDaylight from the
official website and install it on a compatible system.
• Set Up the Environment : Configure the necessary network devices and protocols
to work with OpenDaylight.
• Develop Applications : Use the northbound APIs to develop custom network
applications that meet your specific needs.
• Deploy and Manage : Deploy the controller in your network environment and use
it to manage and optimize network behavior.
OpenDaylight provides extensive documentation and a supportive community to help
you get started and make the most of its capabilities.

PAGE 7
Virtualization and SDN
The term “virtual network” is sometimes erroneously used to mean “SDN.” These two
concepts are distinct, but they do work well together. Network functions virtualization
(NFV) segments one or many logical or virtual networks within a single physical network.
NFV can also connect devices on different networks to create a single virtual network,
often including virtual machines. SDN works well with NFV; it assists NFV by refining the
process of controlling data packet routing through a centralized server, improving
visibility and control.

Types of SDN
There are four primary types of software-defined networking:
Open SDN : Open SDN refers to the use of open-source software and standards to
implement Software-Defined Networking. This approach promotes interoperability,
flexibility, and innovation by allowing different network components to work together
seamlessly. Here are a few notable examples of open SDN projects:
• OpenDaylight (ODL) : OpenDaylight is a widely-used open-source SDN controller
hosted by the Linux Foundation. It provides a modular framework that supports
various southbound protocols like OpenFlow, NETCONF, and BGP. OpenDaylight
is used in both research and commercial environments to manage and automate
network configurations.
• ONOS (Open Network Operating System) : ONOS is another open-source SDN
controller designed for high availability, performance, and scalability. It is
particularly suited for service provider networks and large-scale data centers.
ONOS supports a range of southbound protocols and provides a robust platform
for developing network applications.
• OpenContrail : OpenContrail, now known as Tungsten Fabric, is an open-source
network virtualization platform developed by Juniper Networks. It includes an SDN
controller, virtual router, analytics engine, and northbound APIs. OpenContrail is
used to create virtual networks in cloud environments, providing advanced
networking features and analytics.
• Floodlight : Floodlight is a Java-based OpenFlow controller that is easy to use and
extend. It supports a wide range of network applications and is often used in
educational and research settings. Floodlight provides a simple yet powerful
platform for experimenting with SDN concepts.
Example Use Case: Dynamic Bandwidth Allocation
Imagine a university campus network that needs to dynamically allocate bandwidth to
different departments based on their usage patterns. Here’s how an open SDN solution
like OpenDaylight can help:
• Define Policies : Network administrators define bandwidth allocation policies
using a network application.
• Controller Implementation : The OpenDaylight controller receives these policies
and translates them into specific instructions for the network devices.
• Dynamic Allocation : The controller communicates with the switches and routers
to dynamically allocate bandwidth based on the defined policies.
PAGE 8
 • Monitoring and Adjustment : The controller continuously monitors network
performance and adjusts the bandwidth allocation as needed to ensure optimal
performance.
This approach allows the university to efficiently manage its network resources, ensuring
that each department gets the necessary bandwidth without manual intervention.

SDN via APIs : SDN via APIs is a type of Software-Defined Networking where APIs
(Application Programming Interfaces) are used to interact with and control network
devices. This approach allows for more flexible and programmable network management.
Here’s a detailed explanation with an example:
How SDN via APIs Works :
• Northbound APIs : These APIs allow applications to communicate with the SDN
controller. They enable the controller to understand the requirements of the
applications and adjust the network accordingly. Examples include RESTful APIs,
which are commonly used for this purpose.
• Southbound APIs : These APIs enable the SDN controller to communicate with
the network devices (switches, routers, etc.). They allow the controller to configure
and manage the devices. Examples include NETCONF/YANG, OpenFlow, and
SNMP.
Example of SDN via APIs in Action :
Imagine a company wants to implement a dynamic load balancing solution to optimize
the use of its network resources. Here’s how SDN via APIs can help:
• Define Load Balancing Policy : The network administrator defines a load
balancing policy using a network application. This policy specifies how traffic
should be distributed across multiple servers to ensure optimal performance.
• Controller Implementation : The SDN controller receives this policy through a
northbound API (e.g., a RESTful API). The controller then translates this policy into
specific instructions for the network devices.

PAGE 9
 • Device Configuration : The controller uses southbound APIs (e.g.,
NETCONF/YANG) to configure the switches and routers. It sets up rules to
distribute incoming traffic evenly across the servers.
• Dynamic Adjustment : As network conditions change (e.g., one server becomes
overloaded), the controller can dynamically adjust the traffic distribution by
updating the rules on the network devices via the southbound APIs.

SDN via Hypervisor-based Overlay Network : SDN via hypervisor, also known as
hypervisor-based overlay networks, is a type of Software-Defined Networking where
virtual networks are created over physical networks using hypervisors. This approach
allows for greater flexibility and isolation without changing the configuration of the
underlying physical network.
How SDN via Hypervisor Works :
• Hypervisor : A hypervisor is a software layer that allows multiple virtual machines
(VMs) to run on a single physical machine. In SDN via hypervisor, the hypervisor
also manages virtual network overlays.
• Virtual Network Overlays : These are virtual networks created on top of the
physical network. They use encapsulation techniques to tunnel network traffic
between virtual machines across the physical network.
• Virtual Tunnel Endpoints (VTEPs) : These are the edge devices in the virtual
network that encapsulate and decapsulate packets as they enter and leave the
virtual network.
• Controller : The SDN controller manages the virtual network overlays by
communicating with the hypervisors. It sets up the necessary rules and policies for
traffic management.
Example of SDN via Hypervisor in Action :
Imagine a company with multiple data centers wants to create isolated virtual networks
for different departments (e.g., HR, Finance, IT) without changing the physical network
configuration. Here’s how SDN via hypervisor can help:

PAGE 10
 • Create Virtual Networks : The network administrator uses the SDN controller to
create virtual network overlays for each department. These overlays are managed
by the hypervisors running on the physical servers.
• Define Policies : The administrator defines network policies for each virtual
network, such as access controls and quality of service (QoS) rules.
• Traffic Management : When a packet enters the virtual network, the hypervisor
at the Virtual Tunnel Endpoint (VTEP) encapsulates the packet with an additional
header. This encapsulated packet is then sent across the physical network to the
destination VTEP, where it is decapsulated and forwarded to the destination VM.
• Isolation and Flexibility : Each department’s virtual network is isolated from the
others, ensuring that traffic from one department does not interfere with another.
The virtual networks can be easily reconfigured or moved without affecting the
physical network.
Hands-On Example :
To get hands-on experience with SDN via hypervisor, you can use tools like VMware NSX
or OpenStack with Neutron. Here’s a basic example using OpenStack:
• Install OpenStack : Set up an OpenStack environment with Neutron, the
networking component of OpenStack.
• Create Virtual Networks : Use Neutron to create virtual networks for different
tenants or departments.
• Configure Hypervisors : Ensure that the hypervisors (e.g., KVM, VMware) are
configured to support the virtual network overlays.
• Define Network Policies : Use Neutron to define network policies, such as security
groups and QoS rules.
• Deploy VMs : Deploy virtual machines on the created virtual networks and test the
connectivity and isolation between them.

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.

PAGE 11
Choosing the right approach depends on your specific requirements and existing
infrastructure. Let’s compare these options:
• OpenSDN :
o Pros: Provides end-to-end policy control, multitenancy, and analytics. Ideal
for cloud-native environments.
o Cons: May require additional learning curve due to its specific features.
o Use Case: Cloud-native deployments, especially in multitenant scenarios.
• SDN via APIs :
o Pros: Allows programmatic control of network devices. Familiar for network
administrators.
o Cons: Limited to the capabilities exposed by the APIs of specific devices.
o Use Case: Integrating SDN features into existing infrastructure without
major changes.
• SDN via Hypervisor Overlay :
o Pros: Isolates virtual networks without altering physical infrastructure.
Simplifies management.
o Cons: Requires hypervisor support and may introduce overhead.
o Use Case: Virtualized environments, especially in data centers.
• Hybrid SDN :
o Pros: Balances existing network investments with SDN benefits. Gradual
transition.
o Cons: Complexity due to coexistence of traditional and SDN components.
o Use Case: Organizations with legacy networks transitioning to SDN.

Example of SDN in Action

Imagine a company wants to implement a new security policy that blocks access to certain
websites during work hours. Here’s how SDN can help:
• Define Policy: The network administrator defines the security policy in the
application layer using a network application.
• Controller Implementation: The SDN controller receives this policy and translates
it into specific instructions for the network devices.

PAGE 12
 • Network Configuration: The controller communicates these instructions to the
switches and routers in the infrastructure layer, configuring them to block the
specified websites.
• Dynamic Adjustment: If the policy needs to change (e.g., allowing access during
lunch hours), the administrator can update the policy in the application layer, and
the controller will automatically reconfigure the network devices accordingly.

To get hands-on experience with SDN, you can set up a simple SDN environment using
tools like Mininet (a network emulator) and a controller like RYU. Here’s a basic example:
• Install Mininet: Mininet allows you to create a virtual network on your computer.
You can install it on a Linux machine.
• Install RYU Controller: RYU is an SDN controller that you can use to manage your
Mininet network.
• Create a Network: Use Mininet to create a virtual network with multiple switches
and hosts.
• Write a Simple Application: Write a Python script using RYU to control the
network traffic. For example, you can create a script that blocks traffic between two
hosts.
• Run the Network: Start Mininet and run your RYU controller. Your script will
control the network behavior based on the rules you defined.

Benefits of SDN
SDN architecture comes with many advantages, largely due to the centralization of
network control and management. These benefits include:
• Ease of network control : Separating the packet forwarding functions from the
data plane enables direct programming and simpler network control. This includes
configuring network services in real time, such as ethernet and firewalls, or quickly
allocating virtual network resources to change the network infrastructure through
one centralized location.
• Agility : Because SDN enables dynamic load balancing to manage the traffic flow
as need and usage fluctuates, it reduces latency and increases the efficiency of the
network.
• Flexibility : With a software-based control layer, network operators have more
flexibility to control the network, change configuration settings, provision
resources and increase network capacity.
• Greater control over network security : SDN lets network administrators set
policies from one central location to determine access control and security policies
across the network by workload type or by network segments. You can also use
micro segmentation to reduce complexity and establish consistency across any
cloud network architecture whether it’s public cloud, private cloud, hybrid cloud or
multi cloud.
• Simplified network design and operation : Administrators can use a single
protocol to communicate with a wide range of hardware devices through a central
controller. It also offers more flexibility in choosing networking equipment, since

PAGE 13
 organizations often prefer to use open controllers rather than vendor specific
devices and protocols.
• Modernizing telecommunications : SDN technology combined with virtual
machines and network virtualization lets service providers offer distinct network
separation and control to customers. This helps service providers improve their
scalability and provide bandwidth on demand to customers who need greater
flexibility and have variable bandwidth usage.

SDN solutions come with significant benefits but can pose a risk if not implemented
correctly. The controller is critical in maintaining a secure network. It is centralized and,
therefore, a potential single point of failure. This potential vulnerability can be mitigated
by implementing controller redundancy on the network with automatic failover. This may
be costly but is no different from creating redundancy in other areas of the network to
ensure business continuity.

Conclusions
• Enhanced Network Management : SDN provides a centralized and
programmable approach to network management, allowing for more efficient and
flexible control over network resources. This separation of the control plane from
the data plane simplifies network configuration and management.
• Scalability and Flexibility : By abstracting the network control, SDN enables
networks to scale more easily and adapt to changing demands. This flexibility is
particularly beneficial in dynamic environments like data centers and cloud
services.
• Cost Efficiency : SDN can reduce operational costs by automating network
management tasks and minimizing the need for manual intervention. It also allows
for the use of commodity hardware, further lowering expenses.
• Improved Security : With centralized control, SDN can implement consistent
security policies across the network. It also allows for rapid response to security
threats by dynamically adjusting network configurations.
• Innovation and Interoperability : Open SDN solutions, such as OpenDaylight and
ONOS, promote innovation by providing open-source platforms for developing
new network applications. They also enhance interoperability between devices
from different vendors by using standard protocols.
• Real-World Applications : SDN is being successfully implemented in various
sectors, including telecommunications, data centers, and enterprise networks. Its
ability to provide dynamic bandwidth allocation, load balancing, and network
virtualization makes it a valuable tool for modern network management.
• Future Prospects : As networks continue to grow in complexity, the adoption of
SDN is expected to increase. Its ability to provide a more agile and responsive
network infrastructure will be crucial in supporting emerging technologies like IoT,
5G, and edge computing.

PAGE 14
Overall, SDN represents a significant shift in how networks are designed, managed, and
operated, offering numerous benefits that align with the needs of modern, dynamic
network environments.

PAGE 15