1. Software Defined Networking
Olaf Hagemann
SE Director for DACH and HGM

2. User, Device, App Mobility
SDN Drivers
User, Device, App Mobility
Dynamism
Scale
Complexity
Vendor Dependence
Cost
Cloud-Sourcing
Consumerization of IT
Silo’d Workflows

3. Remember the Mainframe?
App
Specialized Applications
Mac OS
Linux
Windows (OS) or
Programmable Open Interface
Specialized Operating System
Open Interface
Commercial Off The Shelf Microprocessor
Specialized Hardware
The mainframe industry in the 1980s was vertical and closed: it consisted of specialized hardware, operating system and applications --- all from the same company.
A revolution happened when open interfaces started to appear. The industry became horizontal. Innovation exploded.
Vertically integrated
Closed, proprietary
Slow innovation
Controlled industry
Open interfaces
Rapid innovation
Broad industry Participation

4. What is SDN: Networking
App
Specialized Features
Control Plane
Control Plane or
Open Interface
Specialized Control Plane
Merchant Switching Chips
Open Interface
Specialized Hardware
Tight Vertical integration
Closed, proprietary
Slow innovation
Tightly controlled
De-coupling of Layers
Open interfaces
Rapid innovation
Broad Industry Opportunity

5. Software Defined Networking (SDN) Model
Make Control and Management Plane Programmable
Centralize Network Intelligence
Abstract Network Infrastructure for Applications
providing a software abstraction layer above the HW and virtualization layer that can hide & enable management of this bewildering diversity
Separate Control Plane from Data Plane
© 2011 Extreme Networks, Inc. All rights reserved.

6. Today – Closed Boxes, Fully Distributed Protocols
App
Operating
System
App
Specialized Packet Forwarding Hardware
Operating
System
App
Specialized Packet Forwarding Hardware
Operating
System
Historical artifact that forwarding boxes host the code too. Leads to a specific design point for networks. Great for the internet, not so much for the networks the internet connects.
Note each piece.
App
Specialized Packet Forwarding Hardware
Operating
System
Specialized Packet Forwarding Hardware
App
Operating
System
Specialized Packet Forwarding Hardware 6

7. Another Approach – Centralized Control
Network Operating System
Open
App
Operating
System
App
Specialized Packet Forwarding Hardware
Operating
System
App
Specialized Packet Forwarding Hardware
Operating
System
How do we redefine the architecture to open up networking infrastructure and the industry!
By bring to the networking industry what we did to the computing world
App
Specialized Packet Forwarding Hardware
Operating
System
Specialized Packet Forwarding Hardware
App
Operating
System
Specialized Packet Forwarding Hardware 7

8. The “Software-defined Network”
2. At least one good operating system
Extensible, possibly open-source
3. Well-defined open API
App
App
App
Network Operating System
1. Open interface to hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Switches, routers and other middleboxes are dumbed down
The key is to have a standardized control interface that speaks directly to hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware 8

9. Virtualization or “Slicing” Layer
Isolated “slices”
Many operating systems, or
Many versions
App
Network Operating System 1
Network Operating System 2
Network Operating System 3
Network Operating System 4
Open interface to hardware
Virtualization or “Slicing” Layer
Open interface to hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware
Simple Packet Forwarding Hardware

10. Extreme Networks SDN Approach
SDN Apps
VM Lifecycle Management (XNV)
User Identity Management
BYOD
Application Performance Management ….
Management Platforms
Ridgeline
XOS – Extensible, Open Secure
XML
Scripts
External App SDK
OpenStack Quantum Plugin
OpenFlow
Hardware Abstracted
Modular
Predictable Performance
Memory Protected
High Performance Converged Open Fabric
High Capacity
Low Latency
MLAG
DCB

11. Programmability: New Open Interfaces For SDN
Support for OpenFlow across all Ethernet Switch products
Powered by ExtremeXOS
Will be available as a dynamically downloadable module
Hybrid mode of operation
Extending SDN Strategy with OpenFlow
Open Multi-Vendor Approach to SDN
Supporting multiple OpenFlow controllers
Extending SDN Strategy with Openstack
Support for OpenStack Quantum with Plug-In
Launching Xkit for collaborative
Programmable Network Applications
Creating SDN Developer Community Portal with XKit

