Browse Prior Art Database

SDN Controller based replication when destination itself is wildcarded Disclosure Number: IPCOM000237817D
Publication Date: 2014-Jul-15
Document File: 3 page(s) / 36K

Publishing Venue

The Prior Art Database


Replication of packets on the network when there are multiple destinations involved is tricky. This can be acheived making using of SDN Controller to decide the destination reactively by looking at the packet-ins and then installing the replication path rules from destination to target.

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

Page 01 of 3

SDN Controller based replication when destination itself is wildcarded

To replicate packets coming from a source to any destination (wild carded), there can be two approaches

Approach-1 : Replicating from source itself proactively

Approach-2 : Replicating from destination reactively
Approach-2 is new proposal and has advantages over Approach-1, if it exists already.

Approach-1 limitations:

1. Rules need to be installed for each and every destination possible proactively 2. Care needs to be taken to install rule in such a way that packet reaches both original destination as well as Replica Target without any loop formation.

Approach-2 will address the limitations of Approach-1.

Approach-2 can be optimized further not to calculate path from destination to replica target everytime and install the rules once only.

The core problem in supporting replication for any of the destinations, isto find the destination for the incoming packet. The way to achieve this is to send the packet to controller using packet_in and then read the destination from the packet. Then install rules for replication directly from that destination to the replica target. This way we can avoid installing rules for all possible destinations. Also the rules to be installed will have the job to just take the packet directly to replica target as the packet already reached the destination.

The rules which are installed can timeout (if the timeout is set) depending on the traffic and everytime the traffic starts the whole process of finding the path and installing rules have to be repeated. Instead we can install rules without timeout. When the replication sess...