Department : ECE

Guide : Dr. Navin Kumar Kumar Akshay :BL.EN.U4ECE16096

Geethika Kunakuntla :BL.EN.U4ECE16097
Mrinal Chandra V. :BL.EN.U4ECE16114
 AGENDA

• Objective
• Introduction
• State of Art
• Methodology
• Study and Investigation
• Initial Design/ Partial Output
• Conclusion and Future Scope
 OBJECTIVE

• To study and investigate Software Defined Networking

• To study and investigate Network Virtualization
Introduction:
Traditional Network vs Software-Defined-Networking :

vs
 Related Technology

 NFV
 VB
 Linux(Ubuntu)
 Open daylight
 Mininet
 Python
Introduction of the req. Tech

 NFV :  Three Layered:

 Hardware layer
 Virtualization Layer ( Hypervisor )
 VNF Layer

 NFV Manager & Orchestrator.

• Network Architecture that separates the network data plane from the
control plane.

• Separation allows a network operator to control network behaviour from a

single high-level control program.

• Data plane is programmable switches and the controllers controls how it is

forwarded.

• There're various domains in which SDN applications can make network

management easier
 Comparison of SDN with Conventional
Network Architecture

• Presently, network devices particularly routers and

switches are bundled with a specialized control
features and various features.

• SDN is easier to co-ordinate.

• Reason about
 NETWORK VIRTUALISATION
• Representation of one or more logical network topologies on
the same infrastructure.

• Virtualizing a network consists of separating software from

hardware.

• Same server and hardware can be used for several purposes

depending on the software installed.

• Packages of these software are kept in different machines

which forms NFV.

• Interconnection of NFV is managed from a central control

plane which is known as SDN.
 BENEFITS

• Reduced Hardware & Power Consumption.

• There is no need to apply time-consuming manual security updates to

each server, install new cabling to extend network provisioning, or
troubleshoot individual machines.

• Sharing

• Network virtualization allows business to respond to market demands

with agility, expanding the services demanded by a specific group of
users or providing new services as your business evolves.
 Literature survey:

• Problems with the existing Network Architecture:

• Obstacles in development and deployment of new
applications of the internet, IPv6.
• Cutting edge technologies like Big Data Analytics , AI are not
being able to be completely explored.
• Improvement in DATA CENTERS required.
• Providing better Qos Services.
We therefore need a better Network Architecture to cope up with
the upcoming demands.
Use Cases:

• Service Providers Network Architecture

• Data Center Improves
• Controlling Large amount of Network Traffic.

• Network Slicing
• Dividing of available resources/Infrastructure into Slices and allow multiple
instances to co-exist.
• Each Slice has its own Packet forwarding mechanism
• It acts similar to Multiplexer.(Hypervisor)

• Wireless Setting
• Dynamic channel configuration.
The Open Network Foundation

• Organization dedicated to the development of SDN Architecture.

• Emphasizes on OpenFlow Protocol.
• Created groups with equipment vendors and multiple other vendors.
• It has also created a standard for commercial applications of SDN and its
deployment.

• Open Flow Protocol

• It has 4 interfaces:
• NBI – DATA exchange between SDN Controller and the Application.
• SBI – API’s exposed to lower layers that allows Externalization.
• EBI – Allows Connection between Traditional IP and SDN network
• WBI – It is a channel between Control planes of Different SDN Domains.
OpenDaylight

• It is developed by the LINUX Foundation.

• It is a Graphic interface that enables the USER to visualize :
• the architecture/Topology created.
• Network Configuration.
• The Open Daylight project provides a common controller
infrastructure,
• protocol plug-ins,
• SDN applications,
• virtual overlay networks
• Active YANG – models for network topologies.
 Challenges
Security Challenges in SDN
• Security is minimally specified in SDN.
• Security of the controller
• Attack in denial of services
• Attack through spoofing
• Thus the Open – Flow does not account to ensure data
integrity.
• Require more sophisticated encryption and authentication
mechanisms .
• Usually apply TLS Sessions to provide secure channels on both
ends.
Research paper 2

• Installing all the required soft wares and technical

requirements of the system.
• Usage of Linux to Operate on Mininet and Open Daylight.
• Create different topologies using Mininet.
• Visualize them on the graphic interface – Open Daylight.
RESEARCH PAPER 3: SDN

Introductio
n
• Separate data forwarding plane from control plane by
centralizing network stage.
• Doses not have to deal with complicated and distributed
information and decision making.
• Can be implemented in software by any vendors and
can be communicated with network devices through
communication channel.
• Programmability
• Openness
• In SDN network architecture there are three
main layers:
1) Infrastructure layer or data plane
2) Control Layer or control plane
3) Application Layer

• It can be implemented through

OpenDaylight software.
Research paper 4: Network Virtualization

• Virtualisation is transparent abstraction of digital

computing platform that supports multiple logical
views of their properties.
• Single physical network appears as multiple logical
networks.
• Each virtual network is a collection of virtual nodes and
virtual links.
• Historical perspective :
1) Virtual LAN
2) Virtual Service Network
3) Virtual Private Network
4) Active and Programmable Network
Research Paper 5: Mininet

