OpenFlow/Software Defined Networks

1. OpenFlow/Software Defined Networks

2. Exec Summary • OpenFlow/SDN enables innovations within • Enterprise, backbone, & data center networks • Represents a promising architecture direction • Providers like it for their own reasons • Enabling an ecosystem • OpenFlow/SDN networks are being deployed • R&E networks around the world Time for regionals to get involved. Take advantage of GPO Solicitation 3.

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

4. Feature Feature Million of linesof source code Operating System Billions of gates Specialized Packet Forwarding Hardware The Ossified Network Routing, management, mobility management, access control, VPNs, … 5400 RFCs Barrier to entry 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”, reluctant to change

5. The SDN Approach Separate control from the datapath • i.e. separate policy from mechanism Datapath: Define minimal network instruction set • A set of “plumbling primitives” • A vendor-agnostic interface: OpenFlow Control: Define a network-wide OS • An API that others can develop on

6. Network OS Operating System Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware Operating System Operating System Operating System Specialized Packet Forwarding Hardware Restructured Network Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Specialized Packet Forwarding Hardware Specialized Packet Forwarding Hardware Feature Feature

7. 2. At least one Network OSprobably many.Open- and closed-source 3. Well-defined open API The “Software-defined Network” Feature Feature 1. Open interface to hardware Network OS OpenFlow Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

8. OpenFlow Basics Narrow, vendor-agnostic interface to control switches, routers, APs, basestations.

9. Step 1: Separate Control from Datapath Network OS OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch

10. Step 2: Cache flow decisions in datapath “If header = x, send to port 4” “If header =y, overwrite header with z, send to ports 5,6” “If header = ?, send to me” Flow Table OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch

11. Plumbing Primitives • Match arbitrary bits in headers: • Match on any header; or new header • Allows any flow granularity • Actions: • Forward to port(s), drop, send to controller • Overwrite header with mask, push or pop • Forward at specific bit-rate Data Header Match: 1000x01xx0101001x

12. 2. At least one Network OSprobably many.Open- and closed-source 3. Well-defined open API The “Software-defined Network” Feature Feature 1. Open interface to hardware Network OS OpenFlow Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

13. Feature Feature Network Operating System 1 Network Operating System 2 Network Operating System 3 Network Operating System 4 Virtualization or “Slicing” Layer (FlowVisor) Isolated “slices” Many operating systems, or many versions Feature Feature Open interface to hardware Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

14. Some research examplesat Stanford

15. FlowVisor Creates Virtual Networks FlowVisor PlugNServe Load-balancer OpenFlow Wireless Demo OpenPipes Demo OpenFlow Protocol OpenFlow Protocol OpenPipes Policy OpenFlow Switch OpenFlow Switch OpenFlow Switch Multiple, isolated slices in the same physical network [Paper in submission] [Sigcomm 2009 – Best Demo]

16. Demo Infrastructure with Slicing

17. OpenPipesPartition hardware designs across a network [Sigcomm 2009 – 2nd Best Demo] [Paper in submission]

18. Load-balancing as Network Primitive Goal: Minimize http response time over campus network Approach: Route over path to jointly minimize <path latency, server latency> Internet “Pick path & server” Load-Balancer Network OS OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch [Sigcomm 2009 Demo] [Paper in preparation]

19. Intercontinental VM Migration Moved a VM from Stanford to Japan without changing its IP. VM hosted a video game server with active network connections. [Sigcomm 2008– Best Demo]

20. Feature Feature NOX Converging Packet and Circuit Networks Goal: Common control plane for “Layer 3” and “Layer 1” networks Approach: Add OpenFlow to all switches; use common network OS OpenFlow Protocol OpenFlow Protocol WDM Switch IP Router IP Router TDM Switch WDM Switch [Supercomputing 2009 Demo] [OFC 2010]

21. ElasticTree • Goal: Reduce energy in data center networks • Approach: • Reroute traffic • Shut off links and switches to reduce power DC Manager “Pick paths” Network OS [NSDI 2010]

22. ElasticTree • Goal: Reduce energy in data center networks • Approach: • Reroute traffic • Shut off links and switches to reduce power DC Manager “Pick paths” Network OS X X X X X [NSDI 2010]

23. Exec Summary • OpenFlow/SDN enables innovations within • Enterprise, backbone, & data center networks • Represents a promising architecture direction • Providers like it for their own reasons • Enabling an ecosystem • OpenFlow/SDN networks are being deployed • R&E networks around the world Time for regionals to get involved. Take advantage of GPO Solicitation 3.