12. SDN (OpenFlow) Details

13. 22 April 2017
What is OpenFlow?
OpenFlow is a protocol that allows an external node to control the forwarding tables of a switch. 13
© 2011 Extreme Networks, Inc. All rights reserved.

14. Started 2008 at Stanford University
What is OpenFlow?
Started 2008 at Stanford University
Is now driven by Open Networking Foundation(ONF)
ONF has over 70 members including:
Extreme Networks
Broadcom
Google
Microsoft
Yahoo
Facebook
Deutsche Telekom
.....
Extreme builds ethernet switches for cloud, data center and mobile networks.
We have 6,000 customers in 50 countries, including 19 of top 20 mobile operators.

15. What is OpenFlow? Definitions:
22 April 2017
What is OpenFlow?
Definitions:
OpenFlow-only switch: supports the mandatory client features of the OpenFlow protocol.
OpenFlow-capable switch: supports the mandatory client features of OpenFlow in addition to normal switch functions (e.g., STP, EAPS).
Controller: supports the server feature of the OpenFlow protocol. Manages the forwarding behavior of one or more OpenFlow switches.
Flow entry: the basic unit of forwarding management.
Flow table: consists of a set of priority ordered flow entries. A switch may support more than one flow table.
Emergency flow table: flow table that the switch uses in case connectivity with all configured controllers fails.
A switch may simultaneously connect to multiple Controllers, but only one controller is master.
Flowvisor: can be used to slice a switch into multiple logical switches, each managed by a different Controller. 15
© 2011 Extreme Networks, Inc. All rights reserved.

16. New Programmable Interfaces For SDN: OpenFlow
OpenFlow 1.0 API XMOD; Hybrid Support
OpenFlow controller redundancy; Out-of-band management port
Flow Table
Match Condition
Match Action
Counters
Ingress Port
VLAN ID & Priority SA DA
Type
Ethernet
Proto IP
SRC
DST
TCP
Actions
Forward Out-port/Enqueue/Controller
Drop: Drop a packet (Security)
Modify a packet (Source/Destination MAC, VLAN ID)
Counters
Per Table
Per flow
Per port

17. 22 April 2017
Flow Entry Actions
Forward: forward packet to the following physical or virtual ports:
Output port: forward to a specified physical output port
ALL: forward to all ports, excluding the incoming port
CONTROLLER: encapsulate packet (Packet-In message) and send it to the controller
LOCAL: forward via the switch’s local networking stack
TABLE: perform actions in the flow table (for Packet-Out messages only)
IN_PORT: forward the packet back out of the incoming port
NORMAL (optional): forward according to the traditional forwarding path (e.g., generated by STP + learning)
FLOOD (optional): flood the packet along the minimum spanning tree, excluding the incoming port
Drop: drop the packet
Enqueue (optional): enqueue the packet in a specified output port queue.
Modify-Field (optional): modify a header field 17
© 2011 Extreme Networks, Inc. All rights reserved.

18. Flow Entry Modify Actions
22 April 2017
Flow Entry Modify Actions
Set VLAN ID
Set VLAN Priority
Strip VLAN header
Modify Ethernet MAC SA
Modify Ethernet MAC DA
Modify IPv4 SA (and update IPv4/TCP/UDP checksum)
Modify IPv4 DA (and update IPv4/TCP/UDP checksum)
Modify IPv4 ToS (DSCP)
Modify TCP/UDP source port
Modify TCP/UDP destination port
© 2011 Extreme Networks, Inc. All rights reserved.

19. OpenFlow Startup Example
OpenFlow Controller
Switch connects to controller. Both exchange Hello’s. Version negotiation.
Controller requests features with Features-Request.
Switch responds with Features-Reply to indicate supported features and OpenFlow-enabled ports.