• Implementing network with large number of network devices

very difficult and costly
• Mininet has capability to emulate different kinds of network
element such as – host, layer 2 switches, layer 3 routers and link
• Flexibility
• Applicability
• Interactivity
• Scalability
• Sharable
 METHODOLOGY

To set up the host virtual SDN environment, we are trying to do the same in four
steps -
They are:
• Initial Host set-up
• Setting up the Mini-net Virtual machine
• Configuring the Virtual Programmable Flow Controller (PFCs)
• Building the SDN and configuring VPNs

We will be working on Virtual machines and a network emulator- mininet to

create a network of virtual hosts, switches, controllers and links, it supports
OpenFlow for highly flexible custom routing and SDN
PRACTICAL IMPLEMENTATION
Pre - requisites
• Basic Knowledge of Virtual Machine and how to work on it.

• Should know how to work on Unix/Linux

• Understanding of Mininet and Opendaylight working

• Able to write programs in Java and Python.

• Knowledge of Computer Networking.

• Good Understanding of software defined networking and Network
Virtualisation
System Configuration:
16 GB Ram and i7 Processor

Software and Tool used

1.Oracle VM Virtual Box
2.Mininet
3.Ubuntu Operating system on Virtual Box
4.Opendaylight Controller
MININET

• Mininet creates a realistic virtual network, running real

kernel, switch and application code, on a single machine
(VM, cloud or native), in seconds, with a single command.

• Mininet is useful for development, teaching, and research.

• Mininet also allows you to use custom remote controllers

and custom switches.
Basic Mininet Command Line

• Topo – it allows to define a topology via the command

line.

• Switch – defines the switchwe’ll use in that topology.

• By default,the Open vSwitch software is used, but you

can define other switches.

• Controller – defines the controller that you want to use,

by default, uses the controller with a default hub-like
behaviour.

• mn – launch script that executes Python

 TRYING OUT DIFFERENT TOPOLOGIES

1) sudo mn --topo minimal

• Star Topology
• One switch and two
hosts
2) Sudo mn --test pingall --topo single,3
• Star Topology
• One switch and three hosts
3) sudo mn –topo linear,4
4) sudo mn –topo tree,depth=2,fanout=2
 OpenDaylight

• Open source platform for Software Defined

Networking (SDN).

• To provide the centralized, programmatic control

as well as network device monitoring open
protocols are used.

• Robust, extensible open source code base.

• Common industry supported platform

 Advantages of Opendaylight

• Industry Acceptance

• Integration with Openstack

• Cloud Applications

Disadvantages – Complex
 OUTPUT OF THE TREE
TOPOLOGY

For linear topology

:>>sudo mn --controller=remote,ip=ODL_VM_IP(Eg.192.168.253.155) --topo=linear,10
EXTENSION OF THE PROJECT

1) Learn more about working of

OpenDaylight.
2) How to create our own complex
topologies on Mininet.
3) Try to send to different types of data using
SDN on one device.
4) Try to connect more devices and share the
data between them
 REFERENCES

[1] Raj Jain and Subharthi Paul, Washington University,

“Network Virtualization and Software Defined Networking for
Cloud Computing: A Survey”, in IEEE Communications
Magazine, November 2013.

[2] Intel® Network Academy – a comprehensive training

program on network transformation -
https://www.coursera.org/learn/network-transformation-101.
 REFERENCES

[3] Hyojoon Kim and Nick Feamster, Georgia Institute of Technology,

“Improving Network Management with Software Defined Networking”,
IEEE
Communications Magazine, February 2013.

[4] N. M. Mosharaf Kabir Chowdhury and R. Boutaba, &quot, “Network

virtualization:
state of the art and research challenges”, in IEEE Communications
Magazine,
vol. 47, no. 7, pp. 20-26, July 2009.
 REFERENCES

[5] S. Chaudhari, R. S. Mani and P. Raundale, "SDN network

virtualization survey," 2016 International Conference on
Wireless Communications, Signal Processing and Networking
(WiSPNET), Chennai, 2016, pp. 650-655.

[6] SDN and Openflow for beginners with hands on labs book
by Vivek Tiwari
 REFERENCES

[7] Khattak, Z. K., Awais, M., & Iqbal, A. (2014), “ Performance

evaluation of OpenDaylight SDN controller” 2014 20th IEEE
International Conference on Parallel and Distributed Systems
(ICPADS).

[8] L. Xingtao, G. Yantao, W. Wei, Z. Sanyou and L. Jiliang,

"Network virtualization by using software-defined networking
controller based Docker," 2016 IEEE Information Technology,
Networking, Electronic and Automation Control Conference,
Chongqing, 2016.
 REFERENCES

[9] Badotra, Sumit. (2017). A Review Paper on Software Defined

Networking. International Journal of Advanced Computer
Research.8.

[10] Hakiri, Akram & Gokhale, Aniruddha & Berthou, Pascal &
Schmidt, Douglas & Gayraud, Thierry. (2014). Software-Defined
Networking: Challenges and research opportunities for Future
Internet. Computer Networks. 75.
10.1016/j.comnet.2014.10.015.