Panopticon: Incremental SDN Deployment in Enterprise Networks

Transcription

1 Panopticon: Incremental SDN Deployment in Enterprise Networks Stefan Schmid with Dan Levin, Marco Canini, Fabian Schaffert, Anja Feldmann

2 I SDN! How can I deploy it?

3 SDN: Where and why? Datacenters Wide-Area Networks (WANs) IXP...

4 Characteristics? SDN in Datacenters Why SDN? How to deploy?

5 SDN in Datacenters Characteristics? Already highly virtualized Quite homogeneous!

6 Why SDN? SDN in Datacenters Realize fabric abstraction Decouple application from physical infrastructure Own addresses for tenants, VM migration,... Improve performance

7 How to deploy? SDN in Datacenters Run Open VSwitch on servers! Edge deployment (inside: MPEC)

8 Characteristics? SDN in WANs Why SDN? How to deploy?

9 SDN in WANs Characteristics? Bandwidth precious (WAN traffic grows fastest) Latency matters Probably not so many sites Many different applications and requirements

10 Why SDN? SDN in WANs E.g., Google B4 Improve utilization Differentiate applications (latency sensitive Google docs vs datacenter synchronization)

11 SDN in WANs How to deploy? Replace IP core routers (running BGP) at border of datacenter (end of long-haul fiber) Gradually replace routers However, benefits arise only after complete hardware overhaul of network (after years)

12 SDN in WANs How to deploy? Replace IP core routers (running BGP) at border of datacenter (end of long-haul fiber) first benefits! Gradually replace routers However, benefits arise only after complete hardware overhaul of network (after years)

13 Our Use Case: Enterprise Networks What s wrong with enterprise networks?

14 Problems with traditional networks Manual, Device-Centric Network Configuration (CLI, LANmanager) Un-evolved Best Practices (tcpdump, traceroute - from the 1990s) Current Networks Complex, Leaky, Low-level Interfaces (VLANs, Spanning Tree, Routing)

15 Software Defined Networking Automation und Abstraction for Networks Network policy defined programatically Current Networks Our goal Automation and Abstraction SDN

16 SDN Interface f(view) f(view) f(view) Control Programs Control Programs Global Network View Control Programs Controller Platform

17 The SDN Deployment Problem Full SDN Must upgrade to SDN incrementally A real large-scale campus network

18 Key Questions How can we incrementally deploy SDN into enterprise campus networks? What SDN benefits can be realized in a hybrid deployment?

19 Current Hybrid Networks SDN Platform? Legacy Mgmt E.g., part of the Stanford network. Dual-stack approach

20 Current Hybrid Networks SDN Platform? Legacy Mgmt App 1 App 2 SDN Platform App 3 Legacy Mgmt Dual-stack approach Edge-only approach

21 The edge is legacy access switches

22 PANOPTICON SDN ARCHITECTURE Operate the network as a (nearly) full SDN TOOL Determine the partial SDN deployment

23 The Existing Network

24 1. Planning the SDN Deployment SDN controlled port (SDNc) A Network architect provides set of ingress ports to be controlled via SDN B C D E F

25 Network topology Traffic estimates resource aware optimizer Partial SDN deployment Objectives Upgrade budget Path delay Tunable parameters Price model Utilization thresholds (link utilization, VLANs, etc.)

26 The Partial SDN Deployment ( ) B C A D E F

27 Benefits of Partial SDN Deployment? B C Harvest A unutilized network capacity D E F

28 Main benefits of SDN= Principled orchestration of the network policy

29 Can partial SDN deployment still take advantage of principled network orchestration

30 2. Realizing the Benefits of SDN Insight #1: 1 SDN switch Policy enforcement IDS B C Middlebox traversal A D E Access control F

31 2. Realizing the Benefits of SDN Insight #1: 1 SDN switch Policy enforcement B C A Insight #2: 2 SDN switches Fine-grained control D E F Traffic load-balancing

32 Insight #1: 1 SDN switch Policy enforcement Insight #2: 2 SDN switches Fine-grained control Ensure that all traffic to/from an SDN-controlled port always traverses at least one SDN switch SDN Waypoint Enforcement Legacy devices must direct traffic to SDN switches

33 The PANOPTICON SDN Architecture Conceptually group SDN ports in Cell Blocks B C A D E F

34 The PANOPTICON SDN Architecture Traffic restricted by using VLANs B C A D F Per-port spanning trees that ensure waypoint enforcement E

35 PANOPTICON A B Logical SDN A B C D E F C D E F

36 App 1 App 2 SDN Platform App 3 A Logical SDN B C D E F PANOPTICON provides the abstraction of a (nearly) fully-deployed PANOPTICON SDN in a partially upgraded network

37 What is the value of a logical SDN

38 Use Case: Planned Maintenance Operator says: You re Going down for service... A B C D E...and, could the rest of you switches cooperate to minimize the disruption? Let software worry about the dependencies, not the human operator! F

39 Use Case Testbed Evaluation 2x NEC IP8800 (OF 1.0) 1x Cisco C3550XL 3x Cisco C2960G 2x HP 5406zl 1x Pica TCP Connection Recovery Time Locations of port-down events along one path traversing SDN switch.

40 Use Case: Planned Maintenance 3) Update forwarding rules to re-route green flow A 1) Operator signals intent to our application, to remove switch for maintenance. B C D 4) 2) Gratuitous Install forwarding ARP for rules destination for green flow C. E F

41 Use Case Testbed Evaluation 2x NEC IP8800 (OF 1.0) 1x Cisco C3550XL 3x Cisco C2960G 2x HP 5406zl 1x Pica8 3290

42 What is the impact of partial SDN deploymenton the network traffic

43 Potential Impact on Traffic 1. Congestion B A 2. Harvest unutilized network capacity C D E F

44 Network Emulation Experiments 77 switches... of which 28 are IP routers MSS of 536 Bytes 489 SDNc ports B C A D Links limited to 100 MBit/s E F

45 Workload Packet-level enterprise network traffic traces B C Defines a traffic matrix A D E F

46 Workload Traffic Matrix: 1024 source-destination communication pairs B C A D Sequentially initiate TCP flows until 100 MB are sent from every Port E F

47 TCP Throughput Comparison Ethernet switch Vary the number of deployed SDN switches: 5, 10, and 28 B C B C A D vs. A D E F E F Legacy IP router Panopticon

48 SDN Deployment Size vs. Performance Key Takeaway: When only 36% of the switches support SDN, median throughout virtually identical to legacy network

49 Key Results Highlights Evaluated a large campus network (1500+ switches) Real topologies and real traffic traces Upgrade 2% of the switches/routers 100% SDN-controlled ingress ports avg. path stretch < 50% 90th percentile link util. < 25% increase

50 Summary App 1 App 2 SDN Platform App 3 SDN ARCHITECTURE Operate the network as a (nearly) full SDN A TOOL Determine the partial SDN deployment B C D E F PANOPTICON

51 Median values of 10 random TM permutations 1296 SDNc Ports 10 policy rules per port (avg) 1024 VLANs

52 Other Ongoing Projects STN: Concurrent Control Plane Provably Dataplane Connectivity Consistent Network Updates AeroFlux: Wifi SDN with near-sighted control