1 / 19

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 Bellagamba November 24th 2012. SDN, OpenFlow, and SPARC Agenda. 14:00 Introduction to SDN and OpenFlow What is the problem it’s solving?

wanda
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

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

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

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

  5. Split Arch. / SDN • 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

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

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

  8. Network Operating System • 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

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

  10. What is OpenFlow?

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

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

  13. Switch Model 13

  14. Important Messages (proactive)

  15. Important Messages (reactive)

  16. FlowVisor SPARC – Split Architecture.ppt

  17. Standardization, from Stanford to ONF

  18. SDN related activities before SPARC. Most of the focus was here Started here Datacenter Mobile Radio Network Global PacketCore Network Aggregation Network Access Network Enterprise/ Campus Optical Transport Network (Metro/Regio) Optical Transport Network (Backbone)

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

More Related