Software Defined Networking

Presentation Outline

• Abstract

• Introduction

• Implementing Network

• Why SDN?

• SDN and openflow

• Open Flow

• Procera and Architecture

• Conclusion

• References

Abstract• Network Management is really hard and

challenging goal

• Software Defined Networking (SDN), advocatesseparating the data plane and the control plane

• Problems focused ono Enabling frequent changes to network conditions and

state.

oProviding support for network configuration

oProviding better visibility and control over tasks

Introduction

• Networks typically comprise a numerous types of middle boxes

• Network configuration remains incredibly difficult

• Network operators are responsible for configuring the network toenforce various high-level policies, and to respond to the wide rangeof network events (e.g., traffic shifts, intrusions) that may occur.

Implementing Network

• Network policies low-level, are not well equipped to react tocontinually changing network conditions

• State-of-the-art network configuration methods can implement anetwork policy that deals with a single snapshot of the network state.

What is SDN?

• Software Defined Networking (SDN) is a paradigm where a centralsoftware program, called a controller, dictates the overall networkbehavior.

• SDN has two planes• Data plane

• Control plane

• This paradigm shift brings two benefits compared to legacy methods.

• Network wide traffic forwarding decisions in a logically single location,the controller, with global knowledge of the network state.

Contnd..

SDN and Openflow

• Openflow is one of the most common southbound SDN interfaces.

• Open Network foundation

• There are a variety of OpenFlow controllers, for example, NOX, Floodlight,and Maestro

• There are two interfaceso southboundo northbound

Component of Open Flow

Flow Table

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Default Action Statistics

• Flow table in switches, routers, and chipsets

Flow 1.

Flow 2.

Flow 3.

Flow N.

Flow Entry• A flow entry consists of

• Match fields • Match against packets

• Action• Modify the action set or pipeline

processing• Stats

• Update the matching packets Match Fields

StatsAction

In PortSrc

MACDst

MACEth

TypeVlan Id IP Tos

IP Proto

IP Src IP DstTCP Src

PortTCP Dst

Port

Layer 2 Layer 3 Layer 4

1. Forward packet to port(s)2. Encapsulate and forward to controller3. Drop packet 4. Send to normal processing pipeline

1. Packet2. Byte counters

Procera

• Procera is a network control framework that helps operators expressevent-driven network policies that react to various types of eventsusing a high-level functional programming language.

• Procera effectively serves as a glue

• Procera offers a set of control domains

Procera Architechture

Future Work

• Demonstrate the feasibility of Procera, but more evaluation onperformance and scalability is required

• It is not hard to extend Procera to support more control domains;definition and implementation of how a new event will arrive atProcera, and along with what kind of information would make itpossible to support more control domains

• Procera also supports allow and drop packets

Conclusion

• Network operators and management, have designed andimplemented an event driven network control framework on SDN

• We use the OpenFlow protocol to communicate between the Proceracontroller and the underlying network switches.

• Network operators use 4 domains

References

• Kim H., and Feamster N., Georgia Institute of Technology, “Improving Network Management with Software Defined Networking”, IEEE communication Magzine, feb 2013, pp 114-119

• <http://www.openflow.org/

Thank You