CHAPTER 1

INTRODUCTION

The tremendous amount of increasing internet users can create an new

access of internet that was a Internet of Services (IoS). An amount of traffic in
the Internet has been grown dramatically. So, a better network management is
required. Software Defined Networking (SDN) has been proposed for efficient
and flexible resource management. software-defined networking (SDN)
Controller. The reason is that we see the two technologies as complementary
and these markets will likely converge over time.

We also see a potential for these solutions to end up merging with

orchestration systems such as cloud management platforms or OSS or network
service orchestration platforms. Regardless, most of today’s NV platforms
contain SDN controllers. Or put another way, NV is the most common use case
for SDN controllers.

Generally speaking, NV solutions have mostly been deployed within

data centers for cloud platforms (used in both enterprises and service
providers), though we have seen NV start their spread into the campus and the
WAN with SD-WAN based on overlay technologies.

1
 At the same time, SDN controllers (independent of the NV use case)
have primarily been used for WAN deployments, to control and built out
dynamic WAN topologies, or in other service provider solutions involving
service function chaining.

We will split out the technologies where we can, and the vendor
product section at the end of this report containers separate categories for SDN
controllers and NV solutions. Many networking vendors are investing heavily
in both NV and SDN technology, and end users, both on the enterprise and
service provider side, tell us they need both. Much of the analysis of this report
is based on our user survey which guided our research.

The emphasis in this report will be on NV in the data center – though

we will discuss how this will evolve into the WAN. Our forthcoming 2016
Virtual Edge report (to be released in October) will focus on WAN applications,
especially in the service provider world.

When relevant, the vendor and end-user results have been separated;
when probing on current deployments and plans within an organization’s own
environment we considered technology vendors as NV customers and included
their responses in the results.

2
Among the things we will look at include:

• What is driving the adoption of SDN and NV

• Primary benefits of NV technology

• Benefits of SDN controllers

• Top protocols and features of both SDN and NV

• Top functions that will be delivered by NFV and SDN

• Different approaches vendors are taking to the market

• Key attributes to consider when evaluating NV solutions

• Key attributes to consider when evaluating SDN solutions

• Market trends – announcements and moves by NV leaders

• Vendor profiles

3
1.1Project Description

SDN controllers are integral to NV and often included in the

leading NV platforms. As the central control point for the virtualized network,
an SDN controller can simplify and automate the orchestration of the network,
enabling organizations to improve the intelligence, agility, scalability and cost-
effectiveness of their overall infrastructure.

It does this by using the programmable control APIs that are

exposed in an SDN environment, these APIs enable the controller to
communicate to the switches/routers ‘below’ (via southbound APIs) and
applications/services ‘above’ (via northbound APIs). As SDN fever took hold in
the 2010-2012 timeframe.

The SDN controller market started to expand. This included the

ODL project from the Linux Foundation, which was first announced in 2013
and got its first release, named Hydrogen, in 2014.

At the same time, many network vendors scrambled to put

together an SDN strategy – which included picking a controller. Many vendors
opted to develop their own commercial controller solutions, either basing it on
an open source offering such as ODL or by building something different.

4
 The degree to which networking vendors use open source code
such as ODL and market an SDN business model can vary greatly. To date,
ODL appears to have the most momentum of the controller ecosystem.

ODL has more than 100 deployments, including Orange, China

Mobile, AT&T, T-Mobile, Comcast, KT Corporation, Telefonica, TeliaSonera,
China Telecom, Deutsche Telekom, and Globe Telecom. Contributing
individuals recently exceeded 500, vendors contributing including Big Switch
Networks, Cisco, Ericsson, HPE, NEC, and many others, making it one of the
fastest growing open source projects ever.

The fourth release, Beryllium, came out earlier this year. The
controller supports a wide variety of protocols including OpenFlow, Netconfig,
BGP, PCEP, and OVSDM. Many vendors have been developing their own
commercial controller solutions, basing their offerings on the ODL
advancements. The degree to which they leverage ODL, however, and the
business models they deploy vary greatly.

