Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
6 views3 pages

Chapter 8 - Data Plane Basic and OpenFlow

Chapter 8 discusses OpenFlow, a multivendor standard by the Open Networking Foundation for implementing Software Defined Networking (SDN). It defines the interface between OpenFlow Controllers and switches, allowing packet handling instructions through structured flows. The OpenFlow architecture consists of switches, controllers, and applications, and can operate in overlay networks with traditional equipment.

Uploaded by

IZWAN NURLI MAT BISTAMAN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views3 pages

Chapter 8 - Data Plane Basic and OpenFlow

Chapter 8 discusses OpenFlow, a multivendor standard by the Open Networking Foundation for implementing Software Defined Networking (SDN). It defines the interface between OpenFlow Controllers and switches, allowing packet handling instructions through structured flows. The OpenFlow architecture consists of switches, controllers, and applications, and can operate in overlay networks with traditional equipment.

Uploaded by

IZWAN NURLI MAT BISTAMAN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Chapter 8 : Data Plane Basic and OpenFlow

8.1 OpenFlow

8.1 OpenFlow Spec

It is a multivendor standard defined by the Open Networking Foundation


(ONF) for implementing SDN in networking equipment. The OpenFlow
protocol defines the interface between an OpenFlow Controller and an
OpenFlow switch, see Figure 1 below. The OpenFlow protocol allows the
OpenFlow Controller to instruct the OpenFlow switch on how to handle
incoming data packets.

The OpenFlow switch may be programmed to:

(1) identify and categorize packets from an ingress port based on a


various packet header fields;
(2) Process the packets in various ways, including modifying the header;
and,
(3) Drop or push the packets to a particular egress port or to the
OpenFlow Controller.

The OpenFlow instructions transmitted from an OpenFlow Controller to an


OpenFlow switch are structured as “flows”. Each individual flow contains
packet match fields, flow priority, various counters, packet processing

1
instructions, flow timeouts and a cookie. The flows are organized in tables.
An incoming packet may be processed by flows in multiple “pipelined”
tables before exiting on an egress port. The OpenFlow protocol standard is
evolving quickly with release 1.3.2 as the current revision at the time of
this blog being published.

The OpenFlow Network Architecture consists of three layers:

(1) One or more OpenFlow virtual and/or physical switches;


(2) One or two OpenFlow controller(s); and,
(3) One or more OpenFlow application(s).

The OpenFlow controller maintains the OpenFlow protocol


communications channels to the OpenFlow switches, maintains a local
state graph of the OpenFlow switches and exposes a northbound API to
the OpenFlow applications. The northbound API may be viwed as an
abstraction of the network and allows the OpenFlow applications to read
the state of the network and to instruct the network to perform various
tasks.

A real world OpenFlow capable network may consist of only OpenFlow


switches or a mixture of OpenFlow switches and traditional switches and
routers. The latter network type is called an overlay network. Some
OpenFlow applications will require only partial deployment of OpenFlow

2
switches whereas others require a network consisting of only OpenFlow
switches.

As SDN is essentially a nascent market, the majority of implementations


will be as overlays on existing networks. Most of the applications we will
discuss in this blog can be introduced as overlays, and multiple
applications can be introduced in a staged fashion, with new ones building
on the foundations laid by the previous applications.

You might also like