Presentation is loading. Please wait.

Presentation is loading. Please wait.

Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November.

Similar presentations


Presentation on theme: "Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November."— Presentation transcript:

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

2 SDN, OpenFlow, and SPARC Agenda  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

3 Introduction to SDN and OpenFlow What’s the problem and how are we dealing with it? Pontus Sköldström November 24th 2012

4 Million of lines of source code 5400 RFCs 6803 RFCs Integrated by vendors Closed, Not reusable Many complex functions baked into the infrastructure OSPF, BGP, multicast, differentiated services, Traffic Engineering, NAT, firewalls, MPLS, redundant layers, … Existing Network Equipment Specialized Packet Forwarding Hardware Operating System Operating System Feature Routing, management, mobility management, access control, VPNs, … 4

5 ›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

6 Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Ap p Specialized Packet Forwarding Hardware Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Ap p Network Operating System App Split Arch. / SDN 6

7 App Simple Packet Forwarding Hardware App Simple Packet Forwarding Hardware Network Operating System 1. Open interface to hardware 3. Well-defined open API 7 2. At least one good operating system Extensible, possibly open-source Split Arch. / SDN

8 ›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

9 App Simple Packet Forwarding Hardware App Simple Packet Forwarding Hardware Network Operating System IETF ForCes OpenFlow Routing, switching, monitoring, NAT, … 9 NOX, Floodlight, Trema, ONIX Beacon, Maestro, … Split Arch. / SDN

10 What is OpenFlow?

11 OpenFlow Basics Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot L4 sport L4 dport MatchActions Stats 1.Forward packet to zero or more ports 2.Encapsulate and forward to controller 3.Send to normal processing pipeline 4.Modify Fields 5.Any extensions you add! Packet + byte counters 11 VLAN pcp IP ToS Flow Table Entries (simplified)

12 Examples Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * 00:1f:.. *******port6 12 VLAN Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action ** vlan1 ***** port6 00:1f.. Routing * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * *** ***port6

13 Switch Model 13

14 Important Messages (proactive)

15 Important Messages (reactive)

16 SPARC – Split Architecture.ppt FlowVisor

17 Standardization, from Stanford to ONF

18 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 here Started here

19 SDN related activities after SPARC. Access Network Mobile Radio Network Optical Transport Network (Metro/Regio) Aggregation Network Global Packet Core Network Optical Transport Network (Backbone) Datacenter 19 Enterprise/ Campus SPARC first to focus here


Download ppt "Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November."

Similar presentations


Ads by Google