There are also commercial controllers that are proprietary. They

tend to be application-specific, such as VMware’s NSX, Cisco’s Application
Centric Infrastructure (ACI).

5
 They can also be designed to run vendor proprietary or 3rd
party apps, such as Big Switch’s Big Cloud Fabric, HPE’s VAN controller and
NEC’s Programmable Flow Controller. Another big movement in the controller
market is the Open Networking Operating System (ONOS), which was open
sourced in December 2014 and focused on serving the needs of service
providers.

While not as widely adopted at ODL, ONOS has been gaining

momentum around WAN use cases for service providers seeking an SDN
controller designed for service provider scale and performance. It is backed by
Cisco, Ericsson, Fujitsu, Huawei, Intel, NTT, NEC, SK Telecom, and many
others. Many of these companies also support ODL.

Project Modules

1. Controller Module.

1.1 Controller Plane.

2. User Module.

2.1 Application Plane.

2.2 Data Plane.

6
Controller Module

This module contains the controllers of SDN and NV for

managing the network systems in the LAN, MAN, WAN. Where it has plane to
manage the controller that named Controller Plane.

A controller plane does the management of different types of

network systems over the network, when ever the process of handling systems
by the linux based system at 2014, but 2016 the SDN and NV can develop any
type of network operating system can connect the controller.

User Module

A User module contains the user to connect to the SDN & NV

which has the two different types of planes. Those planes are comes under NBI
(North Bound Interface) & SBI (South Bound Interface) this interfaces are lies
in network and both parent and child controllers.

The planes are used in user module are,

1. Application Plane.

2. Data Plane.

7
Application Plane

Where application plane can applied on both controller and

user modules because of manage the different types of network module with
large number of increasing network users.

If the application plane goes to down the next plane of SDN

will raised for backup that is Data plane.

1.2 About SDN

Software defined networking (SDN) is an approach to computer

networking that allows network administrators to programmatically initialize,
control, change, and manage network behavior dynamically via open
interfaces and abstraction of lower-level functionality. SDN is meant to address
the fact that the static architecture of traditional networks doesn't support the
dynamic, scalable computing and storage needs of more modern computing
environments such as data centers.

Software-defined networking (SDN) is an architecture

purporting to be dynamic, manageable, cost-effective, and adaptable, seeking to
be suitable for the high-bandwidth, dynamic nature of today's applications.

8
 SDN architectures decouple network control and forwarding
functions, enabling network control to become directly programmable and the
underlying infrastructure to be abstracted from applications and network
services.

The SDN Controller is a logically centralized entity in charge of

translating the requirements from the SDN Application layer down to the SDN
Data paths and providing the SDN Applications with an abstract view of the
network. An SDN Controller consists of one or more NBI Agents, the SDN
Control Logic, and the Control to Data-Plane Interface (CDPI) driver.
Definition as a logically centralized entity neither prescribes nor precludes
implementation details such as the federation of multiple controllers.

9
 CHAPTER 2

SYSTEM STUDY

2.1 Feasibility Study

The feasibility of the project is analyzed in this phase and

business proposal is put forth with a very general plan for the project and some
cost estimates. During system analysis the feasibility study of the proposed
system is to be carried out. This is to ensure that the proposed system is not a
burden to the company. For feasibility analysis, some understanding of the
major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY

 TECHNICAL FEASIBILITY

 SOCIAL FEASIBILITY

10
Economical Feasibility

This study is carried out to check the economic impact that the
system will have on the organization. The amount of fund that the company can
pour into the research and development of the system is limited. The
expenditures must be justified. Thus, the developed system as well within the
budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

Technical Feasibility

This study is carried out to check the technical feasibility, that

is, the technical requirements of the system. Any system developed must not
have a high demand on the available technical resources. This will lead to high
demands on the available technical resources. This will lead to high demands
being placed on the client.

Social Feasibility

The aspect of study is to check the level of acceptance of the

system by the user. This includes the process of training the user to use the
system efficiently. The user must not feel threatened by the system, instead
must accept it as a necessity.

