+ All Categories
Home > Documents > Brief Production-ready SDN with OpenFlow 1 - CNET...

Brief Production-ready SDN with OpenFlow 1 - CNET...

Date post: 22-Mar-2018
Category:
Upload: doancong
View: 230 times
Download: 7 times
Share this document with a friend
2
Brief Production-ready SDN with OpenFlow 1.3 OpenFlow is the industry’s only standards-based protocol to implement SDN What is OpenFlow? OpenFlow provides programmatic access to the data plane. It does this by providing a forwarding abstraction and a wire protocol that is used to communicate with an SDN controller. Development of OpenFlow began in 2007, led by Stanford University in collaboration with HP, and its 1.0 release was published in 2009. The standardization of OpenFlow transitioned from the academic community to the Open Networking Foundation (ONF) in 2011. HP, one of the ONF’s founding members, along with the other 90+ member companies, have driven the development of OpenFlow through three major iterations. This paper outlines how OpenFlow 1.3 enables production-ready SDN, and why this matters to you. Essential enhancements for production networks The OpenFlow 1.3 specification was released by the ONF in September 2012 with the goal of enabling widespread adoption. This milestone release boasts significant enhancements to capabilities for enabling production deployments, including enhancements from previous 1.1 and 1.2 specifications that were not widely implemented by equipment vendors. Let’s evaluate some of the key features that are required for production-ready SDN. OpenFlow 1.1 Multiple tables OpenFlow 1.0 originally supported a single logical table for implementing flow rules. This limited the full utilization of hardware ASIC capabilities. With multiple tables, OpenFlow can now take advantage of the unique characteristics of each hardware table to increase performance and scalability. Groups With the addition of groups, OpenFlow can create group of ports, similar to link aggregation in legacy networks. This can be used for multipathing or redundancy. MPLS and VLAN tag support OpenFlow originally supported VLANs in a limited fashion. With this enhancement OpenFlow now has robust support for VLANs, QinQ, and MPLS tags. These capabilities provide additional flexibility in programming the forwarding plane with rules that can match against more information contained in Ethernet packets. Virtual ports Virtual ports extend OpenFlow beyond physical ports. The concept of virtual ports, or logical ports, enables OpenFlow to be used across LAGs or tunnels. This enables OpenFlow to be used to implement network virtualization for multi-tenancy at scale. Controller connection failure On losing connection with the controller, OpenFlow 1.0 offered an emergency flow cache which, in practice, was difficult to implement. The latest version of the specification adds two simpler modes to deal with the loss of connectivity with the controller. In fail secure mode, the switch continues operating in OpenFlow mode until it reconnects to a controller. In fail standalone mode the switch reverts to using normal processing (Ethernet switching). HP is leading the industry by enabling OpenFlow across its portfolio Now with over 40 switch models supporting OpenFlow, representing more than 20 million ports in the market, HP continues to lead in OpenFlow enablement. HP is the only vendor to offer a full portfolio of enterprise data center and campus switches that are SDN-ready with OpenFlow support. HP’s OpenFlow leadership 2007 – HP & Stanford collaborate 2008 – HP demos OpenFlow switch 2009 – HP earns 10 lighthouse customers 2010 – HP scales to 60 customers 2011 – HP delivers OpenFlow 1.0 on 16 switches 2012 – HP develops lighthouse SDN customers, and delivers an SDN controller and application • 2013 – HP expands OpenFlow support to over 40 switches and delivers OpenFlow 1.3 Million enabled ports 20 Switch models 40
Transcript
Page 1: Brief Production-ready SDN with OpenFlow 1 - CNET …cdn.cnetcontent.com/4a/2a/4a2acafe-a902-4fe3-8700-732d2056a955.pdf · Brief Production-ready SDN with OpenFlow 1.3 OpenFlow is

Brief

Production-ready SDN with OpenFlow 13OpenFlow is the industryrsquos only standards-based protocol to implement SDN

What is OpenFlow

OpenFlow provides programmatic access to the data plane It does this by providing a forwarding abstraction and a wire protocol that is used to communicate with an SDN controller Development of OpenFlow began in 2007 led by Stanford University in collaboration with HP and its 10 release was published in 2009 The standardization of OpenFlow transitioned from the academic community to the Open Networking Foundation (ONF) in 2011 HP one of the ONFrsquos founding members along with the other 90+ member companies have driven the development of OpenFlow through three major iterations This paper outlines how OpenFlow 13 enables production-ready SDN and why this matters to you

