Enterprise GENI Nick McKeown nickm@stanford

28
OpenFlowSwitch.org Enterprise GENI Nick McKeown [email protected] anford OpenFlow team: Guido Appenzeller , Glen Gibb , David Underhill David Erickson, Adam Covington, Brandon Heller, Rob Sherwood, oshi Kobayashi, Guru Parulkar, Srinivasan Seetharaman, Yiannis Yiako

description

Enterprise GENI Nick McKeown [email protected]. Stanford OpenFlow team : Guido Appenzeller , Glen Gibb , David Underhill, David Erickson, Adam Covington, Brandon Heller, Rob Sherwood, Masayoshi Kobayashi, Guru Parulkar, Srinivasan Seetharaman, Yiannis Yiakoumis. OpenFlowSwitch.org. - PowerPoint PPT Presentation

Transcript of Enterprise GENI Nick McKeown nickm@stanford

Page 1: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Enterprise GENI

Nick [email protected]

Stanford OpenFlow team: Guido Appenzeller, Glen Gibb, David Underhill, David Erickson, Adam Covington, Brandon Heller, Rob Sherwood,

Masayoshi Kobayashi, Guru Parulkar, Srinivasan Seetharaman, Yiannis Yiakoumis

Page 2: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

EnterpriseGENI

GENIClearing House

EnterpriseGENI

EnterpriseGENI

College CampusNetwork

College CampusNetwork

Page 3: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

GENIAggregateManager

GENIClearing House

College CampusNetwork

College CampusNetwork

OpenFlowProtocol

Page 4: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Staged Approach

1. Define OpenFlow feature2. Add OpenFlow to commercial switches and APs3. Deploy at Stanford4. Integrate with GENI Clearing House5. Deploy on many college campus networks

6. We all create lots of open-source software so researchers can build on each other’s work

(We’re part-way into Stage 2)

Page 5: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

OpenFlow Basics

Page 6: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

OpenFlow Basics (1)

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Action Statistics

Rule(exact & wildcard)

Default Action Statistics

Exploit the flow table in switches, routers, and chipsets

Flow 1.

Flow 2.

Flow 3.

Flow N.

Page 7: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

OpenFlow Basics (2)

Rule(exact & wildcard)

Action Statistics

Small number of fixed actionse.g. unicast, mcast, map-to-queue, drop

Extended via virtual portse.g. tunnels, encapsulate, encrypt

As general as possiblee.g. Port, VLAN ID, L2, L3, L4, …

As wide as possible

Count packets & bytesExpiration time/count

Page 8: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

OpenFlow Switch specification

Controller

OpenFlow Switch

FlowTable

SecureChannel

PCOpenFlow

Protocol

SSL

hw

sw

OpenFlow Basics (3)

Add/delete flow entries Encapsulated packets Controller discovery

Page 9: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Controller

OpenFlow Switch

PC

OpenFlow UsageDedicated OpenFlow Network

OpenFlow Switch

OpenFlow Switch

OpenFlowProtocol

Chip’s code

Rule Action Statistics

Rule Action Statistics Rule Action Statistics

Chip

Page 10: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Usage examples

Chip’s code: Static “VLANs” His own new routing protocol: unicast, multicast,

multipath, load-balancing Network access control Home network manager Mobility manager Energy manager Packet processor (in controller) IPvChip Network measurement and visualization …

Page 11: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

http://OpenFlowSwitch.orghttp://OpenFlowSwitch.org

Page 12: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Let’s see an example…

Page 13: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

HP

Experimental feature on ProCurve 5400-series 144-ports of 1GE, hardware forwarding OpenFlow added by HP Labs and ProCurve group In 23 wiring closets in CS Building at Stanford

Praveen Yalagandula

Jean Tourrilhes

SujataBanerjee

Rick McGeer

CharlesClark

Page 14: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

NEC

Experimental feature on IP8800 series router 24-ports of 1GE, 2-ports of 10GE, hardware

forwarding OpenFlow added by NEC team in Japan NEC announced plans for OpenFlow products Deployed at Stanford and in JGN2plus in Tokyo

HideyukiShimonishi

JunSuzuki

MasanoriTakashima

NobuyukiEnomoto

PhilavongMinaxay

ShuichiSaito

TatsuyaYabe

YoshihikoKanaumi

NEC/NICT NEC/NICT

AtsushiIwata

Page 15: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Juniper

OpenFlow added to Junos SDK First platform: MX-480 carrier class Ethernet 24-ports 10GE or 240-ports 1GE Hardware forwarding Deployed in Internet2 in NY and at Stanford

Umesh Krishnaswamy

MichaelaMezo

ParagBajaria

JamesKelly

BobbyVandalore

Page 16: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Cisco

Experimental feature on Catalyst 6509 Software forwarding Deployed at Stanford

QuickTime™ and a decompressor

are needed to see this picture.

QuickTime™ and a decompressor

are needed to see this picture.

FlavioBonomi

SaileshKumar

PereMonclus

Page 17: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Nicira

MartinCasado

ScottShenker

TeemuKoponen

NatashaGude

JustinPettit

Created NOX controller Available at http://NOXrepo.org (GPL) Deployed at Stanford

Controller

Page 18: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Using Enterprise GENIfor research

Page 19: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Step 1: Separate VLANs for Production and Research Traffic

Normal L2/L3 Processing

Flow Table

Production VLANs

Research VLANs

Controller

Page 20: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Step 2: Virtualize OpenFlow Switch

Normal L2/L3 Processing

Flow Table

Flow Table

Flow TableResearcher A VLANs

Researcher B VLANs

Researcher C VLANs

Production VLANs

Controller A

Controller B

Controller C

Page 21: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Virtualizing Control

OpenFlow Switch

OpenFlow Switch

OpenFlow Switch

OpenFlowProtocolOpenFlowProtocol

OpenFlowHypervisor & Policy Control

Craig’sController

Heidi’sControllerAaron’s

Controller

OpenFlowProtocolOpenFlowProtocol

Page 22: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Virtualizing Control

OpenFlow Switch

OpenFlow Switch

OpenFlow Switch

OpenFlowProtocol

OpenFlowHypervisor & Policy Control

Netadmin’sexperiments

Multicast

OpenFlowProtocol

httpLoad-balancer

Page 23: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

GENIAggregateManager

GENIClearing House

Enterprise GENI

OpenFlowHypervisor & Policy Control

OpenFlowProtocol

OpenFlowProtocol

Page 24: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Many Open Questions!

Scalability of a controller Load-balancing over redundant controllers Federation, hierarchy and aggregation Protecting the controller against DDOS

Our goal is to enable the research community to explore all these questions

Page 25: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Thanks…

(It takes a village)

Page 26: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

Internet2 Team

Chris Small Matt Zekauskas Installing Juniper MX-480 in NY

Page 27: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.orgStanford Team

Page 28: Enterprise  GENI Nick McKeown nickm@stanford

OpenFlowSwitch.org

We plan trials in early 20095-6 college campuses

Contact us if you would like to take part

[email protected]