11
2.2 Existing System

Fig 2.2: Existing System

An above figure existing system show the more number of

controllers are used to manage the network systems, this can make the slow
performance, we are going to develop a single controller that mange the
different types of network systems

Disadvantages

 Human manager required.

 Want more number of hardware controllers.

 Less number of network management

12
2.3 Proposed System

Fig 2.3: Proposed System

A proposed system has only a single SDN controller, which

manage the all network system in a network. It also makes different SDN
switches also manage by SDN controller which make different network system
users can manage the resource in different places.

It create automatic controller management to makes fast and

efficient data management over the network so it create child controller for
more users in network.

13
Advantages

 Open Source.

 No hardware maintenance.

 Very low data lose.

 Efficient Data Access.

 More Reliable network.

 Openflow network connections.

14
 CHAPTER 3

SYSTEM SPECIFICATION

3.1 Software Specification

Operating System - Windows & Linux Based.

Language - Java, Java script.

Front End - Net Beans 7.4.1, JDK 1.5

Drivers - Auto Real tech LAN 6.5

3.2 Hardware Specification

Processor - Dual Core 2.8 GHz

Hard Disk - 120 GB

Ram - 3 GB

Monitor - 15VGA Color

Network card - 150 MBPS

15
 CHAPTER 4

LANGUAGE SPECIFICATION

4.1 Features of JAVA

There is given many features of java. They are also known as

java buzzwords. The Java Features given below are simple and easy to
understand.

1. Simple

2. Object-Oriented

3. Portable

4. Platform independent

5. Secured

6. Robust

7. Architecture neutral

8. Dynamic

9. Interpreted

10.High Performance

11.Multithreaded

12.Distributed

16
Simple

According to Sun, Java language is simple because syntax is

based on C++ (so easier for programmers to learn it after C++). removed
many confusing and/or rarely-used features e.g., explicit pointers, operator
overloading etc. No need to remove unreferenced objects because there is
Automatic Garbage Collection in java

Object-oriented

Object-oriented means we organize our software as a

combination of different types of objects that incorporates both data and
behaviour. Object-oriented programming(OOPs) is a methodology that simplify
software development and maintenance by providing some rules.

Basic concepts of OOPs are:

1. Object

2. Class

3. Inheritance

4. Polymorphism

5. Abstraction

6. Encapsulation
Platform Independent

17
 A platform is the hardware or software environment in which a
program runs. There are two types of platforms software-based and hardware-
based. Java provides software-based platform.The Java platform differs from
most other platforms in the sense that it is a software-based platform that runs
on the top of other hardware-based platforms.

It has two components:

1. Runtime Environment

2. API(Application Programming Interface)

Java code can be run on multiple platforms e.g. Windows,

Linux, Sun Solaris, Mac/OS etc. Java code is compiled by the compiler and
converted into bytecode. This bytecode is a platform-independent code because
it can be run on multiple platforms i.e. Write Once and Run Anywhere(WORA).

Secured

18
 Java is secured because:

o No explicit pointer

o Java Programs run inside virtual machine sandbox

o Class loader: adds security by separating the package for

the classes of the local file system from those that are
imported from network sources.

o Bytecode Verifier: checks the code fragments for illegal

code that can violate access right to objects.

o Security Manager: determines what resources a class can

access such as reading and writing to the local disk.

These securities are provided by java language. Some security

can also be provided by application developer through SSL, JAAS,
Cryptography etc.

Robust

Robust simply means strong. Java uses strong memory

management. There are lack of pointers that avoids security problem. There is
automatic garbage collection in java. There is exception handling and type
checking mechanism in java. All these points makes java robust.

Architecture-neutral

19
 There is no implementation dependent features e.g. size of
primitive types is fixed.

In C programming, int data type occupies 2 bytes of memory

for 32-bit architecture and 4 bytes of memory for 64-bit architecture. But in
java, it occupies 4 bytes of memory for both 32 and 64 bit architectures.

Portable