Essential enhancements for production networksThe OpenFlow 13 specification was released by the ONF in September 2012 with the goal of enabling widespread adoption This milestone release boasts significant enhancements to capabilities for enabling production deployments including enhancements from previous 11 and 12 specifications that were not widely implemented by equipment vendors Letrsquos evaluate some of the key features that are required for production-ready SDN

OpenFlow 11

Multiple tablesOpenFlow 10 originally supported a single logical table for implementing flow rules This limited the full utilization of hardware ASIC capabilities With multiple tables OpenFlow can now take advantage of the unique characteristics of each hardware table to increase performance and scalability

GroupsWith the addition of groups OpenFlow can create group of ports similar to link aggregation in legacy networks This can be used for multipathing or redundancy

MPLS and VLAN tag supportOpenFlow originally supported VLANs in a limited fashion With this enhancement OpenFlow now has robust support for VLANs QinQ and MPLS tags These capabilities provide additional flexibility in programming the forwarding plane with rules that can match against more information contained in Ethernet packets

Virtual portsVirtual ports extend OpenFlow beyond physical ports The concept of virtual ports or logical ports enables OpenFlow to be used across LAGs or tunnels This enables OpenFlow to be used to implement network virtualization for multi-tenancy at scale

Controller connection failureOn losing connection with the controller OpenFlow 10 offered an emergency flow cache which in practice was difficult to implement The latest version of the specification adds two simpler modes to deal with the loss of connectivity with the controller In fail secure mode the switch continues operating in OpenFlow mode until it reconnects to a controller In fail standalone mode the switch reverts to using normal processing (Ethernet switching)

HP is leading the industry by enabling OpenFlow across its portfolio

Now with over 40 switch models supporting OpenFlow representing more than 20 million ports in the market HP continues to lead in OpenFlow enablement HP is the only vendor to offer a full portfolio of enterprise data center and campus switches that are SDN-ready with OpenFlow support

HPrsquos OpenFlow leadership

bull 2007 ndash HP amp Stanford collaborate

bull 2008 ndash HP demos OpenFlow switch

bull 2009 ndash HP earns 10 lighthouse customers

bull 2010 ndash HP scales to 60 customers

bull 2011 ndash HP delivers OpenFlow 10 on 16 switches

bull 2012 ndash HP develops lighthouse SDN customers and delivers an SDN controller and application

bull 2013 ndash HP expands OpenFlow support to over 40 switches and delivers OpenFlow 13

Million enabledports 20

Switch models40

Rate this documentShare with colleagues

Sign up for updates hpcomgogetupdated

Brief | SDN with OpenFlow 13

OpenFlow 12

Extensible match supportOpenFlow 12 enables a flexible expression of match criteria and the inclusion of new match fields by replacing the static fixed length match structure with a new TLV-based structure called OpenFlow Extensible Match (OXM) which dramatically increases flexibility

Basic IPv6 support OpenFlow 12 provides basic support for IPv6 using the OXM

Controller role-change mechanismThis is a simple mechanism that allows the switch to be aware of a controllerrsquos role allowing failover from a primary to a secondary controller for example

OpenFlow 13

Expanded IPv6 supportThe IPv6 support in OpenFlow 13 has been expanded to cover IPv6 extension headers using the OXM

Per-flow metersOpenFlow 13 brings support for per-flow meters These can be attached to flow entries and can measure and control the rate of packets One of the main applications of per-flow meters is to rate limit packets sent to the controller

Provider Backbone Bridging taggingOpenFlow now supports matches and actions for Provider Backbone Bridging tags This allows an OpenFlow network to be multi-tenant aware while also enabling hybrid cloud environments

Tunnel-ID metadataThe tunnel-ID metadata is a new OXM field that exposes the OpenFlow processing pipeline to metadata from a logical tunnel port This metadata can be used to specify encapsulation and decapsulation of packets

How to get started

With the release and commercialization of OpenFlow 13 on several HP switch platforms you can now start deploying production SDN-ready infrastructure and begin the journey to software-defined networking HP has outlined key steps to help you embark on your journey

Now is the time to get started with SDN and HP makes it easy with its broad support for OpenFlow via free software upgrades HP is the first company to offer OpenFlow 13 support on a mainstream platformmdashthe HP 5900 Seriesmdashand HP customers using OpenFlow 10 today can upgrade to 13 as it is made available across the portfolio with no additional licensing or costs

Learn more at hpcomnetworking

Capability 11 12 13

Multiple tables X

Groups X

Tags MPLS amp VLAN X

Virtual ports X

Controller connection failure

X

Extensible match support X

Basic IPv6 support X

Controller role-change mechanism

X

Per-flow meters X

Provider Backbone Bridging tagging

X

Tunnel-ID metadata X

Expanded IPv6 support X

copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein

4AA4-6562ENW May 2013

Figure 1 Getting started with SDN

OpenFlow version history

Deploy SDN enterprise-wide

Develop SDN application using RESTful APIs

Test and deploy more HP and partner SDN applications

Deploy SDN controller and Sentinel virtual cloud network apps

Create a lab participate in HP SDN controller and application beta

Lay the foundation deploy FlexNetwork OpenFlow-enabled switches

2015

2014

1H14

2H13

1H13

Now

Page 2: Brief Production-ready SDN with OpenFlow 1 - CNET …cdn.cnetcontent.com/4a/2a/4a2acafe-a902-4fe3-8700-732d2056a955.pdf · Brief Production-ready SDN with OpenFlow 1.3 OpenFlow is

Rate this documentShare with colleagues

Sign up for updates hpcomgogetupdated

Brief | SDN with OpenFlow 13

OpenFlow 12

Extensible match supportOpenFlow 12 enables a flexible expression of match criteria and the inclusion of new match fields by replacing the static fixed length match structure with a new TLV-based structure called OpenFlow Extensible Match (OXM) which dramatically increases flexibility

Basic IPv6 support OpenFlow 12 provides basic support for IPv6 using the OXM

Controller role-change mechanismThis is a simple mechanism that allows the switch to be aware of a controllerrsquos role allowing failover from a primary to a secondary controller for example

OpenFlow 13

Expanded IPv6 supportThe IPv6 support in OpenFlow 13 has been expanded to cover IPv6 extension headers using the OXM

Per-flow metersOpenFlow 13 brings support for per-flow meters These can be attached to flow entries and can measure and control the rate of packets One of the main applications of per-flow meters is to rate limit packets sent to the controller

Provider Backbone Bridging taggingOpenFlow now supports matches and actions for Provider Backbone Bridging tags This allows an OpenFlow network to be multi-tenant aware while also enabling hybrid cloud environments

Tunnel-ID metadataThe tunnel-ID metadata is a new OXM field that exposes the OpenFlow processing pipeline to metadata from a logical tunnel port This metadata can be used to specify encapsulation and decapsulation of packets

How to get started

With the release and commercialization of OpenFlow 13 on several HP switch platforms you can now start deploying production SDN-ready infrastructure and begin the journey to software-defined networking HP has outlined key steps to help you embark on your journey

Now is the time to get started with SDN and HP makes it easy with its broad support for OpenFlow via free software upgrades HP is the first company to offer OpenFlow 13 support on a mainstream platformmdashthe HP 5900 Seriesmdashand HP customers using OpenFlow 10 today can upgrade to 13 as it is made available across the portfolio with no additional licensing or costs

Learn more at hpcomnetworking

Capability 11 12 13

Multiple tables X

Groups X

Tags MPLS amp VLAN X

Virtual ports X

Controller connection failure

X

Extensible match support X

Basic IPv6 support X

Controller role-change mechanism

X

Per-flow meters X

Provider Backbone Bridging tagging

X

Tunnel-ID metadata X

Expanded IPv6 support X

copy Copyright 2013 Hewlett-Packard Development Company LP The information contained herein is subject to change without notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein

4AA4-6562ENW May 2013

Figure 1 Getting started with SDN

OpenFlow version history

Deploy SDN enterprise-wide

Develop SDN application using RESTful APIs

Test and deploy more HP and partner SDN applications

Deploy SDN controller and Sentinel virtual cloud network apps

Create a lab participate in HP SDN controller and application beta

Lay the foundation deploy FlexNetwork OpenFlow-enabled switches

2015

2014

1H14

2H13

1H13

Now


Recommended