20. Topology OpenFlow Application Example
OpenFlow Controller
Switch and controller startup already complete.
Packet-Out LLDP Request
Packet-Out LLDP Request
Packet-Out LLDP Request A
Controller discovers topology of the network by forwarding LLDP’s out to the switching and inspecting the replies. B

21. Topology OpenFlow Application Example
OpenFlow Controller
Packet-In LLDP Request
Packet-In LLDP Request
Packet-In LLDP Request A
Each switch forwards the LLDP’s out the indicated ports.
Each switch forwards the LLDP’s to the controller as Packet-in’s.
Controller now knows the network topology. B

22. Reactive OpenFlow Application Example
OpenFlow Controller
Packet-In ARP Request
Packet-Out ARP Request
ARP Request
ARP Request
ARP Request A
System A needs to communicate with B.
No path exists.
OpenFlow controller reactively establishes path through the switching network. B

23. Reactive OpenFlow Application Example
OpenFlow Controller
Packet-In ARP Reply
ARP Reply A B

24. Reactive OpenFlow Application Example
OpenFlow Controller
Flow-Mod Add
Flow-Mod Add
Flow-Mod Add A B

25. Reactive OpenFlow Application Example
OpenFlow Controller
Packet-Out ARP Reply
ARP Reply
IP Packet A B

26. Extreme Networks SDN Controlled Fabric in action
SDN Community Portal – XKIT
Crowdsourcing, Network Applications store
Open Multi-vendor Approach
BigSwitch, NEC, Floodlight Controller etc.
Extending SDN with OpenStack
Network-as-a-service, Quantum Plugin
Enabling SDN with OpenFlow
OpenFlow 1.0 API, XMOD, Hybrid Support

27. Key SDN OpenFlow Features in EXOS
Open vSwitch (OVS) based OpenFlow
Robust implementation based on OVS Long Term Support (LTS)
Advanced Traffic Management
Traffic distributed using LAG hashing
Queuing support based on EXOS profiles
Multiple Tables for Deployment Flexibility
FDB based flows for simple L2 flows – Higher Scale
ACL based flows for complex match & set conditions
Multiple VLANs with Edit actions
Simple OF based routing between VLANs
Support Applications requiring control of multiple VLANs
MAC Address Rewrite
Rewrite source and destination MAC
Support L3 SDN applications requiring MAC rewrite

28. EXOS SDN Differentiation: Advanced Traffic Management
QP 0
QP 1
OF Controller
QP 2
Ports in LAG Group
WDRR
QP 3
Output traffic to port 1
QP 4 1
QP 5
Switch Fabric/OF Logic
QP 6 2
LAG Hashing function
QP 7
Ingress Traffic 3 4
OpenFlow traffic distributed using LAG hashing function, instead of one port
OpenFlow traffic distributed through different QoS Profiles on egress port

29. SDN OpenFlow: Deployment Flexibility with Unified Forwarding Table
L2 MAC
L3 IPv4/v6
IP Multicast
ACL/Flow
Legacy
Unified Forwarding Table (UFT)
Optimal Table Utilization
SDN Deployment Profiles
L2/L3 Balanced
L3 Heavy
Flow/ACL Heavy

30. SDN OpenFlow: Multiple Tables for Deployment Flexibility
OpenFlow needs flow oriented architecture scaling requirements
L2 MAC
FDB Tables can be used for macro flows that doesn’t need finer-granular traffic control
L3 IPv4/v6
LPM Tables can be used for some complex flows involving IP address match conditions
ACL/Flow
ACL Tables can be used for micro flows that requires finer granular control of traffic with complex match and set conditions
OpenFlow abstracts all these tables into one table. From controller’s perspective, OpenFlow behaves as if there is a single table

31. X-Kit: Application Portal
Crowd-Sourced Knowledge Base for SDN Applications