We may carry the java bytecode to any platform.

High-performance

Java is faster than traditional interpretation since byte code is

"close" to native code still somewhat slower than a compiled language (e.g., C+
+)

Distributed

We can create distributed applications in java. RMI and EJB are

20
used for creating distributed applications. We may access files by calling the
methods from any machine on the internet.

Multi-threaded

A thread is like a separate program, executing concurrently. We

can write Java programs that deal with many tasks at once by defining multiple
threads. The main advantage of multi-threading is that it doesn't occupy
memory for each thread. It shares a common memory area. Threads are
important for multi-media, Web applications etc.

4.2 Benefits of SDN

The benefits of SDN Controllers are very similar to those of

NV—though in this report, we will attempt to touch on other use cases for SDN
Controllers beyond just NV. Although we did not gather specific survey data on
SDN controllers, they offer the benefits that have been cited by our community
in many surveys on SDN technology namely, flexibility, management benefits,
and potentially lower costs of networking infrastructure.

Management Flexibility

21
 The fundamental benefit of SDN is that control of the network
can be managed via software, usually in a centralized manner. This allows
network topologies, applications, security, and routing to be changed on the fly,
without having administrators log into multiple pieces of network equipment
and changing configurations to each one. As we have shown, flexibility has
regularly come up as the #1 benefit of SDN technology in a number of surveys
and user panels we have conducted.

Operational Cost Savings

Tied closely to flexibility, operational costs can be saved by

reducing management overhead and time to launch a service or set up a network
including automation. One of the trends tightly tied to SDN is the move to
COTS hardware, or at least more interoperable equipment and standards,
meaning that more network management functions can be executed via a
software on the virtual level, reducing the time and cost of managing physical
hardware changes and configurations.

Capital Cost Savings

22
 The expansion of the COTS hardware market for SDN, as well
as the demand for increased interoperability of networking gear, is reducing the
number of proprietary networking products and pushing the networking
industry toward greater standardization. Over time, this allows merchant silicon
vendors to create high quality, lower cost products which contribute to lower
hardware costs overall.

Programmability

SDN controllers provide the capability to redirect traffic, apply

dynamic traffic filters, and deliver Quality of Service (QoS) in most of today’s
implementations. In addition, they can leverage automation techniques such as
templates to create applications and network configurations. Using northbound
APIs, the controller can dynamically adapt the network in response to
applications and optimize traffic flows.

Monitoring and Visualization

SDN controllers can enable end-to-end visibility of the network

and centralized management to improve overall performance. This can help
identify problems and speed troubleshooting.

Many SDN controllers will discover and present a logical

abstraction of all the physical links in the network, with the ability to observe
how the multiple virtual networks that are running on top of the physical

23
network are operating. By supporting standard monitoring protocols, the
information can be integrated with other management and orchestration
systems.

Security

SDN controllers can enable network managers to control

security of the network and applications from a central point. SDN controllers
are starting to incorporate security-related functionality that ensures the
controller is not the weakest link in the network and cannot be easily
compromised.

CHAPTER 5

SYSTEM DESIGN

24
 Design is multi-step process that focuses on data structure
software architecture, procedural details, (algorithms etc.) and interface
between modules. The design process also translates the requirements into the
presentation of software that can be accessed for quality before coding begins.

Computer software design changes continuously as new

methods; better analysis and broader understanding evolved. Software Design is
at relatively early stage in its revolution.

Therefore, Software Design methodology lacks the depth,

flexibility and quantitative nature that are normally associated with more
classical engineering disciplines. However techniques for software designs do
exist, criteria for design qualities are available and design notation can be
applied.

5.1 INPUT DESIGN

25
 Input design is the process of converting user-originated inputs
to a computer-based format. Input design is one of the most expensive phases of
the operation of computerized system and is often the major problem of a
system.

To build or modify the structure of a form, we work in forms

design view. We can add control to the form that are bound to fields in a table or
query, includes textboxes, option buttons, graphs and pictures.

Project

Planning

Requirement
Definition

Design

Development

