then section III, [V, V the definition of the Network routers. There are two types of label switch routers:
a. SDN architecture
OpenFlow was simply referred as "a way for The Distributed model contains centralized
researchers to run experimental protocols in the manager connected to Distributed controllers and
networks they use every day". The analogy used by data planes. The centralization of the manager
the authors in describing openflow is to think of interface makes system management appear as a
openflow as a general language or an instruction set whole of systems even when we are managing the
that lets one write a control program for the distributed network one by one. The distributed
network rather than having to rewrite all of code on model deployment is complex because of the access
each individual router. [3] and configuration difficulty, namely timing and
synchronization issues. Distributed model evolution
• NetFlow and scalability make it a recommended solution and
eliminates the Centralized model.
NetFlow is a networking protocol designed by
Cisco Systems for logging and recording the flow • Hybrid SDN
The white paper on NFV defines it as a NFV is highly complementary to SDN, but not
consolidation of Network functions onto industry dependent on it (or vice-versa). it can be
standard servers, switches and storage hardware implemented without a SDN being required,
located in DatalDistribution centers - an optimized although the two concepts and solutions can be
data plane under virtualization. NFV allows combined and potentially greater value accrued.
administrators to replace physical network devices NFV goals can be achieved using non-SON
(traditional) with software that is running on mechanisms, relying on the techniques currently in
commodity servers. This software realizes the use in many datacenters. But approaches relying on
'network functions' that were previously provided the separation of the control and data forwarding
by the dedicated hardware (network devices) [3] as planes as proposed by SDN can enhance
shown the below : performance, simplity compatibility with existing
deployments, and facilitate operation and
maintenance procedures.
NFV is able to support SON by providing the
infrastructure upon which the SON software can be
run. Furthermore, it aligns closely with the SDN
objectives to use commodity servers and switches.
We intend to work closely with organizations
progressing work on SDN such as the ONF whose
work we will specifically take into account. [7]
d. Logical Components
g. Distributed VSC
• Reactive: just program the switches
The Distribution of the SDN Controller makes accessible by the current controller.
network more scalable when adding a new • Proactive: using inter-controller
controller to the cluster and reliable when saving communication to program all switch end
the switches who's connected to a failed controller. to end. [5]
The challenge emerging with this model are The reactive approach can used if all controller are
synchronization, the coordination and cooperation available and are full synchronized, if one
between the VSC. controller fail, it data plane will be blocked, which
leverage on network availability.
h. The VSMIVSC functionality The proactive approach is recommended because
the controller work together to program the
The principle function of the VSMIVSC is helping switches. In this case, if a controller fail the others
the VRlVSC with interpreting information about will replace it transparently.
the infrastructure components. It collect a database
of real-time monitoring information and send it as VIII. Conclusion
an update to all VRlVSC to be considered when
making decision. The network domain is always broaden, and with
It's recommended to use a centralized VSMIVSC, SDN and NFV capabilities, it will quickly develop.
to increase the reliability of information sources, The idea is to involve the newer technology with
resolve the Split brain, coordination, and older Concepts to makes a network more secure and
cooperation and synchronization problems. To to improve its availability.
minimize update traffic among the network, an
update timing most be configured, the timing
depend of the network latency and used bandwidth. REFERENCE
To cancel the update redundancy, the VSMIVSC [1] Analysis of traffic engineering parameters while using Multi
will use revision number will be sent to distinguish protocol label switching (MPLS) and traditional IP
Networks written by Faiz Ahmed & Dr. Irfan Zafar
the older update.
Connecting the VSMIVSC directly to the Backbone
[2] Cisco systems, "CCIP MPLS Study Guide" James Reagn.
ameliorate the security level by using the
programmable firewall functionality on the SDN
[3] "SON and its use-cases-NV and NFV, a state-of-the-art
data plane.
survey, written by Sridhar K. N. Rao
In distributed controller case, when initiating the [5] "Controlling a Software-Defined Network via Distributed
network, the controller assign each switch a virtual Controllers" written by Volkan Yazici, Oguz Sunay, Ali
Qzer Ercan
IP addresses to use when communicate with its
controller. When the switch tries to communicate
[6] http://www.techopedia.com/definition/28315/netflow 22
with the controller, it get redirected to the March 2015
corresponding one.
In the edge of our proposed architecture, controller [7] Network Functions virtualisation - Intoductory White Paper
is attached to the router which reduce latency and
secure the communication. When the attached [8] http://www.opencontrai1.orgiopencontrail-architecture-
controller fail, the Router will redirected to other documentation/#section2 10 juin 2015
contro IIer.
The backbone architecture will be monitored by the
VSMIVSC, and it will be controlled by the
VRIVSC controller because the forwarding path
will depend of the packet treated there.
b. Inter-controller routing