juniper unified sdn technical presentation (sdn day itb 2016)

UNIFIED SDNMochammad [email protected]

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

AGENDA

What is SDN?§ Definition and goals of SDN§ Analogy with Compute Virtualization§ Orchestration via the “next-gen SMS”§ Unified SDN

What parts of the network does SDN touch?

Conclusion


DEFINITION AND GOALS OF SDN

SDN has many definitions and many goalsSeparation of control

and data planesInteroperability, innovation,

higher feature velocity

OpenFlow-based data plane

Standardized, powerful

Increasing use of CPUs (Intel “x86” processors)

General purpose, cheap, ubiquitous

Next-gen NMS: orchestration and

automation

Lower OpEx, faster service delivery SMS = Service

Management System

Separation of control and data planes

Programmability, more network control


SEPARATION OF CONTROL AND DATA PLANESCENTRALIZATION OF CONTROL PLANE à “NOS”

DataPlane

Control

DataPlane

Control

DataPlane

Control

…

Network Operating System

Network Application

Network Application

Network Application

Network State Transform via Network Apps


DISCUSSION

What is the real problem at hand?§ CapEx?§ OpEx?§ Resource efficiency?§ Greater network control?§ Increasing revenue?§ Speed of service rollout?

Of course, all of the above J

Will writing network apps achieve these goals?§ This approach may be tactically suitable for some cases§ But in general seems too low-level, and ultimately not manageable


IS A ROUTER JUST CONTROL AND DATA PLANE?

DataPlane

Control

DataPlane

Control

DataPlane

Control

…

Config ConfigConfig

Academic view ofa router

Actuality of a

router

Interoperable(more so than not)

Not standardized;

not at all interoperable! This is also

where agility is needed


RESTORING AGILITY:SEPARATE CONFIG FROM REST OF ROUTER

DataPlane

Control

DataPlane

Control

DataPlane

Control

…

Config ConfigConfig

Orchestration Layer

The goal: service agility via orchestration:

freedom from “physics”, process, bureaucracy

RESTful APIs


ORCHESTRATION VIA THE NEXT-GENSERVICE MANAGEMENT SYSTEM

Just as in Compute Virtualization, so in networks: we need the ability to orchestrate and automate§ especially service creation and management

Such an ability will save OpEx, offer greater network control, and speed up service rollout, leading to an increase in revenues§ It will also improve resource efficiency, leading to CapEx savings

But how is this different from current Network Management Systems, or OSSes?§ First, let’s describe the approach, then discuss this


WHAT IS “NEXT-GEN” ABOUT THIS APPROACH?

Service definition is based on abstract information models§ These are high-level: device and OS and version independent§ They are standardized, but allow for provider-specific

enhancements§ Service deployment is transformation of an abstract service

definition to device-specific data models

In this system, service deployment will be:§ Fungible – I can use a given device for many services§ Flexible – I can deploy a service at many devices (placement)§ Fast – I can roll out a service quickly, redeploy quickly

§ Responsive – the service adapts dynamically to changes

Provisioning

Analytics and Automation


servicereqts

High-level, declarativespecification of service requirements

Parse specificationProcess analytics

Device 1

Device 6

Device 5

Device 4

Device 3

Device 2

NetworkAnalytics

Service configuration

lives here

SDN AS A COMPILERSAY WHAT YOU WANT, NOT HOW TO DO IT

Configuration is sent to chosen device

Process &

compile

A DB

SDN systemS

DB


UNIFIED SDN

SDN Transformation Engine

Service model 1

Service model 2

Service model 3

Device model 1

Device model 2

Device model 3

OSS/Orchestration

Device 1 Device 3 Device 4 Device nDevice 2

Access Edge/NFV/DC Core/Inter-DC

Abstract

Device level


SERVICE SDN ARCHITECTURE

Process &

compile A DB

SDN systemS

DB

Core

VPNPEs

Edge

CPE

Agg2

Service Instance1

Service Instance2

Service Instance3

Service instance database

Real-time network

information

Metro Ethernet N/w

L2VPN PEs

Analytics database

Programdevices

Service instances defined via service

data modelsSelf-

ServicePortal

SDN for L2VPN


AGENDA

What is SDN?

What parts of the network does SDN touch?§ Virtualized Data Centers§ SDN for NFV§ Core SDN§ Access/Edge SDN

Conclusion


WHAT PARTS OF THE NETWORK DOES SDN TOUCH?

ACX4000/MX104

ACX4000/MX104

MX240/480

MX240/480

MX960

MX960

ACX1000

BUSINESSACCESS

RESIDENTIALACCESS

ACX1000

ACX1000

MOBILEACCESS

CONVERGED ACCESS/HUB-SITE ROUTER

AGGREGATION ROUTER

CELL-SITE / CPE

EDGE ROUTER

CEN Access(CKT/ETH/MPLS)

CEN aggregation(MPLS)

CEN Core(MPLS)

MUX/DEM

UX

amp amp amp amp

Core

amp amp amp amp

MUX

/DE

MUX

MUX/DEM

UX

MUX

/DE

MUX

SERVICECENTER

To other metros

Virtualized DC

Access SDN Edge SDN

NFV

WAN SDN: Centralized and Multi-Layer Traffic Engineering

CPE SDN


CONCLUSION: THE SDN PARADIGM

The paradigm of SDN as a Network Operating System to form the basis for network programming is too low-level

The paradigm of SDN as a Compiler for provisioning via abstract service models is a high-level, declarative approach

This paradigm is standards-based while allowing for provider-specific enhancements

This paradigm applies to all parts of the network: DC, inter-DC, access, edge, NFV, core

juniper unified sdn technical presentation (sdn day itb 2016)

Technology