Integration

& Test

Installation &
Acceptance
Fig 5.1: Input Design

5.2 OUTPUT DESIGN

26
 Output design generally refers to the results and information that are
generated by the system for many end-users; output is the main reason for
developing the system and the basis on which they evaluate the usefulness of
the application. In any system, the output design determines the input to be
given to the application.

Kickof

Process

Informal

Iteration

Formal

Iteration

In-Stage

Assessment

Stage

Exit

Fig 5.2: Output Design

5.3 ARCHITECTURE DIAGRAM

27
 Fig 5.3: Architecture Diagram

If an above architecture is show different types of switches are

connected to the single SDN controller which manages the large different types
increasing technologies over internet.

5.4 DATA FLOW DIAGRAM

28
 Start SDN
Controller

Connect Network Switches

Connect Hosts

Manage Hosts

Add Child Controller

Fig 5.4: Data Flow Diagram

5.5 UML Diagrams

29
5.5.1 Usecase Diagram

Controller

Fig 5.5.1.1: Controller Usecase Diagram

Host

30
 Fig 5.5.1.2: Host Usecase Diagram

5.5.2 Class Diagram

31
 SDN Controller

Manage_Hosts

Child_Controller()
();

Sending ()

Child Controller Hosts

Adding Switches Fig 5.5.2: Class Diagram

Add_Hosts();
Hosts();
Save File ()

Receiving ()
5.5.3 Sequence Diagram

Controller

Start Add Add Hosts Manage Network

Controller

Start Adding 32
Make Child Host & Switch New
Network
User Host
 Fig 5.5.3.1: Sequence Diagram for Controller

Hosts

Conversation
Manage Close
Controller Switch Hosts

Hosts

Communicate
Connected

Close
Add new host

Close
Resource

Fig 5.5.3.2: Sequence Diagram for Host

33
 CHAPTER 6

CODING

Sample Code from our Project

