1 / 45

Unifying Packet & Circuit Networks with OpenFlow

http://openflowswitch.org. Unifying Packet & Circuit Networks with OpenFlow. Saurav Das, Guru Parulkar , & Nick McKeown Stanford University Huawei , Feb 3 rd 2010. Internet has many problems Plenty of evidence and documentation Internet’s “root cause problem”

kera
Download Presentation

Unifying Packet & Circuit Networks 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. http://openflowswitch.org Unifying Packet & Circuit Networkswith OpenFlow Saurav Das, Guru Parulkar, & Nick McKeown Stanford University Huawei, Feb 3rd 2010

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

  3. Million of linesof source code 500M gates 10Gbytes RAM We have lost our way Routing, management, mobility management, access control, VPNs, … App App App 5400 RFCs Barrier to entry Operating System Specialized Packet Forwarding Hardware Bloated Power Hungry

  4. Hardware Datapath Software Control iBGP, eBGP IPSec Authentication, Security, Access Control Multi layer multi region Firewall Router L3 VPN anycast IPV6 NAT multicast Mobile IP HELLO OSPF-TE HELLO L2 VPN RSVP-TE VLAN MPLS HELLO 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. Reality App App App App App App Operating System Operating System Specialized Packet Forwarding Hardware Specialized Packet Forwarding Hardware • Lack of competition means glacial innovation • Closed architecture means blurry, closed interfaces

  6. Glacial process of innovation made worse by captive standards process Deployment Idea Standardize Wait 10 years • Driven by vendors • Consumers largely locked out • Glacial innovation

  7. Change is happening in non-traditional markets 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

  8. 3. Well-defined open API The “Software-defined Network” 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

  9. The change has already started In a nutshell • Driven by cost and control • Started in data centers…. and may spread • Trend is towards an open-source, software-defined network • Growing interest for cellular and telecom networks

  10. 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 Large data center operators are moving towards defining their own network in software.

  11. Trend App App App App App App Controller 1 Controller 2 Controller 1 Controller 2 NOX (Network OS) Network OS Windows (OS) Linux Mac OS Windows (OS) Linux Mac OS Windows (OS) Linux Mac OS Virtualization or “Slicing” Virtualization layer OpenFlow x86 (Computer) Computer Industry Network Industry Simple common stable hardware substrate below+ programmability + strong isolation model + competition above = Result : faster innovation

  12. Decoupled Automated Control Controller Open Interface Into Hardware OpenFlow Protocol Simple, Robust, Reliable Data Path Control Signaling Data

  13. Rule (exact & wildcard) Flow 1. Rule (exact & wildcard) Rule (exact & wildcard) Rule (exact & wildcard) Default Action Statistics Statistics Statistics Statistics Action Action Action Flow 2. Flow 3. Flow N. The Flow Abstraction Exploit the flow table in switches, routers, and chipsets e.g. Port, VLAN ID, L2, L3, L4, … e.g. unicast, mcast, map-to-queue, drop Count packets & bytes Expiration time/count

  14. OpenFlow Switching Controller OpenFlow Switch OpenFlow Protocol SSL Secure Channel sw • Add/delete flow entry • Encapsulated packets • Controller discovery Flow Table hw A Flow is any combination of above fields described in the Rule

  15. Flow Example Statistics Statistics Statistics Action Action Action Rule Rule Rule OpenFlow Protocol Routing Controller A Flow is the fundamental unit of manipulation within a switch

  16. 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 OpenFlow is Backward Compatible Ethernet Switching 00:1f:.. * * * * * * * * * port6 IP Routing * * * * * 5.6.7.8 * * * port6 * Application Firewall * * * * * * * * * 22 drop

  17. 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 OpenFlow allows layers to be combined Flow Switching port3 00:2e.. 0800 vlan1 1.2.3.4 5.6.7.8 4 17264 80 port6 00:1f.. VLAN + App port6, port7 * * * * vlan1 * * * * 80 Port + Ethernet + IP port3 00:2e.. 0800 5.6.7.8 4 port 10 * * * * *

  18. A Clean Slate Approach Goal: Put an Open platform in hands of researchers/students to test new ideas at scale Approach: Define OpenFlow feature Work with vendors to add OpenFlow to their switches Deploy on college campus networks Create experimental open-source software - researchers can build on each other’s work

  19. OpenFlow Hardware Juniper MX-series WiFi NEC IP8800 WiMax (NEC) HP Procurve 5400 Cisco Catalyst 6k Ciena CoreDirector Arista 7100 series (Fall 2009) Quanta LB4G (Fall 2009)

  20. OpenFlow Deployments Research and Production Deployments on commercial hardware Juniper, HP, Cisco, NEC, (Quanta), … • Stanford Deployments • Wired: CS Gates building, EE CIS building, EE Packard building (soon) • WiFi: 100 OpenFlow APs across SoE • WiMAX: OpenFlow service in SoE • Other deployments • Internet2 • JGN2plus, Japan • 10-15 research groups have switches

  21. Nationwide OpenFlow Trials UW UnivWisconsin Princeton IndianaUniv Rutgers Stanford NLR Internet2 Clemson GeorgiaTech Production deployments before end of 2010

  22. Motivation GMPLS C C IP and Transport networks  are separate networks that are controlled and managed independently leading to duplication of functions and resources in multiple layers and high capex and opex  do not dynamically interact and thus do not benefit from diverse switching technologies  have very different architectures that makes integrated operation and convergence hard C IP/MPLS D IP/MPLS D D D D D D C C D D IP/MPLS C IP/MPLS D C D C D C D

  23. GMPLS C C C IP/MPLS D IP/MPLS D D D D D D C C D D IP/MPLS C IP/MPLS D UCP C D Flow Network C D C D

  24. pac.c Research Goal: Packet and Circuit Flows Commonly Controlled & Managed Simple, Robust, Reliable network of Flow Switches Simple, Unified, Automated Control Plane Flow Network … that switch at different granularities: packet, time-slot, lambda & fiber

  25. Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport In Port Out Port Out Lambda In Lambda Starting Time-Slot Starting Time-Slot Action OpenFlow & Circuit Switches Packet Flows Exploit the cross-connect table in circuit switches CircuitFlows VCG 25 VCG 25 Signal Type 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

  26. Unified Architecture Networking Applications App App App App Unified Control Plane NETWORK OPERATING SYSTEM Unifying Abstraction OPENFLOW Protocol Packet Switch Circuit Switch Underlying Data Plane Switching Packet & Circuit Switch

  27. Network Recovery OpenFlow UCP enables innovation @ pkt-ckt interface Congestion Control Routing Traffic Engineering QoS Power Mgmt Security Discovery OpenFlow Protocol

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

  29. Example Application (1) Congestion Control ..via Variable Bandwidth Packet Links

  30. OpenFlow Demo at SC09

  31. Example Application (2) Traffic Engineering

  32. Example Application (2) Traffic Engineering ..via Dynamic Automated Optical Bypass

  33. OpenFlow protocol Controller NetFPGA based OF packet switch NOX Ethernet Hosts AWG WSS (1×9) Fujitsu WSS based OF circuit switch AWG WSS (1×9)

  34. OpenFlow packet switch OpenFlow packet switch 25 km SMF GE-Optical GE-Optical Mux/Demux Openflow Circuit Switch

  35. Unified Virtualization C C OpenFlow Protocol C FLOWVISOR OpenFlow Protocol CK P CK CK P CK CK P P

  36. Unified Virtualization ISP ‘A’ Client Controller Private Line Client Controller High-end Client Controller C C OpenFlow Protocol C FLOWVISOR Under Transport n/w Service Provider control OpenFlow Protocol D CK P D CK D Single Physical Infrastructure of Packet & Circuit Switches D CK Isolated Client Network Slices D D D P D D CK CK D D P D D D P D D D D D D D D D D D D D

  37. Summary • OpenFlow is a large clean-slate program with many motivations and goals • convergence of packet & circuit networks is one such goal • OpenFlow simplifies and unifies across layers and technologies • packet and circuit infrastructures - electronics and photonics • while unified API allow innovations • in data and control planes independently • in network control, management and virtualization • Example demonstrations at circuit & packet intersection • Variable Bandwidth Packet Links • Dynamic Automated Optical Bypass • More @ http://openflowswitch.org/wk/index.php/PAC.C

  38. Backup

  39. Issues with Current IP & Transport n/w • Separate management systems and incompatible protocols - complexity of managing across several layers, interfaces & architectures, leading to duplication of resources and functions • Lack of a unified architecture across packet and circuit – • fully distributed with tightly linked control and data planes in packet networks, • fully distributed, decentralized or fully centralized in transport networks, • multiple vendor domains with proprietary interfaces prevent greater integration and increase complexity • GMPLS the only attempt towards a UCP across packet & circuit (2000) • Today – Packet vendors and ISPs are not interested • Transport n/w SPs view it as a signaling tool available to the mgmt system for provisioning private lines (not related to the Internet) • After 10 yrs of development, next-to-zero significant deployment • GMPLS Issues 

  40. Issues with GMPLS • Issues are when considered as a unified architecture and control plane • control plane complexity escalates when unifying across packets and circuits because it • makes basic assumption that the packet network remains same: IP/MPLS network – many years of legacy L2/3 baggage • and that the transport network remain same - , multiple layers and multiple vendor domains • use of fragile distributed routing and signaling protocols with many extensions, increasing switch cost & complexity, while decreasing robustness • does not take into account the conservative nature of network operation - • can IP networks really handle dynamic links? • Do transport network service providers really want to give up control to an automated control plane? • does not provide easy path to network virtualization

  41. Hardware Datapath Software Control Transport NE PWE3 L1VPN, L2VPN PCE CORBA LMP ASON PBB-TE GMPLS TL-1 Carrier Ethernet MPLS-TP OSPF-TE HELLO HELLO HELLO ENNI intra RSVP-TE ENNI inter UNI Many complex functions baked into the infrastructure More coming ……

  42. Control Plane Architectures Control Plane OF Protocol Data Plane

  43. OpenFlow: Architecture Concepts • Separate data from control • A standard protocol between data and control • Define a “generalized flow” based data path • Very flexible and generalized flow abstraction • Delayer or open up layers1-7 • Hierarchically centralized “open” controller with API • For control and management applications • Virtualization of data and control planes • Backward compatible • Though allows completely new header

  44. OpenFlow: Architecture Implications • Separate data from control • Independent innovations in data and control planes • Less dependence on a single vendor • Define a “generalized flow” based data path • Simpler data path: cheaper, uniform, stable • Applicable across technologies and layers • Hierarchically centralized “open” control with an API • Easier to make reliable and robust • Enables lots of innovations by different stakeholders

  45. OpenFlow: Architecture Implications • Virtualization • Enable innovations and experimentation • Deployment of new ideas: “production revision control” • Backward compatible • Easy to support in existing switches/routers and networks • Easy to show the value proposition Software Defined Networking

More Related