1 / 32

Packet and Circuit Convergence with OpenFlow

Stanford Clean Slate Program. http://cleanslate.stanford.edu. Packet and Circuit Convergence with OpenFlow . Guru Parulkar parulkar@stanford.edu with Saurav Das (Stanford), Nick McKeown (Stanford), Preeti Singh (Ciena), Dan Getachew (Ciena), Lyndon Ong (Ciena) .

adler
Télécharger la présentation

Packet and Circuit Convergence with OpenFlow

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. Stanford Clean Slate Program http://cleanslate.stanford.edu Packet and Circuit Convergence with OpenFlow Guru Parulkarparulkar@stanford.eduwith Saurav Das (Stanford), Nick McKeown (Stanford), Preeti Singh (Ciena), Dan Getachew (Ciena), Lyndon Ong (Ciena) Funded by Cisco, Deutsche Telekom, DoCoMo, Ericsson, Google, LightSpeed, MDV, NEC, NSF, Xilinx

  2. Outline • OpenFlow/Software Defined Networking • Unifying packet and circuit networks • Why providers like it

  3. Internet has many problems Plenty of evidence and documentation Internet’s “root cause problem” It is Closed for Innovations

  4. Million of linesof source code 500M gates 10Gbytes RAM We lost our way Routing, management, mobility management, access control, VPNs, … App App App 5400 RFCs Operating System Specialized Packet Forwarding Hardware Bloated Power Hungry Many complex functions baked into the infrastructure • OSPF, BGP, multicast, differentiated services,Traffic Engineering, NAT, firewalls, MPLS, redundant layers, … • An industry with a “mainframe-mentality”

  5. OpenFlow: Enable Innovations “within” the Infrastructure Net Services PC OpenFlow Switch OpenFlow Protocol API SSL Controller Secure Channel sw • Add/delete flow entries • Encapsulated packets • Controller discovery Flow Table hw

  6. Sliced and Virtualized OpenFlow Infrastructure C C Research Team A Controller Research Team B Controller Production Net Controller OpenFlow Protocol C FLOWVISOR Control Plane API Control Plane API OpenFlow Protocol D D D D D D D Isolated Network Slices D D Physical Infrastructure Packet&Circuit Switches: wired, wireless, optical media D D D D D D D D D D D D D D D D D D

  7. Example Network Services • Static “VLANs” • New routing protocol: unicast, multicast, multipath, load-balancing • Network access control • Mobile VM management • Mobility and handoff management • Energy management • Packet processor (in controller) • IPvX • Network measurement and visualization • …

  8. OpenFlow Enabled Switches/Routers/APs Juniper MX-series WiFi NEC IP8800 WiMax (NEC) Cisco Catalyst 3750 (2010) Ciena CoreDirector HP Procurve 5400 Cisco Catalyst 6k Arista 7100 series (2010) More to follow... Quanta LB4G

  9. OpenFlow as GENI Networking Substrate D D D D D D D D D D D D D D D D D D D D D D D D D A nationwide network before end of 2010 D D

  10. European Deployment Pan-European experimental facility • L2 Packet • Emulation • Wireless • Content delivery • L2 L3Packet • Optics • Content delivery • L2 Packet • Wireless • Routing • L2 Packet • Optics • Content delivery • L2 Packet • Shadow networks

  11. OpenFlow: A Hack to Experiment? Is there a bigger architecture story with business implications?

  12. OpenFlow: Enable Innovations “within” the Infrastructure Net Services PC OpenFlow Switch OpenFlow Protocol API SSL Controller Secure Channel sw • Add/delete flow entries • Encapsulated packets • Controller discovery Flow Table hw

  13. 3. Well-defined open API Architecturally what It Means 2. At least one good operating system Extensible, possibly open-source 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

  14. Packet and Circuit Convergence with OpenFlow

  15. Motivation GMPLS C C IP & Transport Networks (Carrier’s view) C IP/MPLS D IP/MPLS D D D D D D • are separate networks managed and operated • independently • resulting in duplication of functions and • resources in multiple layers • and significant capex and opex burdens • … well known C C D D IP/MPLS C IP/MPLS D C D C D C D

  16. Convergence is hard • … Two networks have • very different architectures • … previous attempts assumed networks remain the same We believe true convergence will come about from architectural change!

  17. Software Defined Networking Research Goal: Packet and Circuit Flows Commonly Controlled & Managed D D D D D D D D D Simple, network of Flow Switches Simple, Unified, Automated Control Plane D UCP D Flow Network D D … that switch at different granularities: packet, time-slot, lambda & fiber

  18. Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Out Port In Port In Lambda Out Lambda Starting Time-Slot Starting Time-Slot Action OpenFlow & Circuit Switches PacketFlows Exploit the cross-connect table in circuit switches Circuit Flows VCG Signal Type VCG Signal Type The Flow Abstraction presents a unifying abstraction … blurring distinction between underlying packet and circuit and regarding both as flows in a flow-switched network

  19. R R S S A A OpenFlow Example P3 IP 11.12.0.0 + VLAN2, P1 VLAN2 VCG 3 STS192 1 VCG5 P1 VC4 1 VCG3 P2 VC4 4 IP11.13.0.0TCP80 VLAN1025 + VLAN7, P2 + VLAN2, P2 VLAN7 VCG5 P1 VC4 10 OpenFlow (software) OpenFlow (software) IN OUT Packet Switch Fabric Packet Switch Fabric TDM Circuit Switch Fabric VCG3 VCG5 GE ports TDM ports

  20. Network Recovery Converged packets & dynamic circuits opens up new capabilities Congestion Control Routing Traffic Engineering QoS Power Mgmt VPNs Discovery OpenFlow Protocol

  21. Example Application Congestion Control ..via Variable Bandwidth Packet Links

  22. OpenFlow Demo at SC09

  23. Demo Video http://www.openflowswitch.org/wk/index.php/PAC.C

  24. Why providers want it

  25. New Generation Providers Already Buy into It In a nutshell • Driven by cost and control • Started in data centers…. What New Generation Providers have been Doing Within the Datacenters • Buy bare metal switches • Write their own control/management applications on a common platform

  26. Example: New Data Center Cost 200,000 servers Fanout of 20 a 10,000 switches $5k commercial switch a $50M $1k custom-built switch a $10M Savings in 10 data centers = $400M Control Optimize for features needed Customize for services & apps Quickly improve and innovate • The value prop applies to enterprise and service provider networks

  27. Going Forward • They want to apply this approach to other parts of their infrastructure • Work together to bring this change at a bigger scale Another way to look at it …

  28. 3. Well-defined open API “Meeting of Minds” with Providers 2. At least one good operating system Extensible, possibly open-source 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

  29. Consequences • More innovation in network services • Owners, operators, 3rd party developers, researchers can improve the network • E.g. energy management, data center management, policy routing, access control, denial of service, mobility • Lower barrier to entry for competition • Healthier market place with reducing Capex&OpEx

  30. Ecosystem Coming TogetherRole for Everyone to Contribute • Researchers and R&E Networks • Providers: old and new • Google, Amazon, Yahoo!, (Microsoft, Facebook), • DT, DoCoMo, BT (Level3, Verizon, …) • Box vendors • Enterprise and backbone • Packet and circuit (electronic and photonics) • Incumbents and startups • Chip vendors • Broadcom, Dune, Marvell, …. The Value Chain

  31. OpenFlow As Networking Substrate • A platform for innovations • Within enterprise, backbone, & data center networks • Providers already buy into this vision • For their own reasons • Opportunities • Eco system is coming together • Time to engage

  32. Thank You!!

More Related