management, network segments, and the state of network elements and applications,
implementing a high-level network management and data flow.
Each controller has at
least one application that manipulates switches connected to it, and can provide a global
view of physical network topology under the controller management. The
idea of
creating a unified, independent from the network equipment manufacturer [
4
–
6
],
program-controlled interface between the controller and the network transport infra‐
structure is defined in the OpenFlow standards and OpenFlow protocol [
7
], which allows
users to define and control with whom, under what conditions and with what quality can
interact on the network. OpenFlow is an open standard, which describes the remote
management requirements to a switch that supports OpenFlow protocol. According to
OpenFlow standard specifications, the interaction between the
controller and the switch
is carried out through OpenFlow protocol. Each switch must contain one or more flow
tables and group tables, which perform packet lookups and forwarding, and support
OpenFlow secured channel to a remote controller. Each flow table in the switch contains
a set of flow entries; each flow entry consists of match fields, counters, and a set of
instructions to apply to matching packets. Data management in OpenFlow is
carried out,
not on the individual packet level, but at the level of their packet streams. Rules are
dynamic. Packets which have no match are sent to the controller (packet in). Controller
creates appropriate rule and sends packet back to switch (packet out) for processing.
The rule in the switch is set only for the first packet, and then all the other packets of
the flow use it.
In this paper is introduced an analytical and simulation analysis of an
SDN model
where the network is modelled as queueing system to capture the time costs associated
with the controller and the switches activities.
Dostları ilə paylaş: