29.01.2015 Views

OpenFlow and SDNS - Extreme Networks

OpenFlow and SDNS - Extreme Networks

OpenFlow and SDNS - Extreme Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Extreme</strong> <strong>Networks</strong> White Paper<br />

<strong>OpenFlow</strong> <strong>and</strong> SDNs<br />

Abstract<br />

<strong>OpenFlow</strong> is a new protocol designed to control flow<br />

tables in Ethernet switches. <strong>OpenFlow</strong> is implemented<br />

on an Ethernet switch controller, using an internal flowtable<br />

<strong>and</strong> a st<strong>and</strong>ardized interface to add <strong>and</strong> remove<br />

flow entries. <strong>OpenFlow</strong> enables Software Defined<br />

<strong>Networks</strong> (SDNs) which utilize abstractions in an effort<br />

to simplify networks for designers <strong>and</strong> operators.<br />

The Open Network Foundation (ONF) has formed<br />

to accelerate <strong>and</strong> define the use of SDNs. <strong>Extreme</strong><br />

<strong>Networks</strong> is an ONF Member <strong>and</strong> is participating in the<br />

future definition of <strong>OpenFlow</strong> <strong>and</strong> is actively involved<br />

in interoperability testing in <strong>OpenFlow</strong> labs. This white<br />

paper provides an overview of <strong>OpenFlow</strong>, SDNs <strong>and</strong><br />

<strong>Extreme</strong> <strong>Networks</strong> participation <strong>and</strong> involvement in the<br />

direction of the <strong>OpenFlow</strong> st<strong>and</strong>ard.<br />

Make Your Network Mobile<br />

© 2012 <strong>Extreme</strong> <strong>Networks</strong>, Inc. All rights reserved.


<strong>Extreme</strong> <strong>Networks</strong> White Paper: <strong>OpenFlow</strong> <strong>and</strong> SDNs<br />

Executive Overview<br />

<strong>OpenFlow</strong> is a new protocol implemented on<br />

an Ethernet switch that allows its forwarding<br />

plane to be managed by an external <strong>OpenFlow</strong><br />

controller. An <strong>OpenFlow</strong> controller can manage<br />

a distributed set of network switches as a single<br />

virtual switch. As most <strong>OpenFlow</strong> controllers<br />

expose an API to applications, the controller<br />

<strong>and</strong> applications together behave as a unified<br />

Network OS, allowing a network operator to<br />

implement a Software Defined Network (SDN).<br />

<strong>OpenFlow</strong> Overview<br />

The <strong>OpenFlow</strong> protocol emerged from the Clean Slate<br />

research program at Stanford University. The objective<br />

was to enable researchers to experiment with new<br />

networking protocols <strong>and</strong> applications. Instead of<br />

porting each new protocol/application to switches,<br />

each br<strong>and</strong> with its own proprietary OS, the researchers<br />

need only port an <strong>OpenFlow</strong> protocol client, exposing<br />

the switch’s forwarding plane. The experimental control<br />

component could then be implemented on a st<strong>and</strong>ard<br />

PC running a Unix OS (such as Linux).<br />

This approach proved popular, <strong>and</strong> <strong>OpenFlow</strong> was<br />

adopted as a core component by university researchers<br />

participating in NSF GENI- <strong>and</strong> EU OPHELIA-funded<br />

research projects. <strong>OpenFlow</strong> protocol definition was<br />

opened to a group of interested researchers <strong>and</strong><br />

networking vendors meeting periodically at Stanford,<br />

<strong>and</strong> via e-mail lists. <strong>OpenFlow</strong> version 1.0.0 was<br />

published in December 2009, <strong>and</strong> version 1.1 was<br />

published in February 2011. Multiple vendors, including<br />

<strong>Extreme</strong> <strong>Networks</strong>, have implemented <strong>OpenFlow</strong><br />

1.0 prototypes. Some of these prototypes were<br />

demonstrated at the Interop <strong>OpenFlow</strong> Interoperability<br />

Lab, in May 2011.<br />

<strong>OpenFlow</strong> exposes a switch’s forwarding plane as a<br />

set of Ethernet ports, flow tables, counters, queues,<br />

<strong>and</strong> capabilities. A flow table entry consists of a set of<br />

L2/L3/L4 match conditions, which may be variously<br />

wildcarded or masked. Associated with each flow table<br />

rule is a set of one or more actions, including Forwarding<br />

(to a physical or virtual port, to the controller, or<br />

flooded), Enqueueing, <strong>and</strong> Packet Modification. Added<br />

in <strong>OpenFlow</strong> 1.1 are support for multiple cascaded<br />

flow tables <strong>and</strong> MPLS label-related actions. By default,<br />

packets arriving at an <strong>OpenFlow</strong>-managed port which<br />

do not match a flow entry are encapsulated <strong>and</strong> sent<br />

to the controller, which as a result may send a flow<br />

installation comm<strong>and</strong> to the switch <strong>and</strong> return the<br />

packet back to the switch for forwarding.<br />

The wide generality of the <strong>OpenFlow</strong> flow match<br />

conditions allows a controller to manage forwarding<br />

at L2, L3, <strong>and</strong>/or L4 layers, either in isolation, or<br />

in combination. This enables a SDN with multiple<br />

virtualized network topologies. As a simple example, a<br />

controller can configure forwarding for UDP traffic on a<br />

special restricted topology, with guaranteed b<strong>and</strong>width<br />

allocated to dedicated queues used exclusively for<br />

UDP traffic.<br />

Industry Direction<br />

In March 2011, the Open Networking Foundation (ONF)<br />

was formed to advance the adoption of SDNs. ONF<br />

will manage future evolution <strong>and</strong> specification of the<br />

<strong>OpenFlow</strong> protocol, <strong>and</strong> may also define st<strong>and</strong>ard<br />

APIs to the <strong>OpenFlow</strong> controller, to allow for portable<br />

SDN applications. The board members are Deutsche<br />

Telekom, Verizon, Google, Facebook, Microsoft, NTT<br />

Communications, <strong>and</strong> Yahoo. ONF currently has 54<br />

additional members, including <strong>Extreme</strong> <strong>Networks</strong>. See<br />

http://www.opennetworkingfoundation.org/<br />

for more information.<br />

ONF published the <strong>OpenFlow</strong> 1.2 specification in<br />

December 2011. It also published the first version of<br />

the <strong>OpenFlow</strong> Configuration protocol, OF-Config 1.0,<br />

in January 2012. ONF working groups are currently<br />

working on new revisions of each specification, as well<br />

as defining the requirements for hybrid <strong>OpenFlow</strong><br />

switches, <strong>and</strong> defining the long-term structure <strong>and</strong><br />

evolution of the <strong>OpenFlow</strong> protocol.<br />

2<br />

© 2012 <strong>Extreme</strong> <strong>Networks</strong>, Inc. All rights reserved.


<strong>Extreme</strong> <strong>Networks</strong> White Paper: <strong>OpenFlow</strong> <strong>and</strong> SDNs<br />

Multiple vendors have implemented prototypes of<br />

<strong>OpenFlow</strong> 1.0, <strong>and</strong> a few have released generally<br />

available implementations. It is unclear whether<br />

<strong>OpenFlow</strong> 1.1 will be widely implemented; it is likely that<br />

most vendors will wait to refresh their implementations<br />

to <strong>OpenFlow</strong> 1.3 or later versions.<br />

The commercial l<strong>and</strong>scape for SDNs includes not<br />

only switch vendors, but also controller vendors. The<br />

original controllers (Stanford, NOX, Beacon, SNAC) were<br />

developed by researchers <strong>and</strong> released as open source.<br />

NEC has announced a commercial controller, <strong>and</strong> two<br />

startup companies (Big Switch, Nicira), that spun out<br />

of the Stanford research team, are building commercial<br />

<strong>OpenFlow</strong> controllers, <strong>and</strong> have recently received<br />

venture capital funding.<br />

