sdn – to be or not to be - · pdf filesdn – to be or not to be uwe richter ......

SDN – TO BE OR NOT TO BE

Uwe Richter SE Director Russia/CIS, East and South East Europe [email protected]

2 Copyright © 2013 Juniper Networks, Inc. www.juniper.net

FUNDAMENTAL PROBLEMS TO SOLVE

  Want more innovation in networking §  Want it more quickly too

  Want more control §  Over all aspects – devices, ports, traffic, services, …

  Want more abstraction §  Understand better what I think I’m doing

  Want more visibility §  Understand what is actually happening


SDN IS A NEW ARCHITECTURAL PARADIGM

Management Plane

Service Plane

Control Plane

Forwarding Plane

C

M

S

VMs on x86 C

Control

Forwarding

S S

THE SYSTEM AS A PLATFORM

THE NETWORK AS A PLATFORM


Blank Slide Title and Content

1-Line

It’s going to happen immediately

It’s only about Software

Myth SEVEN MYTHS ABOUT SDN

Reality

It’s only about Data Centers It applies to all network areas and all networking services

It’s only about reducing CapEx OpEx reduction is equally or even more significant

It will fuel hardware innovation

It’s only about centralization It’s about getting the right balance between centralization and distribution

It’s only about OpenFlow OpenFlow is just a protocol, and not even the most important one for SDN

It will happen step-by-step

It’s going to take forever You will see the first results in 2013

$€

∞