24. New Data Center Cost 200,000 servers Fanout of 20  10,000 switches $5k commercial switch  $50M $1k custom-built switch  $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

25. Cellular Networks • Recently made transition to IP • Billions of mobile users • Need to securely extract payments and hold users accountable • IP is dreadful at both, yet hard to change

26. Telco Operators e.g. AT&T, DT, NTT, … • Global IP traffic will grow 5x by 2013 • End-customer monthly bill remains unchanged • Therefore, CAPEX and OPEX need to be reduced 5x by 2013 • But in practice, reduces by <20% per year Q: How can operators reduce cost? Q: How can they differentiate their service? A: SDN is a potential solution they want to explore

27. Now, introducing: • Srini Seetharaman seethara@stanford.edu

28. Matt Davy’s Strawman Approach to a Regional Deployment of OpenFlow

29. OpenFlow building blocks Monitoring/debugging tools oftrace oflops openseer Stanford Provided ENVI (GUI) LAVI GENI Aggregate Manager Applications n-Casting SNAC Nicira NOX Controller Slicing Software FlowVisor Console FlowVisor Stanford Provided Commercial Switches Software Ref. Switch NetFPGA Broadcom Ref. Switch HP, NEC, Pronto, Juniper.. and many more OpenFlow Switches OpenVSwitch OpenWRT PCEngine WiFi AP 29

30. OpenFlow Vendor Hardware Product Prototype Juniper MX-series Cisco Catalyst 6k (prototype) Core Router HP ProCurve5400 and others NEC IP8800 Enterprise Campus Data Center Arista 7100 series (Q4 2010) Pronto Circuit Switch Ciena CoreDirector WiMAX (NEC) more to follow... Wireless 30

31. Commercial Vendors

32. Ecosystem coming together Disclaimer: level of the interest differs Vendors (Hardware/Software) Providers Academy Chip Vendors Switch/Router Vendors - Enterprise & Backbone - Packet & Circuit - Wireless New Class Data Center Google, Amazon, Microsoft, .. NW Provider DT, DoCoMo (Level3, BT, Verizon,..) Researchers Research & Education Networks 33

33. Exec Summary • OpenFlow/SDN enables innovations within • Enterprise, backbone, & data center networks • Represents a promising architecture direction • Providers like it for their own reasons • Enabling an ecosystem • OpenFlow/SDN networks are being deployed • R&E networks around the world Time for regionals to get involved. Take advantage of GPO Solicitation 3.

34. OpenFlow as GENI Networking Substrate Eight universities and two national research backbones

35. OpenFlow Deployment at Stanford • OpenFlow-enabled buildings • Gates Computer Science Building • CIS EE Building • Packard EE Building (soon) • 20 switches from NEC, HP and Pronto • 50 OpenFlow enabled WiFi APs • WiMAX OpenFlow Service 36

36. An Experiment of OpenFlow-enabled Network (Feb. 2009 - Sapporo Snow Festival Video Transmission) KOREA OpenFlow Network Seoul OpenFlow Switch (Linux PC) Suwon NOX OpenFlow Controller VLAN on KOREN Data Transmission Daejeon TJB Controller TJB Broadcasting Company Deagu Gwangju Busan Sapporo Studio Japan OpenFlow Network Sapporo Japan A video clip of Sapporo snow festival is transmitted to TJB (Daejeon, KOREA) via ABC server (Osaka, JAPAN). Server Asahi Broadcasting Cooperation (ABC) at Osaka, Japan

37. Three New EU Projects:Ophelia, SPARC, CHANGE 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 38

38. Current Trials 68 trials/deployments spanning 13 countries

39. Campuses and Backbones are participating… Time for regionals to deploy, experiment with and benefit from OpenFlow/SDN

40. Regional Opportunity Partner with Stanford, network researchers, and industry to bring innovations to your network and to your customers Deploy OpenFlow packet and circuit infrastructure Allow researchers to innovate on top Take control of your own infrastructure and innovate services as you need them

41. Regionals Well Positioned You have • an infrastructure connecting key institutions • strong relationships with vendors • experience deploying experimental facilities • a track record • deploying high end technologies in support of E-Science applications You have NOT • enabled Internet architecture research as much and this is the time to do this

42. GPO Solicitation Calls for It

43. Interested? Contact Guru Parulkar (parulkar@stanford.edu) or Matt Davy (mpd@grnoc.iu.edu)