32. SDN Differentiations Hardware Link Aggregation Hybrid Mode Support
Extreme Networks has specific capabilities that provide clear differentiation among competition. Shipping TODAY !
Hardware Link Aggregation
EXOS represents the LAG as a single virtual interface to the OpenFlow controller enabling bandwidth scaling, load balancing and link redundancy
Hybrid Mode Support
Standard Ethernet switching and OpenFlow based forwarding on a “per-vlan” basis.
Hardware Quality of Service
Configured profile queues are reported to the OpenFlow controller, enabling flows to be programmed directly to hardware queues.
Automated Flow Management
EXOS intelligently classifies and maps flows to hardware resources, both the ACL and FDB tables, allowing up to 100,000 flows per switch.

33. Extreme Networks Products & SDN Support
Campus Enterprise
Data Center
15.3
N/S
N/S
15.4
15.3
Summit X350
Summit X450a/e
Summit X670
N/S
Summit X480
N/S
15.3
15.3
Summit X650
BlackDiamond X8
Summit X250e
Summit X440
N/S
Future
Summit X460
15.4
Summit X150
Future
WM3xxx
Future
Mobile Backhaul
15.4
BlackDiamond 8800
Altitude 45xx/46xx/47xx
Altitude 4511
E4G-200
E4G-400
N/S: Not Supported 33

34. SDN Technology Leadership Continues….
OpenFlow Rel. 2 with Open vSwitch extensions
Openstack Rel. 2
Extreme starts discussions with Big Switch
Extreme demos OpenFlow switch at INTEROP 2011
Extreme demo OpenFlow at ONS
Extreme demo OpenFlow at Interop 2012
2010
2011
2012
2013
Extreme XOS supports Stanford software implementation of OpenFlow 1.0
OpenFlow & Openstack GA in Extreme’s Open Fabric 1QCY2013
Extreme XOS OpenFlow distributed to over 20 customers
OpenFlow Rel. 1 with Open vSwitch extensions
Openstack Rel. 1
Extreme enters partnering discussions with controller vendors (BigSwitch, Nicira etc.)

35. Merge to Mainstream EXOS
OpenFlow Implementation Plan-of-Record* *FUTURE AVAILABILITY – PRODUCTS AND FEATURES SUBJECT TO CHANGE
SDN Rel1.1*
FDB based flows for increased scale
VLAN modification (Edit)
SDN Rel1.2*
Multiple OpenFlow VLANs
Source MAC modification
MediLight SDN Applications
SDN Rel2.1*
Support for OF 1.3
Open Controller Strategy
Intermediate
Releases
Feb’13
Apr’13
Jun’13
Dec’13
Feb’14
EXOS 15.4*
SDN Rel2.0*
All previous features merged into Mainline Releases
FDB based flows for increased scale
VLAN modification (Edit)
Multiple OpenFlow VLANs
Enhanced ACL flow performance
Source MAC modification
EXOS 15.3
SDN Rel1.0
Open Virtual Switch (OVS) based on OpenFlow 1.0 XMOD
ACL Based Flows
Redundant Controller Support
Multiple Actions per Flow
OpenFlow QOS Support using EXOS QOS Profiles
Platform Support: X440, X460, X480, X670
Integration with BigSwitch, NEC & Floodlight Controllers
Merge to Mainstream EXOS

36. Merge to Mainstream EXOS
OpenStack Implementation Plan-of-Record* *FUTURE AVAILABILITY – PRODUCTS AND FEATURES SUBJECT TO CHANGE
DROP 1
HA on management ports
Porting to Grizzly
Provider Network Extension API
DROP 2
VR Insertion API
SR-IOV Data Model
DROP 3
API for Router Configuration
DROP 4
QoS Rate limiting per Quantum port Profile Management.
Intermediate
Releases to
Feb’13
Aug’13
Oct’13
Nov’13
Dec’13
Feb’14
SDN 1.0
OpenStack Release 1.0
Quantum based on Folsom
Topology Aware Scheduler
VLAN & VMAN configuration through API for Multi-tenancy
Live VM Migration
SDN 2.0*
Openstack Release 2.0
All features from intermediate drops merged
Merge to Mainstream EXOS

37. Controller & Applications

38. Multi-Vendor Interoperability & Applications with OpenFlow
Future Support
Big Switch
Floodlight
NEC
VMware ……
App
App
App
App
Applications
Controller Platform
Controller tier
OpenFlow API
Switch
Switch
Switch
Switch
Data plane tier
Switch

