14
OpenFlow Stanford University / Ericsson Collaboration Mobile World Congress 2013

Openflow Stanford University - Ericsson Collaboration

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Openflow Stanford University - Ericsson Collaboration

OpenFlow Stanford University / Ericsson Collaboration

Mobile World Congress 2013

Page 2: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 2

Application

Simple Packet

Forwarding Hardware

Application Application

Simple Packet

Forwarding Hardware

Simple Packet

Forwarding Hardware

Simple Packet

Forwarding Hardware

Data Plane

Separation of Data and ControlPlane

Open interface to forwarding

(L1/L2/L3) such as Openflow

Well-definedopen API

In collaboration with:

Openflow & Sdn

Specialized Packet

Forwarding

Hardware

Operating

System

App

App

App

Specialized Packet

Forwarding

Hardware

Operating

System

App

App

App

Specialized Packet

Forwarding

Hardware

Operating

System

App

App

App

Specialized Packet

Forwarding

Hardware

Operating

System

App

App

App

Network Operating System

Page 3: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 3

Stanford Research ObjectivesEricsson Research

› Scalable and reliable Service Provider SDN

architecture

› Inline service chaining and traffic steering as a

new SDN application

› Integration of Cloud and Service Provider SDN

controller platforms

› Statical analysis and dynamic

troubleshooting

› SDN for Home

networks

› Connectivity management on

mobile devices

Problem to solve

› Evaluate different design choices

› Improve networkperformance

› Leverage the SDN

platform for new applications

› SDN architecture and design

› New features added to existing protocols

› New applications built

on top of SDN

Ericsson is a founding member of Open Networking Research Center (ONRC)

Open Network research

contributions

In collaboration with:

Page 4: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 4

› Service chain: An ordered list of services (NAT, firewall, DPI, etc.)

› Dynamically derived from subscriber, application, and service ordering policies

› Unidirectional: different upstream and downstream service paths

› Multiple service paths per subscriber

Inline service chaining

and traffic steering

SERVICEA

SERVICEA

SERVICEA

BNGSERVICE

AROUTER

SERVICEA

SERVICEA

Service Path 1 (Upstream)Service Path 2 (Downstream)Service Path 3 (Voice)Service Path 4 (Video)

In collaboration with:

Page 5: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 5

Controller-Switch Connectivity

Internet2 3SOE Deployment› Controller placement for

− Maximum resiliency (Ericsson Research)

− Minimum average delay (Stanford University)

› Optimizing control traffic routing for combined

resiliency-delay metric

› Network partitioning: switch to controller assignment for

maximum resiliencyController location for minimum average delayController location for maximum resiliency

In collaboration with:

Page 6: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 6

Elastic Networking for OpenStack

Applications

› Connectivity and bandwidth

on demand− Cloud – Cloud

− Cloud – Enterprise

› Simple, customer usable API

− Reduces operator management overhead

• Tight integration with

OpenStack Quantum data center networking

− End to End, Data Center to WAN to X, virtual networking

Disaster Recovery

Remote Backup and Replication

Enterprice VoIP in the Cloud

Streaming Video with SLAs

GW

SWIFT NOVA QUANTUM ELASTIC

NETWORKING

INTERNAL

NETWORKINGAGENT

INTERNAL API

SITE A SITE B

SITE C (e.g. Enterpise)

GW

INTERNAL

NETWORKINGAGENT

SWIFT NOVA QUANTUM

INTERNAL NETWORKING AGENT

GW

In collaboration with:

Page 7: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 7

Ericsson OPENFLOW/SDN RESEARCH in next steps

Integrated Network Control

Service Exposure

Network and Cloud Management

TelcoData

Center

Separation of Data and ControlPlane

Well-definedopen API

In collaboration with:

Simple Packet

Forwarding Hardware

Simple Packet

Forwarding Hardware

Simple Packet

Forwarding Hardware

Simple Packet

Forwarding Hardware

Data Plane

Open interface to forwarding

(L1/L2/L3) such as Openflow

Network Operating System

Application Application Application

Page 8: Openflow Stanford University - Ericsson Collaboration

Mobile World Congress 2013 | © Ericsson AB 2013 | 2013-02-25 | Page 8

Ericsson OPENFLOW/SDN RESEARCH in next steps

Integrated Network Control

Service Exposure

Network and Cloud Management

TelcoData

Center

OpenFlow/SDNIn collaboration with:

Page 9: Openflow Stanford University - Ericsson Collaboration
Page 10: Openflow Stanford University - Ericsson Collaboration

Overview

Users Network Operators Content Providers

1. Improve User Experience 2. Improve Network Operation

Leverage Programmable Networks and SDN to :

Page 11: Openflow Stanford University - Ericsson Collaboration

Putting Users in Charge of their Network

Myth 1 : Dumb Users

• Preferences

• Current experience

• Context

Myth 2 : Too Complex

• Queues / User easy

• SDN

ISPContent Provider

PolicyMakers

User Agents

• Capture User Preferences & Feedback

• Translate into Network Semantics

• Communicate to ISP

ISPs

• Configure network, paths, queues

• Expose Network Interface

Page 12: Openflow Stanford University - Ericsson Collaboration

Hercules –

Making use of all networks around us

Google

Data

Center

Netflix

CDNGoogle Netflix

•OpenFlow switch

•Scheduling

Page 13: Openflow Stanford University - Ericsson Collaboration

Header Space Analysis

HSA Parser

Network State:

Topology, Configs,

Forwarding Tables, etc.

T1(h,p) T2(h,p)

T3(h,p)

Real NetworkModel of Network

Simple and Protocol Agnostic

Abstraction of Forwarding

Functionality.

Network Debugging:

Checking Reachability,

Finding Forwarding Loops,

etc.

Network Monitoring:

Automatic Test Packet

Generation with Maximum

Coverage

Real Time Policy Checking for

SDNs:

Detect violating changes before

they hit the data plane

Page 14: Openflow Stanford University - Ericsson Collaboration

Easier network troubleshooting using Packet Histories

Network Admin

Packet History: the full path, modifications, and headers

encountered during a packet’s journey through the network.

NetSightNetwork

“Host A can’t talk to Host B.

Show me where packets from A to B are going and why.”

“Some hosts are failing to grab IP addresses. Show me all

DHCP traffic.packet [MAC src: 0x123, ...]:

switch 1: { in/out port:mods:switch state:

matched rules:switch 2: { …

Questions AnswersNetSight returns Packet Histories, which provide direct

evidence to troubleshoot networks.