SOFTWARE DEFINED NETWORKING: INDUSTRY INVOLVEMENT

BROCADE

SOFTWARE DEFINED NETWORKING:

INDUSTRY INVOLVEMENT

Rajesh Dhople

Brocade Communications Systems, Inc.

[email protected]

Why can’t you do these things today?

•

Network changes are

y

y

g

y

Traditional Network

_g

difficult, slow, and risky

•

Can’t handle rapid swings in

traffic demands

•

New services requires adding

expensive specialized skills

expensive specialized skills

•

Unlimited funds needed to

solve issues

Hierarchical

N th/S th

Monolithic

Closed

Cloud-Optimized Networks via SDN are the Solution

p

Software Defined Networking

•

Network changes are quick

and easy

R id d l

t f

VM VM VM

Network

Controller

Cloud

Management

System

•

Rapid deployment of new

services

•

Flexible on demand networks

Network Fabric

VM VM VM

PHY PHY

VM VM VM

PHY PHY

VM VM VM

PHY PHY

Flexible, on demand networks

•

Highly automated

environments

Open

Automated

Personalized

Network Fabric

More Resilient

Flexible

SDN Target Use Cases

DC Network Virtualization

Network Analytics

g

DC Virtualization Network Analytics

VM VM VM

PHY PHY

VM VM VM

PHY PHY

VM VM VM

PHY PHY DC Virtualization

Overlay Gateway

Network Analytics

Production 100 GE and 10GE WAN

Analytics & Telemetry

WAN Network Virtualization

Services Creation & Insertion

Network Fabric

y y

Network Tool 1

Tool 2 Tool 3 Tool 4 Tool 5

Customer 1

WAN Virtualization Services Insertion

ADC FW Cache

100 GE and 10GE WAN Customer 2

DC 1 DC 2

Service Provider WAN Use Case

•

Hybrid switch mode

Using Hybrid Switch Mode

Features (Applications)

N

k C

ll

•

OpenFlow ports run OpenFlow

only

•

WAN traffic managed

Network Controller

OpenFlow Network

WAN traffic managed

exclusively using OpenFlow

OpenFlow Network

WAN Physical Infrastructure

WAN Physical Infrastructure

Service Provider WAN Use Case

•

Hybrid port mode

O

Fl

l

“Unprotected” Production IP Network with OpenFlow Overlay

Features (Applications)

N

k C

ll

•

OpenFlow overlay runs

concurrently with traditional

MPLS/IP routing

•

OpenFlow enabled on existing

d ti t

k

Network Controller

OpenFlow Overlay

_{production network}

•

Unprotected

•

OpenFlow allowed as an

S

OpenFlow Overlay

Traditional MPLS/IP Routing

“exception rule” to MPLS/IP

forwarding

•

Service Provider can add new

revenue-generating features on

WAN Physical Infrastructure

_{top of existing production}

network

Research and Education Network (REN) WAN Use Case

•

Hybrid port mode

“Protected” Production IP Network with OpenFlow Overlay

Features (Applications)

N

k C

ll

_•

_{OpenFlow overlay runs}

concurrently with traditional

MPLS/IP routing

•

OpenFlow enabled on existing

Network Controller

OpenFlow Overlay

Protection

Layer

•

OpenFlow enabled on existing

production network

•

Protected

OpenFlow Overlay

Traditional MPLS/IP Routing

•

OpenFlow experimentation by

researchers does not affect

production traffic

•

OpenFlow/Production traffic

WAN Physical Infrastructure

•

OpenFlow/Production traffic

isolation in hardware

Protected versus Unprotected Hybrid Port Mode

•

Protected Hybrid Port Mode

•

OpenFlow rules cannot affect the traffic of a set of protected VLANs

•

Protection is supported in hardware

•

Unprotected Hybrid Port Mode

•

Ingress frames are checked against OpenFlow rules first

•

If there is no match, traffic is processed by configured features on the port,

SDN Use Case: Network Virtualization

Network Virtualization

A SDN Application

ƒ

A SDN application that enables

the creation of logical networks

g

(multi-tenancy) over a common

physical network

