Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Stackwise agent-based mechanism for SDN smooth transition

IP.com Disclosure Number: IPCOM000238041D
Publication Date: 2014-Jul-29
Document File: 6 page(s) / 144K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention targets to fully reuse the stacking topologies and its technologies in an OpenFlow enabled networking environment, with our invention, the stacking topology is maintained and part of the stacking unique features and the benefits will be inherited when enabling OpenFlow.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 43% of the total text.

Page 01 of 6

Stackwise agent

Stackwise agent-

based mechanism for SDN smooth transition

With our invention, when enable OpenFlow in an stacking environment, Only the master switch connects with the controller and it behaves as an agent for all member switches. The master switch is responsible for processing the requests from the controller and reply it on behalf of all members. The advantages of our solution are listed as below:
1. No damage to the original topologies and no additional cabling except the connection between controller and master switch.

2. Controller only needs to manage the connections and exchange the message with the master switch.

3. Controller simplifies the route computing because all the stacking switches will be handled as an logical node.

4. The running traffic can be maintained and not be impacted during the OpenFlow deployment. Under hybrid mode, the active ports can carry the existing traffic and be assigned to non-OpenFlow ports.

5. The benefits of stacking can be inherited, for example, FDB synchronization between all stackable switches can facilitate forwarding the known packets in all stacking ports without the controller's interaction.

Known solution:


Usually OpenFlow is enabled in a Data Center, the original design and topologies might not be reused or adopted directly. Take the example shown as Fig.1, stacking topologies cannot be maintained and the traditional stacking features have to be disabled once they connect to the controller. Correspondingly, the benefits of stacking will be lost. More specifically, it has the below drawbacks:
1. The particular stacking topology cannot be reused, moreover, the special switching stack interconnect might be useless for some vendors if the switches

come with built-in ports dedicated for stacking.

2. All the benefits of stackable switch will be lost, for example, link aggregation of ports on different units in the stack, stacking resiliency via bypassing a "down" switch in a stack, etc.


3. Additional cabling is needed to connect all the switches belong to the same stack logical unit to the OpenFlow controller.


4. The running traffic will be interrupted because it depends on the stacking topologies and its technologies.

1

--based mechanism for SDN smooth transition



Page 02 of 6

 OpenFlow Controller

OpenFlo

N

w Management

etwork

Fig.1 StackBlind OpenFlow Topology

With our invention, the stacking topology is maintained and part of the stacking unique features and the benefits will be inherited when enabling OpenFlow. As shown in Fig.2, only the master switch connects with the controller and it behaves as an agent for all member switches. The master switch is responsible for processing the requests from the controller and reply it on behalf of all members. The advantages of our solution are listed as below: 1. No damage to the original topologies and no additional cabling except the connection between controller and master switch.

2. Controller only needs to manage the connect...