Cisco Software Defined Networks & EPN - Cisco Connect TR '14

Software Defined Networks & Cisco Evolved Programmable Network

Alexander Preusche

Consulting Systems Engineer EMEAR

[email protected]

Cisco and/or its affiliates. All rights reserved. Presentation_ID Cisco Public

Agenda

3

SDN Introduction and SP Industry Initiatives

Evolved Programmable Network – Infrastructure Layer

SDN Control and Orchestration Layer

Network Application Layer

– DEMO

Summary

SDN Introduction and SP Industry Initiatives


What is Software Defined Networking?

Separation of Control and Forwarding Plane

Centralized Management – Global View

Open and Programmable Flexibility and Innovation at Software Speed

Application Interaction

Virtualized Ressources

Simplicity, Automation

SDN Layers

Infrastructure Layer

NCS NCS

Open

APIs

Open

APIs

EDGE CORE

Access

VM VM

Edge

Core

VM

Orchestration and Control Layer

VM / Storage Control

Service Catalog Service Orchestration Apps

VM

Application Layer

CDN

Cisco and/or its affiliates. All rights reserved. Presentation_ID Cisco Public 6

“…In the SDN architecture, the control and data planes are decoupled, network intelligence and state are logically centralized, and the underlying network infrastructure is abstracted from the applications…”

https://www.opennetworking.org/images/stories/downloads/white-papers/wp-sdn-newnorm.pdf

“Open protocol that specifies interactions between de-coupled control and data planes……..open standard that enables researchers to run experimental protocols in campus networks. Provides standard hook for researchers to run experiments, without exposing internal working of vendor devices……”

http://www.openflow.org/wp/learnmore/

Open source project formed by industry leaders and others under the Linux Foundation. “…OpenDaylight's mission is to facilitate a community-led, industry-supported open source framework, including code and architecture, to accelerate and advance a common, robust Software-Defined Networking platform…”

http://www.opendaylight.org/

Key SP Industry Initiatives (1) SDN, OpenFlow, Open Daylight










Cisco Confidential 7

“Open vSwitch (OVS) is a production quality open source software switch designed to be used as a vswitch in virtualized server environments.……Open vSwitch supports standard management interfaces (e.g. sFlow, NetFlow, IPFIX, RSPAN, CLI), and is open to programmatic extension and control using OpenFlow and the OVSDB management protocol”

Self-Organizing Network (SON): ….Automation of some network planning, configuration and optimisation processes via the use of SON functions can help the network operator to reduce OPEX by reducing manual involvement in such tasks.

Key SP Industry Initiatives (2) SON, Openstack, Open vSwitch

http://www.3gpp.org

http://openvswitch.org

Open source software for building public and private Clouds; includes Compute (Nova), Networking (Neutron) and Storage (Swift) services.

http://www.openstack.org







NFV Initiative

– Initiative announced at “SDN and OpenFlow World Congress”, Darmstadt, Oct 2012

Use of cloud technology to support network functions

– Management, Control and Data plane components

Not technically related to SDN

Value Proposition

– Shorter innovation cycle

– Improved service agility

– Reduction in CAPEX and OPEX

ETSI based standardization

Extract from ”Network Functions Virtualisation – Introductory White Paper

Open

Innovation

Software

Defined

Networks

Network

Functions

Virtualisation

Key SP Industry Initiatives (3) NFV (Network Functions Virtualisation)

NFV = Transition of network infrastructure services to run on virtualised

compute platforms – typically x86


NAT

VM

Firewall

VM

SBC

VM

dDOS

VM

Virus Scan

VM

IPS

VM

DPI

VM

CGN

VM

Portal

VM

PCRF

VM

DNS

VM

DHCP

VM

BNG

VM

SDN Ctrl.

VM

RaaS

VM

WLC

VM

WAAS

VM

CDN

VM

Caching

VM

NMS

VM

Cisco UCS

Network infrastructure/Service Functions run on

Virtualized x86 compute platforms

• Key Enabler: Cloud

– Hypervisor & x86 compute hardware

– Network automation / orchestration