ƒ

Logical networks contain VMs and

VM VM VM

PHY PHY

VM VM VM

PHY PHY

VM VM VM

PHY PHY

Logical networks contain VMs and

physical workloads (e.g., physical

servers, firewalls, etc)

ƒ

Enables seamless control of

SP Physical Infrastructure

Enables seamless control of

network resources regardless of

location

ƒ

Logical networks can be used to

SP Physical Infrastructure

Logical networks can be used to

Network Virtualization Using L2 over L3 Tunnels

g

An Industry Trend for Hyper-Scale Data Centers

ƒ

Network Virtualization

ƒ

Network Virtualization

created using L2 over L3

tunnels

VM VM VM

PHY PHY

VM VM VM

PHY PHY

VM VM VM

PHY PHY

ƒ

Programmatic interface

may use OpenFlow

L2 over L3 Tunnels

Tunnels

SP Physical Infrastructure

ƒ

Requires additional

management protocols

beyond OpenFlow to

L2 over L3 Tunnels

Public Cloud Use Case

At Customer B DC

and VMs

Hyper-scale DC

Customer A

Customer B

Customer A

(Logical Network)

SP DC

PHY VM VM

Customer B

• VLANs and MAC learning do no scale well in this case

• Must maximize number of VMs per server to lower

costs

N t k i t li ti i t l t dd

VM1 VM2 PHY 1

L3 VPN or Internet

SP DC

Customer DC

VM 3

VM

4 PHY VM VM

PHY PHY 2

CPE

• Network virtualization using tunnels to address

• VLAN/MAC learning limitations

• Flexible allocation of services (VMs and Physical workloads) anywhere in DC

• SDN provisioning at edge of DC network

SDN Controller

L2 over L3 tunnels

Data Center

ToR

Cloud Router

• SDN provisioning at edge of DC network

• Not hop-by-hop

• Requires hardware-based switches terminating

tunnels

• For physical workload attachment (ToR) PHY1

PHY2 Server

vSwitch

vSwitch

SDN: Edge of

DC Network

• For physical workload attachment (ToR)

• For access to L3VPN and the Internet (Cloud router) • For customer site termination of tunnels (CPE)

PHY1

VM4 VM2 Physical workloads

Web 2.0 Use Case

• Large internal “customers”

• Use of VLANs for customer isolation limits workload

SDN Controller

Internal Customer A

Internal Customer B

Data Center

Cloud Router

• Use of VLANs for customer isolation limits workload placement leading to under utilized resources (servers), leading to higher CapEx and OpEx

• Must maximize resource utilization (servers) to lower

costs

( g )

SP DC

1

SDN: Edge of

( g )

SP DC

2 VM3

• Network virtualization using tunnels to address

• Flexible allocation of services (VMs and Physical

workloads) anywhere in DC

_{L2 over L3 tunnels}

SDN: Edge of

DC Network

ToR

• SDN provisioning at edge of DC network

• Not hop-by-hop

• Requires hardware-based switches terminating tunnels

PHY1 PHY2 Server

vSwitch

vSwitch

• For access to L3VPN and the Internet (Cloud router)

PHY1

Web 2.0 Data Center

VM4 VM2

Physical workloads Virtual workloads

The Emergence of the Cloud Router

Cloud Gateway

g

Routing Automation of IP-VPN PE Data Center Router

C t

VM VM VM VM VM VM

•

Direct mapping from customers Logical Network

and Metro/WAN transport

• Eliminates use of transit hop using VLANs

•

Single SDN point of control between Metro/WAN

Customers

Internet, IP-VPN,

WAN/Metro

PHY PHY PHY PHY

•

Single SDN point of control between Metro/WAN

and DC

Cloud Scale

Cloud Router

Data Center

WAN/Metro

•

Optimized to large multi-tenancy requirements

•

End-to-end OAM and SLA from customer site to

DC cloud services

P

id d d DC ti

biliti

Tunnels

Tunnels

Tunnels

SDN Controller

Server Server

•

Provider edge and DC routing capabilities

•

Inter-DC connectivity

VM VM PHY VM VM PHY