OpenFlow Workshop APAN FIT Workshop ‐ Hong Kong APAN FIT Workshop Hong Kong Chris Small – Indiana University Feb 22 2011
Sections Sections • OpenFlow concepts, hardware and software l h d d f • OpenFlow use cases – Network Operators View – Network Operators View • Demos D • Discussion
Operations Operations • Focus on why and how to deploy a OpenFlow h d h d l O l network – Someone deploying OpenFlow Apps not necessarily building them – Concepts C t – Nuts and Bolts – What software is availible • Resources for OpenFlow h http://www.openflowswitch.org/wk/index.php/H // fl i h / k/i d h /H OTITutorial2010
Keys to Openflow/Software ‐ Defined Networking • Separation of Control Plane & Data Plane with S i f C l l & l i h Open API Between the Two • Logically Centralized Control ‐ Plane with Open API to Applications • Network Slicing/Virtualization • Creates Open Interfaces between Hardware, OS and Applications Similar to Computer Industry and Applications Similar to Computer Industry • Increases Competition, Enables Innovation
So why interesting to operations? So why interesting to operations? • Researchers can use to OpenFlow to explore new network ideas – Quick turn around from idea to deployment • Operators also can use OpenFlow to build (or • Operators also can use OpenFlow to build (or eventually purchase) interesting apps – “À la carte” networking – Inexpensive hardware p – Provide an infrastructure
App App App App App App Network Operating System Ap Ap Ap p p p Operating System Ap Ap Ap p p p Specialized Packet Forwarding Hardware Operating System Ap Ap Ap Specialized Packet p p p Forwarding Hardware di d Operating System Ap Ap Ap p p p Specialized Packet Forwarding Hardware Operating System System Specialized Packet Forwarding Hardware Ap Ap Ap p p p Operating S System t Specialized Packet Slide from Nick McKeown at Stanford Forwarding Hardware
The “Software ‐ defined Network” 2. At least one good operating system 3. Well ‐ defined open API Extensible, possibly open ‐ source App App App App App App Network Operating System 1. Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding H Hardware d Simple Packet Forwarding Hardware Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Slide from Nick McKeown at Stanford Hardware
Trend Trend App App App App App App Controller Controller Controller 1 Windows Mac NOX Controller 1 Windows Mac 2 Linux Windows Network OS Mac Linux 2 OS (OS) Linux OS (Network OS) (OS) ( (OS) ) OS Virtualization or “Slicing” Virtualization layer x86 OpenFlow (Computer) Computer Industry Network Industry Slide from Nick McKeown at Stanford
OpenFlow Basics
OpenFlow Basics (1) OpenFlow Basics (1) Exploit the flow table in switches, routers, and chipsets Rule Flow 1. Action Statistics ( (exact & wildcard) t & ild d) Rule Flow 2. Action Statistics (exact & wildcard) (exact & wildcard) Rule Flow 3. Action Statistics (exact & wildcard) Rule Flow N. Default Action Statistics (exact & wildcard) OpenFlowSwitch.org
OpenFlow Basics (2) OpenFlow Basics (2) Rule A ti Action St ti ti Statistics (exact & wildcard) As general as possible Count packets & bytes e.g. Port, VLAN ID, L2, L3, L4, … Expiration time/count As wide as possible Small number of fixed actions e.g. unicast, mcast, map ‐ to ‐ queue, drop Extended via virtual ports p e.g. tunnels, encapsulate, encrypt
Flow Table Entry OpenFlow 1.0 Switch Rule Action Stats Packet + byte counters 1. Forward packet to port(s) 2. Encapsulate and forward to controller p 3. Drop packet 4. Send to normal processing pipeline Switch MAC MAC Eth VLAN IP IP IP TCP TCP Port src dst type ID Src Dst Prot sport dport + mask + mask
OpenFlow Basics (3) p Controller OpenFlow Switch specification p p PC OpenFlow Switch Secure sw Channel Add/delete flow entries Encapsulated packets Flow hw hw Controller discovery Table OpenFlowSwitch.org
OpenFlow Usage Dedicated OpenFlow Network Dedicated OpenFlow Network Controller Chip’s code Chip s code PC OpenFlow Switch Rule Action Statistics OpenFlow Protocol OpenFlow OpenFlow Rule Action Statistics Rule Action Statistics Switch Switch Switch Switch OpenFlowSwitch.org Chip
What to do with OpenFlow ? What to do with OpenFlow ? • 1k ‐ 3k TCAM Entries in Typical Edge Switch • Difficult to take advantage of: Difficult to take advantage of: – Manual Config, SNMP Writes, RADIUS – Limited Actions (allow/deny) Li it d A ti ( ll /d ) – Vendor Specific • But what if you could program these through a standard API ? through a standard API ?
Possible Uses of Openflow (Quick Wins) • Security Applications – NAC – IDS/IPS – Remote Packet Capture & Injection Remote Packet Capture & Injection • VM Mobility – Redirect specific application traffic to remote site – Flow ‐ based forwarding – no need to extend entire Flow based forwarding no need to extend entire broadcast domain – no STP issues
Other Applications Other Applications • Load Balancing g • n ‐ cast – multiple streams over lossy networks l l l k • Policy (Firewall) y ( ) – SNAC • Flow based network provisioning • Flow based network provisioning
Intercontinental VM Migration Moved a VM from Stanford to Japan without changing its IP. VM hosted a video game server with active network connections.
Possible Uses of Openflow p (Quick Wins) • Dynamic Circuit Provisioning – Don’t need to extend layer ‐ 2 end ‐ to ‐ end y – Simply direct specific flows down a engineered path with guaranteed priority path with guaranteed priority – Don’t have to rely on scripted SSH sessions, SNMP or other sub optimal ways to programmatically or other sub ‐ optimal ways to programmatically configure switches/routers.
Possible Uses of Openflow p (Grand Challenges) • Distributed Control ‐ Plane Architecture Requires a Lot of State to be Synchronized q y Across Many Devices • Many Protocols Needed for Synchronization • Many Protocols Needed for Synchronization Internally to Networks (OSPF, RSVP, STP, etc) • Can these “internal” protocols eventually be removed entirely with only BGP for inter ‐ removed entirely with only BGP for inter domain route advertisements ?
OpenFlow Paradigm shifts OpenFlow Paradigm shifts • “Wireless like” management of wired switches • Manipulate virtual switches over many Manipulate virtual switches over many physical devices – VM Migration demo VM Mi ti d • OSI model breakdown • Control at the flow level
Deployments
GENI GENI • GENI OpenFlow deployment on 8 campuses • Internet2 and NLR backbones Internet2 and NLR backbones • Integrated with Production hardware on campuses • Backbone, Regionals (funded in GENI , g ( Solicitation 3) and Campuses interconnected • Outreach to more campuses in future? O t h t i f t ?
Internet2 and NLR Internet2 and NLR • Internet2 – Backbone of 5 NEC IP8800 – Multiple 1G connections (in each direction) – L2circuits between sites L2circuits between sites • NLR – Backbone of 5 HP 6600 ‐ 24XG – 10 G wave between sites 10 G wave between sites
NLR – I2 OpenFlow Core p OpenFlow Core Connectivity v.1.0 IU BBN N LR I nt ernet 2 NLR DENV I2 WASH I2 NEWY NLR CHIC NLR ATLA I2 ATLA NLR SEAT I2 LOSA NLR SUNN I2 HOUS U of Wash VLAN 3715 Stanford VLAN 3716
IU Campus Deployment IU Campus Deployment • Focused on Edge (Closet) Deployment • Goals: Goals: – Stress ‐ Test Current Implementations – Verify “Sandboxing” of Openflow V if “S db i ” f O fl – Develop Monitoring Tools – Prepare for Production Deployments
IU Deployment IU Deployment • HP switches in Testlab and Production – 4 6600s in Bloomington testlab g – 1 5406in Testlab/Wireless – 2 5406 used by Engineering 2 5406 used by Engineering – 3500 in Gigapop • Pronto switches (w/ Purdue Calumet) • NetGear switches • NetGear switches • NetFPGA 10G and 1G?
3 New EU Projects: OFELIA, SPARC, CHANGE
EU Project Participants EU Project Participants • Germany • Germany – ACREO AB (Sweden) – ACREO AB (Sweden) – Ericsson AB Sweden (Sweden) – Deutsch Telekom Laboratories • Hungary – Technishche Universitat Berlin – European Center for ICT p – Ericsson Magyarorszag gy g – ADVA AG Optical Networking Kommunikacios Rendszerek – NEC Europe Ltd. KFT – Eurescom • Switzerland • United Kingdom U it d Ki d – Dreamlab Technologies D l b T h l i – University of Essex – Eidgenossische Technische – Lancaster University Hochschule Zurich – University College London University College London • Italy Italy • Spain – Nextworks – i2CAT Foundation – Universita` di Pisa – University of the Basque y q • Belgium g Country, Bilbao – Interdisciplinary Institute for • Romania Broadband Technology – Universitatea Politehnica – Universite catholique de B Bucuresti ti L Louvain i • Sweden
OpenFlow Deployment in Japan OpenFlow Deployment in Japan NEC and JGN2Plus (NICT) 32 • Network virtualization and slicing • HD video distribution in different slices – Baseball game – Snow festival
Recommend
More recommend