• Benefits:

– Faster service provisioning/Agility

– Shorter innovation cycle

– CAPEX & OPEX Savings

• SDN complementary, but not mandatory

NfV (Network Functions Virtualization)


The SDN Proposal The “purist” viewpoint

Data Plane

Control Plane

Data Plane

Provisioning Controller

Today SDN / OF

Devic

e

Vendor-specific

APIs

Openflow

Protocol

SDN Optimist View • Simpler to configure

• More flexible

• More scalable

• Cheaper/Monetisation

SDN Pessimist View • Reinventing the wheel

• Moving complexity around

protocol integrations

Centralised

Distributed

“…In the SDN architecture, the control and data planes are decoupled,

network intelligence and state are logically centralized, and the

underlying network infrastructure is abstracted from the applications…”

Openflow

Hardware

Key Factors in SDN evolution

• SDN needs “simplification” and an Evolution of current environment

• Collaborative “Hybrid” Control plane adoption

• Abstraction layers and Programmability via API’s/Protocols

• Use case driven based on SDN models

Conclusion: Derive the common themes and adapt to thrive

bring real value to SPs


Centralized - PCE TE Path placement

Global topology view

Global TE requirements

Predictable tunnel placement

Network wide optimized tunnel placement

Distributed – Head End TE Path Calculation

Global topology view

Local TE requirements

Unpredictable TE tunnel placement

Overall n/w sub-optimal tunnel placement

“centralised optimisation enables ~30% more traffic for the same installed capacity”

PCE/ N/W SDN CONTROLLER

Centralized Control Example - Network Optimization

The Collaborative “Hybrid” Control Plane


Distributed Control Example – IGP Network Convergence

CT = time to: detect failure + signal to controller + calculate new path + disseminate + update FIBs

Major failure multiple devices will be doing this at the same time

– Impulse load on controller and paths to controller, difficulty correlating of events, failure in paths to controllers

Distributed – Network Convergence

The Collaborative “Hybrid” Control Plane

Fully Centralized Control

RIB

FIB FIB FIB

CPU

CPU CPU CPU

IGP server


The Collaborative “Hybrid” Control Plane True Service Level Benefits

Distributed Components –Functions tightly coupled to data plane

– IGP convergence, OAM and physical link state driven protection, Distributed SON

Centralized Components –Functions where a holistic/abstracted view is required

– PCE (Path Computation Element) Traffic Placement : 30% efficiency, Centralised SON

Existing distributed control plane ->Augmented by centralised control plane function

Application

Distributed Control Plane

Data Plane

Centralized Control Plane

APIs

Traditional Control Plane

Architecture

(Distributed)

SDN Control Plane Architecture

(Centralized)

Collaborative Control Plane

Architecture


Enable a holistic Network Programming model

Leverage and extend infrastructure at pace of the business

Deploy common applications across all devices

Extend/upgrade/add features without upgrading the network operating system

Reduced time to market by leveraging common platform for building services

Transport/Device/ASICs

Network Service

Management

Orchestration

Applications/Development Application development

frameworks, e.g. Spring,…

Programmatic network

automation,,..

Automated, policy directed service and cloud management, e.g. OpenStack, …

Network wide service access: Optimized paths (PCE), Topology & service selection (NPS/ALTO)

Device configuration, state monitoring, logging, debugging

Harvest Network

Intelligence

Program for Optimized

Experience

Forwarding

Control Common control abstractions: Security, Policy, Routing, ..

Common forwarding abstractions: Data-Path access, Flow-Forwarding, Tunneling, ..

“Strict SDN”

Network Programmability – Multiple Layers Full-Duplex access to the network at multiple layers and networking planes


Application Frameworks, Management Systems, Controllers, ...

Device

Forwarding

Control

Network Services

Orchestration

Management

“Protocols”

onePK API & Agent Infrastructure

…

…

I2RS

I2RS

PCEP

PCEP

Ouantum

Neutron

OpenFlow

OpenFlow

OMI

OMI

Netconf

Netconf

Puppet

Puppet

BGP-LS

