10/29/2019 3.

SDN Protocols - Software-Defined Networking (SDN) with OpenStack

 So ware-Defined Networking (SDN) with OpenStack

PREV NEXT
⏮ ⏭
Summary Configuration management protocols
  🔎

Chapter 3. SDN Protocols
In the previous chapter, we outlined the challenges of traditional networks
and showed how a SDN architecture with its distributed control plane and
centralized management offers a superior solution. In this chapter, we will
delve into the underlying components and protocols that enable the SDN-
based architecture. We will introduce Open vSwitch (OVS), a popular
virtual switch in SDN environments and leverage it to gain insights into
SDN building blocks.

We will cover the following topics in this chapter:

How protocols with definition of standard API are the key driver for
the SDN architecture and solutions.

Introduction to Open vSwitch

Data modeling language: YANG (RFC 6020), data model: YANG

data models, Encoding formats: XML, JSON, and YAML

Protocols: OpenFlow, NETCONF, RESTCONF, OF-CONFIG,

OVSDB, and their role in SDN eco-system

Learning the protocols using sample configurations of software that

implement and tools supporting configuration, monitoring of the
packet flow

Getting familiar with SDN protocols

In pre-SDN architectures, although there is a separation between the
control plane and the data plane, the communication between the layers
is usually proprietary and it is defined by the merchant silicon vendor or
network equipment vendors. Moreover, the network management
configuration syntax is not interoperable between networking gear from
different vendors, for instance, CLI for Cisco IOS is not compatible with
Juniper's JUNOS CLI.

The definition of standard protocols with open APIs between control plane
and data plane in addition to a standardized configuration model is the
catalyst that is enabling the SDN. This standard API-based separation of
the control plane from the forwarding plane enables consistent
management and control across network. It also facilitates interoperability
between forwarding planes and control planes between networking
equipment from different vendors. The ability to communicate with
forwarding elements across the network through centralized control plane
protocols facilitates use cases such as network-wide custom traffic
engineering, besides providing a network-wide operational view for ease
of manageability.

In this chapter, we will use OVS with a rich set of utilities as a platform to
understand the SDN paradigm with hands-on configuration samples in a
Linux environment. It is important to note that OVS is the most widely
used virtual switch in OpenStack environments.

Open vSwitch
Let's start with an introduction to OVS, a production quality, multilayer
virtual switch popularly deployed in virtualized environments. Open
vSwitch is licensed under the open source Apache 2.0 license, and is
included as default feature from Linux 3.3 Kernel onwards.

In addition to bringing in L2 learning, L3 forwarding, and ACL features

that are typically found in switching processors, OVS supports features
tailored for virtualized deployments. OVS supports fine-grained Quality of
Service (QoS), control across traffic aggregate connections, and per VM
interface traffic policing. OVS also supports visibility into inter-VM
⬆
communication via NetFlow, sFlow(R), IPFIX, SPAN, RSPAN, and GRE-
tunneled mirrors. It supports tunneling protocols popular in virtualized
environments such as GRE, VXLAN, STT, and Geneve, with IPsec.

Find answers on the fly, or master something new. Subscribe today. See pricing options.

https://learning.oreilly.com/library/view/software-defined-networking-sdn/9781786465993/ch03.html 1/3
10/29/2019 3. SDN Protocols - Software-Defined Networking (SDN) with OpenStack

OVS supports mobility of state by live network state reconstruction of

virtual machines as they migrate between different hosts. It supports
remote triggers for the changes in the network dynamics. Open vSwitch
supports methods to append and manipulate tags in the network packets
that uniquely identify a VM in a network context

OVS supports OpenFlow protocols including many virtualization

extensions. The following diagram describes the OVS components and
interaction between them:

Figure 1: Open vSwitch components.

Open vSwitch's modular architecture with switching daemons (ovs-

vswitchd) and sets of software utilities allows its deployment as the
control stack for switching silicon. With Linux kernel module
(openvswitch_mod.ko) for flow-based switching, OVS functions as soft
switch running within the hypervisor.

ovs-vswitchd communicates with OpenFlow controller using OpenFlow.

It communicates with Ovsdb-server using OVSDB protocol. It
communicates with the kernel module over netlink, and with the system
through the netdev abstract interface.

ovs-vswitchd (slow path) implements core switching features, including

learning VLAN and bonding via programming the flow table, which is also
exposed via OpenFlow. It supports visibility via NetFlow, sFlow(R), IPFIX,
SPAN, RSPAN, and GRE-tunneled mirrors. The packet classifier supports
lookup based on L2-L4 wildcarding, priorities and actions to forward,
drop, and modify packets. It monitors the data-path flow counters to
handle flow expiration.

ovs-vswitchd supports centralized control, having one OpenFlow

connection per OpenFlow Logical Switch. It exports an idealized view of
OpenFlow Logical Switch. Queue missed flows go to the central
controller.

The following diagram will be used to describe the packet flow in the
OVS:

Figure 2: Open vSwitch packet flow.

The Kernel module (fast path) openvswitch_mod.ko handles packet

lookup, switching, and tunneling efficiently. It caches flows; however, it
does not have OpenFlow awareness. It extracts the packet header and
generates the hash to use it as an index to find a match in the flow table.
If a flow match is found, it performs actions to modify, forward, and tunnel
encapsulate/de-capsulate as programed by the controller and increments
packet counters. If there is no flow entry, the packet is sent to ovs-
vswitchd and eventually to the controller if configured. ovs-vswitchd, in
consultation with the controller takes decision on how to process the
packet and programs the data path's actions for the flow. Once the flow is
programmed with the actions, the subsequent packets are handled in the
kernel fast path based on the flow match and actions.

OVS provides a rich set of command-line utilities supporting

configuration, monitoring, and debugging:

ovs-vsctl: This command-line utility configures ovs-vswitchd

interfacing with its configuration database; it connects to an
ovsdb-server process that maintains an Open vSwitch ⬆
configuration database. It provides interface to push the commands
and waits for ovs-vswitchd to finish reconfiguring. It supports
commands to create Open vSwitch bridges, configure ports,
interfaces, and setting up the OpenFlow controller.

Find answers on the fly, or master something new. Subscribe today. See pricing options.

https://learning.oreilly.com/library/view/software-defined-networking-sdn/9781786465993/ch03.html 2/3
10/29/2019 3. SDN Protocols - Software-Defined Networking (SDN) with OpenStack

ovs-ofctl: This command-line tool is for monitoring and

administering OpenFlow switches. It can also show the current
state of an OpenFlow switch, including features, configuration, and
OpenFlow table entries.

ovs-appctl: This program provides a way to invoke the

commands supported by Open vSwitch daemons, ovs-vswitchd.
ovs-appctl sends the command and prints the daemon's
response on a standard output.

ovs-dpctl: This program can create, modify, and delete Open

vSwitch datapaths that are implemented outside of ovs-
vswitchd, such as the Linux kernel-based datapaths.

Settings / Support / Sign Out

© 2019 O'Reilly Media, Inc. Terms of Service / Privacy Policy
PREV NEXT
⏮ ⏭
Summary Configuration management protocols

Find answers on the fly, or master something new. Subscribe today. See pricing options.

https://learning.oreilly.com/library/view/software-defined-networking-sdn/9781786465993/ch03.html 3/3