Notes For SDN
Notes For SDN
(SDN)
By
Linda Rosencrance
Jennifer English, Executive Editor
John Burke, Nemertes Research
SDN architecture
A typical representation of SDN architecture comprises three layers: the
application layer, the control layer and the infrastructure layer. These layers
communicate using northbound and southbound application programming
interfaces (APIs).
Control layer
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 traffic flows throughout the network.
Infrastructure layer
APIs
The switch -- also known as a data plane device -- queries the controller for
guidance as needed and provides the controller with information about the
traffic it handles. The switch sends every packet going to the same destination
along the same path and treats all the packets the same way.
The virtualization aspect of SDN comes into play through a virtual overlay, which
is a logically separate network on top of the physical network. Users can
implement end-to-end overlays to abstract the underlying network and
segment network traffic. This microsegmentation is especially useful for
service providers and operators with multi-tenant cloud environments and cloud
services, as they can provision a separate virtual network with specific policies
for each tenant.
With SDN, an administrator can change any network switch's rules when
necessary -- prioritizing, deprioritizing or even blocking specific types of
packets with a granular level of control and security.
This capability is also a security advantage because the controller can monitor
traffic and deploy security policies. If the controller deems traffic suspicious,
for example, it can reroute or drop the packets.
SDN also virtualizes hardware and services that were previously carried out
by dedicated hardware. This results in the touted benefits of a reduced
hardware footprint and lower operational costs.
Networking innovations
Security
Security is both a benefit and a concern with SDN technology. The centralized
SDN controller presents a single point of failure and, if targeted by an
attacker, can prove detrimental to the network.
Unclear definition
Another challenge with SDN is the industry really has no established definition
of software-defined networking. Different vendors offer various approaches to
SDN, ranging from hardware-centric models and virtualization platforms to
hyper-converged networking designs and controllerless methods.
Market confusion
Some networking initiatives are often mistaken for SDN, including white box
networking, network disaggregation, network automation and programmable
networking. While SDN can benefit and work with these technologies and
processes, it remains a separate technology.
SDN technology emerged with a lot of hype around 2011 when it was
introduced alongside the OpenFlow protocol. Since then, adoption has been
relatively slow, especially among enterprises that have smaller networks and
fewer resources. Many enterprises cite the cost of SDN deployment to be a
deterring factor.
Data center security. SDN supports more targeted protection and simplifies
firewall administration. Generally, enterprises depend on traditional
perimeter firewalls to secure their data centers. However, companies can
create a distributed firewall system by adding virtual firewalls to protect the
virtual machines. This extra layer of firewall security helps prevent a
breach in one virtual machine from jumping to another. SDN centralized
control and automation also enables admins to view, modify and control
network activity to reduce the risk of a breach.
SDN architectures can make network control programmable, often using open
protocols, such as OpenFlow. Because of this, enterprises can apply aware
software control at the edges of their networks. This enables access to
network switches and routers, rather than using the closed and proprietary
firmware generally used to configure, manage, secure and optimize network
resources.
While SDN deployments are found in every industry, the effect of the
technology is strongest in technology-related fields and financial services.
Nearly all the participants in the financial market depend on legacy networks
that can be non-predictive, hard to manage, slow to deliver and vulnerable to
attacks. With SDN technology, organizations in the financial services sector
can build predictive networks to enable more efficient and effective platforms
for financial trading apps.
SDN and SD-WAN share similarities. For example, they both separate the
control plane and data plane, and they both support the implementation of
additional virtual network functions.
However, while SDN primarily focuses on the internal operations within a local
area network, SD-WAN focuses on connecting an organization's different
geographical locations. This is done by routing applications to the WAN.
Before we move deeper with the SDN Controllers, let us understand what is SDN and
SDN Controller. Software-Defined Networks (SDN) : It is one of the biggest and on-
going platforms in the area of Networks which makes the network flexible and agile.
SDN overcomes all the demerits of Traditional Networks. The main aim of the SDN is to
control the network with the help of controllers. SDN is the future of Networking. As
there is a rise in the storage and servers, the SDN introduces a new concept called
“Network Function Virtualization (NFV)“. SDN architecture forms three major layers
namely as:
1. Infrastructure Layer
2. Control Layer
3. Application Layer
Let’s discuss one by one. Infrastructure Layer : Infrastructure Layer consists of
Networking Devices like Switches, Routers and it is also called a Data Plane. Control
Layer : Control Layer consists of Controllers which controls the in and outflow of the
data packets with the help of a controller. Let us understand the different controllers in
detail. Application Layer : Application Layer consists of networking applications like
monitoring, traffic control, network analysis, and security. SDN Controllers : As
discussed in the previous section, controllers are present in the mid-layer. They are
numerous SDN Controllers, namely as:
1. Ryu
2. OpenDay Light
3. Ryu Controller
It is one of the SDN controller specially designed for the agility of the network and for
managing the higher traffic rate. Ryu includes well-defined software components along
with API. Ryu makes the developers develop a new application and manage various other
networking devices. Ryu controller is written in Python. Quick start with the Ryu
Controller. Run all the below commands in your Ubuntu system or in the VMWare
Workstation which is pre-installed with the SDN OVA file.
// Python
pip install ryu
To Install the Ryu from the git repository follow the following commands as follows.
git clone https://github.com / faucetsdn / ryu.git
cd ryu; pip install
OpenDay Light (ODL) Controller : ODL is one of the most versatile and largest open-
source controllers. It is helpful for automating larger area networks and it is scalable.
ODL is written in Java. Compared to all other SDN Controllers, this controller is the best
out of all and it is well-known for its security. Below are the commands to install the
controller and run it.
// For Java
$wget https : // nexus.opendaylight.org/content/repositories/
opendaylight.release/org/opendaylight/integration/
opendaylight/0.12.1/
opendaylight-0.12.1.zip
$unzip opendaylight
- 0.12.1.zip $yum install java
- 11 $export JAVA_HOME
= / usr / lib / jvm / jre - 11 $cd / root /
opendaylight - 0.12.1 $./ bin / karaf