SDN AND JUNIPER`S JOURNEY   Juniper Networks Fundamentals

§  Use General Purpose Infrastructure §  Centralize As Much as You Can, Distribute When You Must §  Automate Everything That Can Be Automated §  Leverage an Open Software Platform

  Pre-SDN Juniper Execution §  Open JUNOS with SDK (partners/customers)

§  Router Embedded Service Plane (router blade) with internal service chaining

§  Flexible Service Delivery Gateway (seamless MPLS) §  Open Network Software Appliance (Junos Space / SDK)

§  Software to Hardware offload (Fast-Update-Filters) §  Enhanced control capabilities of the forwarding plane

(BGP Flow Spec, Openflow, Qfabric) §  AAA - Policy and Control Management (SBR / SRC)

A D N

P I O N E E R



1-Line

Centralize Management

Extract Services Centralize Controller Optimize the Hardware

Standard Centralize Separate Use the cloud Common Platform

Apply Broadly

JUNIPER’S SDN STRATEGY: 6-4-1

6 – General Principles

4 – Juniper Steps

1 – New Licensing Model

JUNIPER SOFTWARE ADVANTAGE

Full Use/Elastic Transferable Software Lifetime Assurance



1-Line

Principles of SDN

JUNIPER’S SDN STORY

Customer Benefits Separate networking into four layers – Forwarding, Control, Services and Management

Optimize each network element

Centralize Mgmt, Services and Control layers, as appropriate

Simplifies network design and lowers opex

Cloud for elastic scale, pay-by-use, and cost-effective deployment

Reduce time to services and correlates cost based on value

Common Platform for Network and Security applications Enables new business solutions

Standard protocols for interoperability across vendors Provides choice and lowers cost

Broadly apply to enterprise, mobile & wireline customers & data centers

Flexibility and new business opportunities


Parse and store

User reqts

High-level, declarative specification of network

requirements

Parse and process specification

Data Plane

Data Plane

Data Plane

Data Plane

Data Plane

Data Plane

Management plane

Compile, translate to low level language

Control plane

SDN AS A COMPILER SAY WHAT YOU WANT, NOT HOW


HIGH-LEVEL SPECIFICATION: SERVICE CHAINING

tenant t1-‐a

tenant t1-‐b

tenant rou,ng instance ri-‐t1

tenant t2-‐a

tenant t2-‐b


S1

service rou,ng instance ri-‐s1

S2


Data plane traffic

Control plane route leaking

next-‐hop-‐self + new label

High-level spec: connect “tenant 1” and “tenant 2” via services S1 and S2 Low-level constructs: VRFs, labels, route leaking, BGP next hops

“tenant” could be a class of subscribers, a class of traffic, a business customer or a tenant in a cloud DC

Service instances could be physical or virtual


HIGH-LEVEL SPEC: CHANGING SERVICE CHAINS

tenant t1-‐a

tenant t1-‐b


S1


tenant t2-‐a

tenant t2-‐b


Data plane traffic

Control plane route leaking

next-‐hop-‐self + new label

S3


High-level: connect “tenant 1” and “tenant 2” via services S1, S3 and S2 Low-level: VRFs, labels, route leaking, BGP next hops

S2


The details of how to insert S3 (create new

VRF, change route leaking, next hops, etc.) are the responsibility of

the SDN system

Service chaining via BGP has been tried before; however, managing this “by hand” has

been tried and abandoned: too cumbersome and error-prone



1-Line

EXAMPLE SDN SERVICE CHAIN Datacenter Cloud Application Internet to Web Server Runs as a

VM

Web Server

Internet Router

Stateful Firewall

Application Delivery

Controller

Hypervisor vSwitch



1-Line

EXAMPLE SDN SERVICE CHAIN Data Center Cloud Web Server VM to Mid-tier VM

Physical Network

Runs as a VM

Web Server

Mid-Tier Application

Hypervisor vSwitch

Application Delivery

Controller

Hypervisor vSwitch



1-Line

EXAMPLE SDN SERVICE CHAIN

Mobile Service Provider Edge

Edge Router

Edge Router

Runs as a VM

Stateful Firewall

Deep Packet

Inspection

Carrier Grade

Network Address

Translation

Policy & Charging Enforcem

ent Function

Evolved Packet Core


FOUR LAYER ARCHITECTURE

SDN System

Data Plane (Forwarding) Layer

DP-‐1 DP-‐2 DP-‐N

Management Layer

Configura,on State Opera,onal State

Control Plane Layer

Services Layer and Analy,cs

DP-‐3

CP-‐1 CP-‐2 CP-‐M

Northbound APIs NB APIs

Centralized

Distributed, but not 1-1 with DP

Highly distributed but not dumb

OpenStack CLI GUI OSS



1-Line

SOFTWARE

SECURITY & NETWORKING DEVICES

Past

HARDWARE

FOR

WA

RD

ING

BLA

DES

C

ON

TRO

L PR

OC

ESSO

R

SER

VER

BLA

DES

OSS/BSS

CLI

SERVICES

MANAGEMENT

FORWARDING

OR



1-Line

SOFTWARE

SECURITY & NETWORKING DEVICES

2012

HARDWARE

FOR

WA

RD

ING

BLA

DES

C

ON

TRO

L PR

OC

ESSO

R

SER

VER

BLA

DES

OSS/BSS

CLI

SERVICES

MANAGEMENT

FORWARDING

OR

Management Services



1-Line

CENTRALIZATION

Network Element 1

Forwarding Layer

Local Control layer

Configuration copy

Network Element… n

Forwarding Layer

Local Control layer

Configuration copy

Network Element 2

Forwarding Layer

Local Control layer

Configuration copy

Centralized Controller

Centralized Management

Centralized Services

CENTRALIZED FUNCTIONS DISTRIBUTED DEVICES



1-Line

STEP 1: Centralize Management

Orchestration OSS/BSS

Custom Applications

Management VMs

Analytics VMs

Dat

a C

ente

r O

rche

stra

tion

HARDWARE SOFTWARE

CONFIGURATION COPY

FORWARDING SERVICES

Option A

Option B

X86 SERVER RACK

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

X86

SE

RV

ER

B

LAD

ES

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

Published Protocols Open standard where

possible



1-Line

STEP 2: Extract Services

Custom Applications

Mgmt & Analytics VMs

Analytics VMs

Dat

a C

ente

r O

rche

stra

tion

HARDWARE SOFTWARE

CONFIGURATION COPY

FORWARDING SERVICES

Option A

Option B

X86 SERVER RACK

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

X86

SE

RV

ER

B

LAD

ES

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

TETHERED SERVICES



1-Line

JUNIPER In 2013

Custom Applications

Junos Space

SGSN/MME, Media Cache

Juno

sV

Orc

hest

ratio

n

MX HARDWARE JUNOS SOFTWARE

CONFIGURATION COPY

FORWARDING SERVICES

Option A

Option B

X86 SERVER RACK

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

X86

SE

RV

ER

B

LAD

ES

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

R

TETHERED SERVICES



1-Line

STEP 3: Centralize the controller

Dat

a C

ente

r O

rche

stra

tion

HARDWARE SOFTWARE

CONFIGURATION COPY

FORWARDING

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PR

OC

ES

SO

RS

SERVICE CHAINING

Custom Applications


Services VMs

Central Controller VMs

X86 CLOUD

SERVICES



1-Line

JUNIPER In 2014/2015

VM

war

e or

O

penS

tack

MX AND SRX HARDWARE JUNOS SOFTWARE

CONFIGURATION COPY

FORWARDING SERVICES FO

RW

AR

DIN

G B

LAD

ES

X86

RO

UTI

NG

EN

GIN

E

SERVICE CHAINING

Custom Applications

Junos Space

Juniper Linux ServiceVMs

Contrail Controller VMs

X86 CLOUD

JunosV App Engine



1-Line

STEP 4:

Dat

a C

ente

r O

rche

stra

tion

HARDWARE SOFTWARE

X86 SERVER RACK

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PRO

CES

SOR

X86

SER

VER

B

LAD

ES

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PRO

CES

SOR

Option A

Option B

FOR

WA

RD

ING

B

LAD

ES

CO

NTR

OL

PRO

CES

SOR

Option C

Option D

X86 CLOUD

X86 CLOUD

CONFIGURATION COPY

LOCAL CONTROL

OPTIMIZED FORWARDING

Custom Applications


Services VMs

Central Controller VMs

SERVICE CHAINING

Optimize the Hardware


JUNIPER SDN MACHINERY

  A new flexible software licencing scheme

  Build a framework for software to run on x86 platforms

  Develop a to-be-standardized Service Chaining framework with provisioning from VM to device (router/FW/switch)

§  Service Control plane §  A Enhanced Data Plane

JUNIPER SOFTWARE ADVANTAGE

Full Use / Elastic Transferable

Software Lifetime

Assurance


DEMO/TRIAL

  Demos in progress §  Many already done for providers in the US and APAC §  Demo at MPLS World Congress §  Demos can be done in the Amsterdam PoC lab

  SDN System available in beta soon §  Target: DC use case

  JSP/JVAE targeted for later this year §  Target: Service Edge use case

Cпасибо !

sdn – to be or not to be - · pdf filesdn – to be or not to be uwe richter ......

Documents