import java.net.*;
import java.io.*;
import java.lang.Runtime;
import java.lang.Process;
public class pController extends Thread
{
private ServerSocket serverSocket;
private long currentTime;
public IncomingCmd(int port) throws IOException
{
serverSocket = new ServerSocket(port);
serverSocket.setSoTimeout(0);
}
public IncomingCmd(long timeValue) throws IOException
{
currentTime = timeValue;
System.out.println("IncomingCmd:: Timer thread that checks switch
master-slave failover implemented");
}
public void run()
{
while (true)
{
if (!Thread.currentThread().getName().equals("Thread-4"))
{

34
 System.out.println("IncomingCmd::run(): Thread Started
" + Thread.currentThread().getName());

try {
System.out.println("IncomingCmd::run(): Listening on socket "
+ serverSocket.getLocalPort());
Socket server = serverSocket.accept();
DataInputStream in = new
DataInputStream(server.getInputStream());
String checkInput = in.readUTF();
System.out.println(checkInput);
if (checkInput.equals("Delete-gs1"))
{
try
{
Process p = Runtime.getRuntime().exec("sudo
ovs-vsctl del-port gs1 gs1-eth1");
}
catch (IOException e)
{
System.out.println("IncomingCmd::run(): Error
deleting G-Switch 1 port gs1-eth1");
}
}
else if (checkInput.equals("Delete-gs2"))
{
try
{
Process p = Runtime.getRuntime().exec("sudo
ovs-vsctl del-port gs2 gs2-eth1");
}
catch (IOException e)
{
System.out.println("IncomingCmd::run(): Error
deleting G-Switch 2 port gs2-eth1");
}
}

35
 else if (checkInput.equals("Pull-gs1"))
{

try
{
Process p = Runtime.getRuntime().exec("sudo ovs-vsctl
add-port gs1 gs1-eth1");
}
catch (IOException e)
{
System.out.println("IncomingCmd::run(): Error adding
G-Switch 1 port gs1-eth1");
}
}
else if (checkInput.equals("Pull-gs2"))
{
try
{
Process p = Runtime.getRuntime().exec("sudo ovs-vsctl
add-port gs2 gs2-eth1");
}
catch(IOException e)
{
System.out.println("IncomingCmd::run(): Error adding
G-Switch 2 port gs2-eth1");
}
}
else if (checkInput.startsWith("Switch-Controller"))
{
String switchNumber = checkInput.substring(18, 19);
switchController(switchNumber);
}
}
catch (SocketTimeoutException s)
{
System.out.println("IncomingCmd::run(): Socket Timed Out");
}

36
 catch (IOException e)
{
System.out.println("IncomingCmd::run() Error receiving data from
socket");
e.printStackTrace();
}
}
else if (Thread.currentThread().getName().equals("Thread-4")
&& (System.currentTimeMillis() - currentTime) > 10000)
{
currentTime = System.currentTimeMillis();
String[] switchList = {"s1", "s2", "s3", "s4"};
for ( String switchID : switchList) {
checkFailover(switchID);
}
}
}
}
if (serverSocket.getLocalPort() == 41102)
{
try
{
Process p = Runtime.getRuntime().exec("sudo ovs-vsctl del-controller
" + switchID);
p = Runtime.getRuntime().exec("sudo ovs-vsctl set-controller " +
switchID + " tcp:192.168.56.21:6633");
}
catch(IOException e)
{
System.out.println("IncomingCmd::switchController(): Error
performing controller commands for switch " + switchID); }
}
else if (serverSocket.getLocalPort() == 41202) {
try {
Process p = Runtime.getRuntime().exec("sudo ovs-vsctl del-controller
" + switchID);
p = Runtime.getRuntime().exec("sudo ovs-vsctl set-controller " +
switchID + " tcp:192.168.56.20:6633");
}
catch(IOException e)

37
 {
System.out.println("IncomingCmd::switchController(): Error
performing controller commands for switch " + switchID); }
}
}

public void checkFailover(String switchID) {

try {
Process p = Runtime.getRuntime().exec("sudo ovs-vsctl get-controller
" + switchID);
BufferedReader input = new BufferedReader(new
InputStreamReader(p.getInputStream()));
String controller = input.readLine();
System.out.println("IncomingCmd::checkFailover(): " + switchID + "
connected to controller " + controller);
if (controller != null)
{
if (controller.equals("tcp:192.168.56.20:6633"))
{
p = Runtime.getRuntime().exec("sudo ovs-vsctl -- get Controller " +
switchID + " is_connected");
BufferedReader newInput = new BufferedReader(new
InputStreamReader(p.getInputStream()));
String newInputString = newInput.readLine();
System.out.println("IncomingCmd::checkFailover(): Is " + switchID +
" connected to current controller? " + newInputString);
if (newInputString.equals("false"))
{
p = Runtime.getRuntime().exec("sudo ovs-vsctl del-controller "
+ switchID);
Thread.sleep(1000);
p = Runtime.getRuntime().exec("sudo ovs-vsctl set-controller "
+ switchID + " tcp:192.168.56.21:6633");
}
}
else if (controller.equals("tcp:192.168.56.21:6633"))
{
p = Runtime.getRuntime().exec("sudo ovs-vsctl -- get Controller " +
switchID + " is_connected");

38
 BufferedReader newInput = new BufferedReader(new
InputStreamReader(p.getInputStream()));
String newInputString = newInput.readLine();
System.out.println("IncomingCmd::checkFailover(): Is " + switchID +
" connected to current controller? " + newInputString);
if (newInputString.equals("false"))
{
p = Runtime.getRuntime().exec("sudo ovs-vsctl del-controller "
+ switchID);
Thread.sleep(1000);
p = Runtime.getRuntime().exec("sudo ovs-vsctl set-controller "
+ switchID + " tcp:192.168.56.20:6633");
}
}
}
}
catch(IOException e)
{
System.out.println("IncomingCmd::checkFailover(): Error executing
commands for switch " + switchID);
}
catch(InterruptedException ie)
{
System.out.println("IncomingCmd::checkFailover() Error with thread sleep
");
}
}
public static void main(String[] args)
{
System.out.println("IncomingCmd::main() Started");
int port1 = 41101;
int port2 = 41102;
int port3 = 41201;
int port4 = 41202;
long timer = System.currentTimeMillis();
try
{
Thread t1 = new IncomingCmd(port1);
Thread t2 = new IncomingCmd(port2);
Thread t3 = new IncomingCmd(port3);

39
 Thread t4 = new IncomingCmd(port4);
Thread t5 = new IncomingCmd(timer);
t1.start();
t2.start();
t3.start();
t4.start();
t5.start();

}
catch (IOException e)
{
System.out.println("IncomingCmd::main() Error starting thread");
e.printStackTrace();
}
}
}

40
 CHAPTER 7

SYSTEM TESTING

7.1 UNIT TESTING

The procedure level testing is made first. By giving improper

inputs, the errors occurred are noted and eliminated. Then the web form level
testing is made. For example storage of data to the table in the correct manner.

In the company as well as seeker registration form, the zero

length username and password are given and checked. Also the duplicate username
is given and checked. In the job and question entry, the button will send data to the
server only if the client side validations are made.

The dates are entered in wrong manner and checked. Wrong

email-id and web site URL (Universal Resource Locator) is given and checked.

41
7.2 INTEGRATION TESTING

Testing is done for each module. After testing all the modules,
the modules are integrated and testing of the final system is done with the test data,
specially designed to show that the system will operate successfully in all its
aspects conditions. Thus the system testing is a confirmation that all is correct and
an opportunity to show the user that the system works.

7.3 VALIDATION TESTING

The final step involves Validation testing, which determines

whether the software function as the user expected. The end-user rather than the
system developer conduct this test most software developers as a process called
“Alpha and Beta Testing” to uncover that only the end user seems able to find.

The compilation of the entire project is based on the full

satisfaction of the end users. In the project, validation testing is made in various
forms. In question entry form, the correct answer only will be accepted in the
answer box. The answers other than the four given choices will not be accepted.

42
 CHAPTER 8

SYSTEM MAINTENANCE

The objectives of this maintenance work are to make sure that

the system gets into work all time without any bug. Provision must be for
environmental changes which may affect the computer or software system. This is
called the maintenance of the system. Nowadays there is the rapid change in the
software world. Due to this rapid change, the system should be capable of adapting
these changes. In our project the process can be added without affecting other parts
of the system.

Maintenance plays a vital role. The system liable to accept any

modification after its implementation. This system has been designed to favor all
new changes. Doing this will not affect the system’s performance or its accuracy.

In the project system testing is made as follows:

The procedure level testing is made first. By giving improper

inputs, the errors occurred are noted and eliminated. Then the web form level
testing is made. For example storage of data to the table in the correct manner.

43
 In the form, the zero length username and password are given
and checked. Also the duplicate username is given and checked. The client side
validations are made. The dates are entered in wrong manner and checked. Wrong
email-id is given and checked.

This is the final step in system life cycle. Here we implement

the tested error-free system into real-life environment and make necessary changes,
which runs in an online fashion. Here system maintenance is done every months or
year based on company policies, and is checked for errors like runtime errors, long
run errors and other maintenances like table verification and reports.

44
 CHAPTER 9

SYSTEM IMPLEMENTATION

Implementation is the most crucial stage in achieving a

successful system and giving the user’s confidence that the new system is workable
and effective. Implementation of a modified application is to replace an existing
one. This type of conversation is relatively easy to handle, provide there are no
major changes in the system.

Each program is tested individually at the time of development

using the data and has verified that this program linked together in the way
specified in the programs specification, the computer system and its environment is
tested to the satisfaction of the user. The system that has been developed is
accepted and proved to be satisfactory for the user. And so the system is going to
be implemented very soon. A simple operating procedure is included so that the
user can understand the different functions clearly and quickly.

Initially as a first step the executable form of the application is

to be created and loaded in the common server machine which is accessible to the
entire user and the server is to be connected to a network. The final stage is to

45
document the entire system which provides components and the operating
procedures of the system.

9.1 SCOPE FOR FUTURE DEVELOPMENT

Every application has its own merits and demerits. The project
has covered almost all the requirements. Further requirements and improvements
can easily be done since the coding is mainly structured or modular in nature.

We are going to improve the user interface with simple GUI

and make more faster when compare to this version of SDN.

9.2 LITERATURE SURVEY

Hassan Habibi Gharakheili received the B.Sc. and M.Sc.

degrees in electrical engineering from the Sharif University of Technology, Tehran,
Iran, in 2001 and 2004, respectively, and the Ph.D. degree in electrical engineering
and telecommunications from the University of New South Wales, Sydney,
Australia, in 2015, where he is currently a Post-Doctoral Researcher with the
School of Electrical Engineering and Telecommunications. His research interests
include network architectures, software-defined networking, and broadband
networks

46
 Vijay Sivaraman (M’94) received the B.Tech. degree from IIT,
Delhi, India, in 1994, the M.S. degree from North Carolina State University in
1996, and the Ph.D. degree from the University of California at Los Angeles in
2000, all in computer science. He was with Bell-Labs and a Silicon Valley startup.
He is currently an Associate Professor with the University of New South Wales,
Sydney, Australia. His research interests include software-defined networking and
sensor networks for environmental and health applications

Arun Vishwanath (M’11–SM’15) received the Ph.D. degree in

electrical engineering from the University of New South Wales, Sydney, Australia,
in 2011. He is a Research Scientist with IBM Research-Australia. He was a
Visiting Ph.D. Scholar with the Department of Computer Science, North Carolina
State University, USA, in 2008. His research interests include software defined
networking and energy-efficient networking.

47
 CHAPTER 10

CONCLUSION

Recent SDN Controllers are used simultaneously, we are

implement SDN APIs for MULTI-SIDED RESOURCE MANAGEMENT IN ANY
NETWORK can manage the hosts by parallelly to reduced traffic and speed of
resource management. The network topologies can used to improve the Single
parent controller for different hosts if more hosts connect to the network mean
parent controller automatically create child controller for manage the network
traffic. This can reduce manageability of user and reduced collusion over network.

48
 CHAPTER 11

APPENDICES

11.1 SCREEN SHOTS

Start SDN Controller with 1 switch & 3 Hosts

Fig 11.1.1: SDN Controller Start

49
Controller GUI Create Edit

Fig 11.1.2: Network Designing

SDN to Graphically created for 1 Switch & 8 hosts

50
 Fig 11.1.3: Sample Network in SDN

CHAPTER 12

BIBILOGRAPHY

[1] H. Habibi Gharakheili et al., “Broadband fast-lanes with two-sided control:

Design, evaluation, and economics,” in Proc. IEEE/ACM IWQoS, Portland, OR,
USA, Jun. 2015, pp. 195–200.

[2] The Guardian. (Apr. 2014). The FCC Is About to Axe-Murder Net Neutrality.
Don’t Get Mad Get Even. [Online].

[3] G. Nagesh. (Apr. 2014). “FCC to propose new ‘net neutrality’ rules,” The Wall
Street Journal. [Online].

[4] “Netflix wants to put Comcast genie back in fast lane bottle.” (Nov. 2014).
Financial Times. [Online].

51
[5] S. Sundaresan et al., “Broadband Internet performance: A view from the
gateway,” in Proc. ACM SIGCOMM, Toronto, ON, Canada, Aug. 2011, pp. 134–
145.

[6] Internet Society. (Nov. 2012). “Measuring Internet congestion: A preliminary

report.” [Online].

Websites

http://www.theguardian.com/commentisfree/2014/apr/24/fcc-netneutrality-tom-
wheeler-stop-rules,
http://online.wsj.com/news/articles/SB10001424052702304518704579519963416
350296,

http://www.ft.com/cms/s/0/0bc54d54-639e-11e4-8216-00144feabdc0,

https://goo.gl/aUyWyX,

52