Top Banner
Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November 24th 2012
19

Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Mar 23, 2016

Download

Documents

Wanda

Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain. Pontus Sköldström - Wolfgang John – Elisa Bellagamba November 24th 2012. SDN, OpenFlow, and SPARC Agenda. 14:00 Introduction to SDN and OpenFlow What is the problem it’s solving? - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Pontus Sköldström - Wolfgang John – Elisa BellagambaNovember 24th 2012

Page 2: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

SDN, OpenFlow, and SPARCAgenda

14:00 Introduction to SDN and OpenFlow What is the problem it’s solving? Protocols and models

14:15 SPARC, use-cases and results Requirements and Controller Architecture Implementations – MPLS and Split BRAS Network Virtualization

15:10 Coffee break 15:25 Overview of Ericsson's SDN-related activity

Operator challenges VNS and Service Chaining

15:55 Future work at Acreo

Page 3: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Introduction to SDN and OpenFlow

What’s the problem and how are we dealing with it?

Pontus SköldströmNovember 24th 2012

Page 4: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Million of linesof source code

5400 RFCs6803 RFCs

Integrated by vendorsClosed, Not reusable

Many complex functions baked into the infrastructureOSPF, BGP, multicast, differentiated services,Traffic Engineering, NAT, firewalls, MPLS, redundant layers, …

Existing Network Equipment

Specialized Packet Forwarding Hardware

OperatingSystem

Feature Feature

Routing, management, mobility management, access control, VPNs, …

4

Page 5: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

› Current situation› Difficult to innovate, especially inter-domain

› Complicated to add new functionality› Standardization is a pain wait for vendor to impl. › Reinvent the wheel (distribution, routing, signaling, ..)› No standard APIs

› Why is software so fast? › Open APIs› Good abstractions

Split Arch. / SDN

Page 6: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Specialized Packet Forwarding Hardware

App

App

App

Specialized Packet Forwarding Hardware

App

App

App

Specialized Packet Forwarding Hardware

App

App

App

Specialized Packet Forwarding Hardware

App

App

App

Specialized Packet Forwarding Hardware

OperatingSystem

OperatingSystem

OperatingSystem

OperatingSystem

OperatingSystem

App

App

App

Network Operating System

App App App

Split Arch. / SDN

6

Page 7: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

App

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

App App

Simple Packet Forwarding Hardware Simple Packet

Forwarding Hardware

Network Operating System

1. Open interface to hardware

3. Well-defined open API

7

2. At least one good operating systemExtensible, possibly open-source

Split Arch. / SDN

Page 8: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

› Network operating system provides:› API for applications – provides an intermediate layer› Network topology – a global view of the network› Network events – filter to find what is important › Distribute configuration to switches – no signaling

› Don’t worry about these basic things anymore› Implement the basics correct, once.› Focus on the functionality you want on top

Network Operating System

Page 9: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

App

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

Simple Packet Forwarding Hardware

App App

Simple Packet Forwarding Hardware Simple Packet

Forwarding Hardware

Network Operating System

IETF ForCesOpenFlow

Routing, switching, monitoring, NAT, …

9

NOX, Floodlight, Trema, ONIXBeacon, Maestro, …

Split Arch. / SDN

Page 10: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

What is OpenFlow?

Page 11: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

OpenFlow Basics

SwitchPort

MACsrc

MACdst

Ethtype

VLANID

IPSrc

IPDst

IPProt

L4sport

L4dport

Match Actions Stats

1. Forward packet to zero or more ports2. Encapsulate and forward to controller3. Send to normal processing pipeline4. Modify Fields5. Any extensions you add!

Packet + byte counters

11

VLANpcp

IPToS

Flow Table Entries (simplified)

Page 12: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Examples

Switching

*

SwitchPort

MACsrc

MACdst

Ethtype

VLANID

IPSrc

IPDst

IPProt

TCPsport

TCPdport Action

* 00:1f:.. * * * * * * * port6

12

VLAN Switching

*

SwitchPort

MACsrc

MACdst

Ethtype

VLANID

IPSrc

IPDst

IPProt

TCPsport

TCPdport Action

* * vlan1 * * * * * port600:1f..

Routing

*

SwitchPort

MACsrc

MACdst

Ethtype

VLANID

IPSrc

IPDst

IPProt

TCPsport

TCPdport Action

* * * * * 5.6.7.8 * * * port6

Page 13: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Switch Model

13

Page 14: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Important Messages (proactive)

Page 15: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Important Messages (reactive)

Page 16: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

08.06.2010 SPARC – Split Architecture.ppt

FlowVisor

Page 17: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

Standardization, from Stanford to ONF

Page 18: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

SDN related activities before SPARC.

Access Network

Mobile Radio Network

Optical Transport Network (Metro/Regio)

Aggregation Network Global Packet

Core Network

Optical Transport Network (Backbone)

Datacenter

18

Enterprise/Campus

Most of the focus was hereStarted here

Page 19: Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain

SDN related activities after SPARC.

Access Network

Mobile Radio Network

Optical TransportNetwork (Metro/Regio)

Aggregation Network

Global PacketCore Network

Optical Transport Network (Backbone)

Datacenter

19

Enterprise/Campus

SPARC first to focus here