ch 04 --- sdn deployment models

10
NDI Communications - Engineering & Training Software Defined Networking (SDN) Chapter 4 – SDN Deployment Models

Upload: yoram-orzach

Post on 15-Apr-2017

118 views

Category:

Internet


0 download

TRANSCRIPT

Page 1: Ch 04 --- sdn deployment models

NDI Communications - Engineering & Training

Software Defined Networking (SDN)

Chapter 4 – SDN Deployment Models

Page 2: Ch 04 --- sdn deployment models

Page 2

Chapter Content

Introduction

Centralized vs Distributed Control

Flow Routing vs. Aggregation

2

Page 3: Ch 04 --- sdn deployment models

Page 3

Introduction and Terms

Symmetric vs Asymmetric:

In an asymmetric model, SDN global information is centralized as much as possible, and edge driving is

distributed as much as possible.

In a symmetrically distributed SDN model, an effort is applied to increase global information

distribution ability, and SDN aggregation performance ability so that the SDN elements are basically

one type of component.

Floodless vs Flood-based:

In a flood-based model, significant amount of the global information sharing is achieved using well

known broadcast and multicast mechanisms.

In a FloodLess model, all forwarding is based on global exact match typically achieved using

Distributed Hashing and Distributed Caching of SDN lookup tables.

Host-based Vs Network Centric:

In a host-based model, under an assumption regarding use of SDN in data-centers with lots of virtual

machines moving to enable elasticity, the SDN encapsulation processing is already done at the

host HyperVisor on behalf of the local virtual machines.

In a Network Centric design, a clearer demarcation is made between network edge and end points.

Such an SDN edge is associated with the access of Top of Rack device and outside the host endpoints.

Page 4: Ch 04 --- sdn deployment models

Page 4

Reactive vs. Proactive (pre-populated)

Reactive

First packet of flow

triggers controller to

insert flow entries

Efficient use of flow

table

Every flow incurs small

additional flow setup time

If control connection lost,

switch has limited utility

Proactive

Controller pre-populates

flow table in switch

Zero additional flow setup

time

Loss of control connection

does not disrupt traffic

Essentially requires

aggregated (wildcard)

rules

Page 5: Ch 04 --- sdn deployment models

Page 5

Reactive vs. Proactive (pre-populated)

Reactive

First packet of flow

triggers controller to

insert flow entries

Efficient use of flow

table

Every flow incurs small

additional flow setup time

If control connection lost,

switch has limited utility

Proactive

Controller pre-populates

flow table in switch

Zero additional flow setup

time

Loss of control connection

does not disrupt traffic

Essentially requires

aggregated (wildcard)

rules

Page 6: Ch 04 --- sdn deployment models

Page 6

Chapter Content

Introduction

Centralized vs Distributed Control

Flow Routing vs. Aggregation

Page 7: Ch 04 --- sdn deployment models

Page 7

SDN Domains

OpenFlow Switch

Domain Controller

OpenFlow Switch

OpenFlow Switch

OpenFlow Switch

OpenFlow Switch

OpenFlow Switch

OpenFlow Protocol

Domain Controller

SDNi

Page 8: Ch 04 --- sdn deployment models

Page 8

Chapter Content

Introduction

Centralized vs Distributed Control

Flow Routing vs. Aggregation

Page 9: Ch 04 --- sdn deployment models

Page 9

Flow Routing vs. Aggregation

Flow-Based

Every flow is individually

set up by controller

Exact-match flow

entries

Flow table contains one

entry per flow

Good for fine grain

control, e.g. campus

networks

Aggregated

One flow entry covers

large groups of flows

Wildcard flow entries

Flow table contains one

entry per category of

flows

Good for large number of

flows, e.g. backbone

9

Page 10: Ch 04 --- sdn deployment models

Page 10

Summary

Yoram Orzach

[email protected]

Thank You!!!

Coming soon LIVE on our NEW e-Learning portal