39. Big Network Controller mit Hyperglance

40. Big Network Controller mit Hyperglance

41. Floodlight Dashboard

42. Floodlight Topology View

43. Floodlight Switchview Detail

44. Floodlight Switchview

45. Software-Defined Networking: Myths vs. Reality
“We’ve been doing SDN with scripts for years…”
There has been a trend toward central controllers, but a programmable dataplane is different from configuration automation
“OpenFlow can’t scale”
Google’s entire datacenter backbone runs on OpenFlow 1.0
“SDN/OpenFlow deployment is rip-and-replace ”
All our current deployments have SDN/OpenFlow interoperating with existing networks
“SDN is just a research topic”
Seeing real production deployments for early adopters, moving to early majority
“OpenFlow can (can’t) solve any real-world network problem”
OpenFlow is at version 1.0 and can solve a few problems well, but is expanding
Key point: it is a *control* (not a data) protocol
“SDN == OpenFlow”
OpenFlow is an open, standard protocol between the control & data planes in an SDN architecture
“SDN == Network Virtualization”
Network Virtualization is an important, key application for SDN, but others are possible

46. Architectural Disruptions
Open architectures bring waves of innovation
Open
Architectures
Linux OS
X86 Architecture
Disruption
Both the compute and mobile industry went through a transition from closed architectures to open architectures, and opened the door to a wave of innovation.
Compute went from a closed proprietary Big Iron world – to a more open yet still closed world of smaller systems, SPARC & Power, running closed systems like Solaris & AIX.
Then the Intel moved the market with cheaper and faster chips. Linux came along….
On top of that this entire ecosystem evolved based around Open Standards.
We ended up with amazing transformation we see today of larger scale compute and services available of the smallest companies – the startups of tomorrow.
It changed the world. There would be no Google, no Yahoo, no Facebook, no Amazon with out this move Open SW and HW. The result - unlocked customer value.
In Mobile we had a close world. HW companies made phones. The applications on those phones were dictated by the Mobile provider….and lets face it – they were terrible.
They Apple comes along and destroys the mobile providers neat little world. No you cannot install your crap-ware and also we are going to open our API’s so software can be developed that people really want to use.
Google went even further - Hey guys – here’s Android – have fun.
Think about it. How many companies have been created, how many new ideas have been expressed because Apple and Google understood that letting someone create Angry Birds was a good thing.
Korea’s own Samsung has benefited highly from Android and the eco system built around it. The result - unlocked customer value.
Then we come to networks. Let’s see – we have a picture of a Cisco How many applications have been written for that – outside of Cisco?
Want a firewall on it? Write a check to Cisco. Who care if it does not do what you want and what you really need something provided my the likes of Palo Alto network.
Sure you can put the Palo Alto in line, but that is just not the same as having it intergraded into the network core now is it? The close network dictates inflexibility.
So Compute, Mobile, they have changed. You can drive your servers harder with virtualization in order to move even more applications to the open mobile platforms faster.
However those packet still travel of that closed locked in inflexible world of close networking.
At Big Switch Networks we believe the change in networking is happing now. The same change that happen to compute and mobile is at this very minute has started to crack networking. All thanks to Open SDN.
Closed,
Proprietary
Systems
Compute
Mobile
Networking

47. Looking to the Future of SDN and OpenFlow
OpenFlow becomes the Android of networking
Open network OS and controller for Ethernet switches and routers
OpenFlow and related specifications all available as Open Source
Apps for every need
From QoS, to PBR, to Identity Management, to Mobility Management, to multi-tenancy and so on
Controller vendors eventually become application developers
Apps come in free, premium, and freemium models
Switch vendors continue to build and sell switches
Much like phone vendors continue to sell phones
App Stores and Marketplaces for OpenFlow and SDN Apps
© 2011 Extreme Networks, Inc. All rights reserved.

48. And the Hardware......?

49. .....still matters!

50. THANK YOU Extreme Networks Confidential and Proprietary.
© 2010 Extreme Networks, Inc. All rights reserved.