Initial SDN applications which have attracted interest<br />

in the campus, enterprise, <strong>and</strong> data center markets<br />

include multi-path support (to avoid the capacity loss<br />

<strong>and</strong> instability caused by STP <strong>and</strong> its failures), simplified<br />

administration of add/move changes (via managing<br />

the network as a single virtual switch), VM mobility<br />

<strong>and</strong> multi-tenancy (for hosting/cloud providers). SDN<br />

applications for the WAN including transport path<br />

provisioning <strong>and</strong> routing.<br />

<strong>Extreme</strong> <strong>Networks</strong> Opportunities<br />

<strong>Extreme</strong> <strong>Networks</strong> initiated development of <strong>OpenFlow</strong><br />

support in <strong>Extreme</strong>XOS® based in part on requests from<br />

various university customers involved in GENI- <strong>and</strong><br />

OPHELIA-funded research projects. In the subsequent<br />

year dem<strong>and</strong> for <strong>OpenFlow</strong> from university customers<br />

has exp<strong>and</strong>ed beyond the research lab into the<br />

production campus network. <strong>Extreme</strong> <strong>Networks</strong> is<br />

working with a major university customer to trial SDN<br />

applications within its campus network.<br />

<strong>Extreme</strong> <strong>Networks</strong> is also exploring opportunities with<br />

partners to deploy SDN applications in the enterprise<br />

campus <strong>and</strong> datacenter network environments. An<br />

SDN can serve as a platform to deploy a variety of<br />

intelligent network services in a scalable way, because<br />

the network switches are centrally managed by the<br />

<strong>OpenFlow</strong> controller. Of particular value are the network<br />

virtualization capabilities enabled. It becomes easier<br />

to deploy <strong>and</strong> dynamically manage security isolation<br />

between classes of users in university, enterprise<br />

campus or hospital networks, by isolating each class<br />

of user to their own virtual network topology. Unlike<br />

Ethernet VLANs, this isolation can also be enabled at<br />

the L3 <strong>and</strong>/or L4 layers. In a datacenter network, the<br />

network virtualization capabilities enabled by <strong>OpenFlow</strong><br />

can simplify the provisioning of services for individual<br />

tenants, <strong>and</strong> can enable scalable VM migration across<br />

a large datacenter network or between physical<br />

datacenter sites.<br />

<strong>Extreme</strong> <strong>Networks</strong> Involvement<br />

<strong>Extreme</strong> <strong>Networks</strong> participated in the <strong>OpenFlow</strong><br />

interoperability Lab at Interop 2011. <strong>Extreme</strong> <strong>Networks</strong><br />

has also joined the ONF, <strong>and</strong> is participating in the future<br />

definition of the <strong>OpenFlow</strong> protocol. Current plans for<br />

<strong>Extreme</strong> <strong>Networks</strong> <strong>OpenFlow</strong> implementation include<br />

support as part of the <strong>Extreme</strong>XOS network operating<br />

system, across a variety of switching products.<br />

Make Your Network Mobile<br />

Corporate<br />

<strong>and</strong> North America<br />

3585 Monroe Street<br />

Santa Clara, CA 95051<br />

United States<br />

Phone +1 408 579 2800<br />

Europe, Middle East, Africa<br />

<strong>and</strong> South America<br />

Phone +31 30 800 5100<br />

Asia Pacific<br />

Phone +65 6836 5437<br />

Latin America<br />

Phone +52 55 5557 6465<br />

www.extremenetworks.com<br />

© 2012 <strong>Extreme</strong> <strong>Networks</strong>, Inc. All rights reserved. <strong>Extreme</strong> <strong>Networks</strong>, the <strong>Extreme</strong> <strong>Networks</strong> logo, are either registered trademarks or trademarks of<br />

<strong>Extreme</strong> <strong>Networks</strong>, Inc. in the United States <strong>and</strong>/or other countries. All other names <strong>and</strong> marks are the property of their respective owners. Specifications<br />

are subject to change without notice. 1795_02 04/12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!