BGP-LS

onePK

Operating Systems – IOS / NX-OS / IOS-XR

BGP Diameter

Radius SNMP …

APIs and Agents Linkage to OnePK Framework


What is REST?

REpresentational State Transfer (REST) is an API architecture style that can use HTTP to send messages between a client and server, piggyback on existing HTTP Internet

Perl

Python

C#

Java

Server REST API

Applications HTTP Packets

Svr

.

Ap

p

• Using REST, applications can Create/Read/Update/Delete

• A REST service is platform-independent, language-independent

• App can be browser-based or standalone

Evolved Programmable Network - EPN


TDM Era

TDM rigidity limits new services, forces architectural shift

Voice Centric

Defined by reliability

IP NGN Era

Commoditization of IP services plus high traffic growth limits profitability

Network migration to multi-service transport & a single protocol

Data Centric

Defined by convergence and scale

Move into an applications centric service environment

Take advantage of the shift from static connectivity to virtualized service creation

EPN becomes the flexible network fabric linking data centres with SP networks

Application centric

Defined as programmatic and dynamic

Entering a New Era in the SP Network Evolution

Edge

Access/ Agg

IP Core

Orchestrated with Self-service

App & Network Interaction

Well-known Programmatic Interfaces

Autonomic, with Control & Visibility

Open & Pluggable

Configurable

Apps Independent of Network

Command Line Interface

Managed

Proprietary

Managed

Configurable

Apps Independent of Network

Command Line Interface

Proprietary

EVOLVED PROGRAMMABLE NETWORK

IPv6

EVOLVED SERVICES PLATFORM

APPLICATIONS


Ultra HD

M2M

Cloud

Mobility Evolved Programmable Network

Open Network Strategy Open SDN/NFV Innovations for an Evolved Programmable Network

NCS NCS

Open

APIs

Open

APIs

EDGE CORE

Access

VM VM

Edge

Core

VM

Evolved Services Platform

VM / Storage Control

Service Catalog Service Orchestration Apps

VM

Applications

CDN

ACCELERATE

OPTIMIZE

MONETIZE ¥ £ € $

Always “ON”

On-Demand Services Anywhere

Dynamic Scale

Application

Interaction Seamless

Experience

Policy

Real-Time Analytics

Fully Virtualized

Intelligent Convergece

Automated

Open and Programmable

Access


Deliver Ultra-High EPN Multi-Service Scalability Convergence without Compromise

Multi-service Hardware Design

• Line rate in the access • Per service HW

structures at PE • Scalable H-QoS • Multicast Replication • HW MAC Learning

HW Accelerated Ultra-High BFD and EOAM Performance & Scale

• 3.3ms BFD • 3.3ms CCM • Fast failure detection • Per LC scale

High Scale by Solution Architecture

• Common high scale

control plane • Optimized forwarding

resources • Scalable EFP-based

service termination

Modular IOS-XR

• Scale as you grow • Distribute processes

between RP and LC • Ultra-high Multi-

Dimension Scale with superior stability

Video Business Cloud Mobile

3.3

ms

Unified

MPLS


Evolved Programmable Network Family Meeting the Needs of Today’s Challenges and Tomorrow’s Opportunities

Fixed and Mobile Convergence

Monetize IoE Opportunity

WAN + DC Physical and Virtual

Global Visibility and Programmability

Multi-Service Core Routing:

Drives 100GE multi-service density with MC Scale

CRS

NCS:

Flexible Network Fabric Converging Core, Edge, Optical, Access, and Data Centre

Edge Portfolio:

Optimized 10GE/100GE Ethernet Density for Scalable Business, Consumer , Mobile, Video

ASR Series

Data Centre

Dense 10GE/40GE/100GE

LAN/SAN Switching Fabric

Virtualized Compute Nexus

UCS

Elastic Access Portfolio:

Converged TDM/Ethernet Aggregation

GPON for wholesale and Mobile & Cloud demarc

Access

NCS


Application Enabled Forwarding

- Each engineered application flow is mapped on a path

- A path is expressed as an ordered list of segments

- The network maintains segments

Simple: less Protocols, less Protocol interaction, less state

- No requirement for RSVP, LDP

Scale: less Label Databases, less TE LSP

- Leverage MPLS services & hardware

Forwarding based on Labels with simple ISIS/OSPF extension

50msec FRR service level guarantees

Leverage multi-services properties of MPLS

Millions of Applications

flows

A path is mapped on a

list of segments

The network only

maintains segments

No application

state

The state is no longer in the network but in the packet

Network (Physical and Virtual Infrastructure) Segment Routing (SR)


65

A packet injected anywhere

with top label 65 will reach Z

Nodal segment: Operator allocates a

label from the SR registry to each node.

For example Z is given label 65 9001

Adjacency segment: Node automatically

allocates a local label for each adjacency.

For example Label 9001 allocated for

adjacency O

A packet injected at node C

with label 9001 is forced

through datalink CO

Forwarding state (segment) is established by IGP

LDP and RSVP-TE are not required

MPLS Dataplane is leveraged without any

modification

push, swap and pop: all what we need

segment = label

A B C

M N O

Z

D

P

A B C D

Z

M N O P

Network (Physical and Virtual Infrastructure) Segment Routing (SR)


Any explicit path can be expressed i.e. ABCOPZ

A B C

M N O

Z

D

P

9001

Packet to Z

65

9001

Packet to Z

65

Packet to Z

Packet to Z

65

Packet to Z

65

9001

72

Packet to Z

65

9001

72

72 72

65

65

Network (Physical and Virtual Infrastructure) Segment Routing Label usage

A B C D

Z

M N O P

SDN Controller / Service Orchestration


SDN Controller – Strategic vision

Two layered environment

Elementary Infrastructure Functions

- Basic capability to interact with the network

- NB APIs

- Device level APIs / Protocols

- Baseline capabilities

Controller application

- Function specific applications

- Utilises Infrastructure controller to interact with n/w

- Potentially multiple controller applications running

Other functions have their own controllers. Example OpenStack with Nova, Swift and glance

Topology Security Device Mgmt Data Collection Data Storage

Elementary Infrastructure Functions

Programming

Device APIs Netconf/Yang PCEP OpenFlow OnePK

Controller Application (Orchestration)

Controller Applications Management

Controller Applications

Applications

SDN Controller

Controller NB APIs

Virtual Networks

Packet Network

Optical

Network

Network/Device APIs

Controller Application

(Data Centre)

Controller Application

(Network)


SDN Controller Examples WAE, Tail-f/NCS & Opendaylight

WAE WAN Automation Engine

NCS Network Control System

ODL Opendaylight


WAN

R1

R2

R3

Cloud Consumer Customer Site

Deployment Collection

Service, Network and Analytics REST APIs

WAN Automation Engine

Content Sites

Service

Broker

WAN Automation Engine: Operational Model Enables Software to Software (Not Human to Human) Interactions

Consumer Service

Request DC Domain

Network Domain

Orchestration Engine


Z with SLA (BW, lat)

shortest-path 65 straight to Z

provides the requested SLA

65

OK, use {65} OK, use {72, 9001, 65}

ABCOPZ meets SLA. I account the BW.

I encode the path as nodal segment to C, adj segment

to O, nodal segment to Z

72

65

9001

Congestion

WAN Controller Future Use-Case: Segment Routing with Centralized Control

A B C

M N O

Z

D

P

A B C D

Z

M N O P

Network Application - Demo

Topology viewer & ACL provisioning using Opendaylight, REST, BGP-LS and Netconf/YANG


Summary The Journey to true SDN/NFV Service Innovation

Simplify

• Convergence / Consolidation • Network Function Virtualization • Service Chaining • Service Orchestration

Accelerate New Services

• Bandwidth on Demand • Virtual Managed Services • Security Services • Premium Mobile Broadband • Cloud DVR

Business Applications Integration

The network proactively adjusts to the application needs in real time

Seamless Experience

On Demand Services Anywhere

Always “On”

Application Interaction

Networks Networks

Networks IPv6