ODL behavior when connectivity with HW-VTEP's ovsdb-server goes down and comes back after sometime


Arunkumar R G
 

Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?

Thanks,
Arun.


daya k
 

hi arun,
any time there is a connection flap between ODL and the hwvtep, ODL triggers a re-conciliation mechanism with the device. As part of this re-conciliation mechanism, ucast_macs_local entries are considered to be owned by the device, so ODL will update its entries to what is present in the switch table. ucast_macs_remote entries are owned by ODL, and as such it will update the device table with the latest information.

there is no aging mechanism in ODL for mac entries learnt from the hwvtep, so during the connection down interval, the entries should stay untouched in the controller.

thanks,
daya




From: Arunkumar Rg <arunkumar.rg@...>
To: ovsdb-dev@...
Sent: Thursday, April 13, 2017 12:04 PM
Subject: [ovsdb-dev] ODL behavior when connectivity with HW-VTEP's ovsdb-server goes down and comes back after sometime

Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?

Thanks,
Arun.

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



Anil Vishnoi
 

+ suneel, vishal 

please see inline ..

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?
​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

Thanks,
Arun.


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@....org
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev




--
Thanks
Anil


Arunkumar R G
 

HI Anil,

Thanks for looking into this!

A clarification on your comment:
Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"
Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?

Thanks,
Arun



On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:
+ suneel, vishal 

please see inline ..

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?
​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

Thanks,
Arun.


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...rg
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev




--
Thanks
Anil


Anil Vishnoi
 

Hi Arun,

Please see inline ...

On Fri, Apr 14, 2017 at 7:24 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
HI Anil,

Thanks for looking into this!

A clarification on your comment:
Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"
Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?
​When i say operational state of the device is cleared, i meant the the operational state stored in the controller operational data store and not really the operational state in the device. Once device disconnects from controller, hwvtep will remove the operational data that it learned from device through rpc notifications from it's operational data store , it does not have any way to clear any state in the device itself because it's already disconnected.

Thanks,
Arun



On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:
+ suneel, vishal 

please see inline ..

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?
​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

Thanks,
Arun.


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...rg
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev




--
Thanks
Anil




--
Thanks
Anil


Santosh
 

Hi Anil 
As part of reconciliation does ODL takes care of sending delete request for the Macs( which were removedfrom local ucast table during the period when ODL was  disconnected), from the remote vtep ovsdb store I.e. remote ucast Macs.

Thanks
Santosh

On 17-Apr-2017 1:51 am, "Anil Vishnoi" <vishnoianil@...> wrote:
Hi Arun,

Please see inline ...

On Fri, Apr 14, 2017 at 7:24 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
HI Anil,

Thanks for looking into this!

A clarification on your comment:
Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"
Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?
​When i say operational state of the device is cleared, i meant the the operational state stored in the controller operational data store and not really the operational state in the device. Once device disconnects from controller, hwvtep will remove the operational data that it learned from device through rpc notifications from it's operational data store , it does not have any way to clear any state in the device itself because it's already disconnected.

Thanks,
Arun



On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:
+ suneel, vishal 

please see inline ..

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:
Hi,

Lets say there is a HWVTEP managed by ODL.

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?
​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?
​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

Thanks,
Arun.


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...rg
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev




--
Thanks
Anil




--
Thanks
Anil

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@....org
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Vishal Thapar <vishal.thapar@...>
 

Hi Santosh,

 

You need to clarify what you mean by ODL here. If you mean OVSDB plugin, no it is not responsible for maintaining config DS entries for remote mcast/ucast macs. It is up to the application using the OVSDB/HWVTEP plugin to listen for Local ucast/mcast changes in HWVTEP operational datastore and accordingly add/remove remote ucast/mcast mac entries.

 

If you mean ODL to include applications too, it depends on which application you’re using. If you’re using the new netvirt which has implementation for L2GW, then yes, ODL does take care of update remote ucast/mcast mac entries based on changes on swtiches’ local ucast/mcast mac entries, whether at runtime or through reconciliation on reconnect.

 

Regards,

Vishal.

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Santosh Singh
Sent: 17 April 2017 10:46
To: Anil Vishnoi <vishnoianil@...>
Cc: ovsdb-dev@...; K.V Suneelu Verma <k.v.suneelu.verma@...>
Subject: Re: [ovsdb-dev] ODL behavior when connectivity with HW-VTEP's ovsdb-server goes down and comes back after sometime

 

Hi Anil 

As part of reconciliation does ODL takes care of sending delete request for the Macs( which were removedfrom local ucast table during the period when ODL was  disconnected), from the remote vtep ovsdb store I.e. remote ucast Macs.

 

Thanks

Santosh

 

On 17-Apr-2017 1:51 am, "Anil Vishnoi" <vishnoianil@...> wrote:

Hi Arun,

 

Please see inline ...

 

On Fri, Apr 14, 2017 at 7:24 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

HI Anil,

 

Thanks for looking into this!

 

A clarification on your comment:

Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"

Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?

​When i say operational state of the device is cleared, i meant the the operational state stored in the controller operational data store and not really the operational state in the device. Once device disconnects from controller, hwvtep will remove the operational data that it learned from device through rpc notifications from it's operational data store , it does not have any way to clear any state in the device itself because it's already disconnected.

 

Thanks,

Arun

 

 

 

On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:

+ suneel, vishal 

 

please see inline ..

 

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

Hi,

 

Lets say there is a HWVTEP managed by ODL.

 

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

 

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

 

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?

​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

 

Thanks,

Arun.

 


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



 

--

Thanks

Anil

 



 

--

Thanks

Anil


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Santosh
 

Thanks vishal , this was in reference to l2gateway  , netvirt.

On 17-Apr-2017 11:04 am, "Vishal Thapar" <vishal.thapar@...> wrote:

Hi Santosh,

 

You need to clarify what you mean by ODL here. If you mean OVSDB plugin, no it is not responsible for maintaining config DS entries for remote mcast/ucast macs. It is up to the application using the OVSDB/HWVTEP plugin to listen for Local ucast/mcast changes in HWVTEP operational datastore and accordingly add/remove remote ucast/mcast mac entries.

 

If you mean ODL to include applications too, it depends on which application you’re using. If you’re using the new netvirt which has implementation for L2GW, then yes, ODL does take care of update remote ucast/mcast mac entries based on changes on swtiches’ local ucast/mcast mac entries, whether at runtime or through reconciliation on reconnect.

 

Regards,

Vishal.

 

From: ovsdb-dev-bounces@lists.opendaylight.org [mailto:ovsdb-dev-bounces@lists.opendaylight.org] On Behalf Of Santosh Singh
Sent: 17 April 2017 10:46
To: Anil Vishnoi <vishnoianil@...>
Cc: ovsdb-dev@....org; K.V Suneelu Verma <k.v.suneelu.verma@ericsson.com>
Subject: Re: [ovsdb-dev] ODL behavior when connectivity with HW-VTEP's ovsdb-server goes down and comes back after sometime

 

Hi Anil 

As part of reconciliation does ODL takes care of sending delete request for the Macs( which were removedfrom local ucast table during the period when ODL was  disconnected), from the remote vtep ovsdb store I.e. remote ucast Macs.

 

Thanks

Santosh

 

On 17-Apr-2017 1:51 am, "Anil Vishnoi" <vishnoianil@...> wrote:

Hi Arun,

 

Please see inline ...

 

On Fri, Apr 14, 2017 at 7:24 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

HI Anil,

 

Thanks for looking into this!

 

A clarification on your comment:

Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"

Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?

​When i say operational state of the device is cleared, i meant the the operational state stored in the controller operational data store and not really the operational state in the device. Once device disconnects from controller, hwvtep will remove the operational data that it learned from device through rpc notifications from it's operational data store , it does not have any way to clear any state in the device itself because it's already disconnected.

 

Thanks,

Arun

 

 

 

On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:

+ suneel, vishal 

 

please see inline ..

 

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

Hi,

 

Lets say there is a HWVTEP managed by ODL.

 

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

 

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

 

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?

​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

 

Thanks,

Arun.

 


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@....org
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



 

--

Thanks

Anil

 



 

--

Thanks

Anil


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@....org
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


Arunkumar R G
 

Thanks Anil, Vishal!

Hi Anil,

I was also referring to the operational states of the device within ODL. Anyways, I got it clarified now.

Thanks,
Arun.

On Mon, Apr 17, 2017 at 11:56 AM, Santosh Singh <santosh.chandan@...> wrote:
Thanks vishal , this was in reference to l2gateway  , netvirt.

On 17-Apr-2017 11:04 am, "Vishal Thapar" <vishal.thapar@...> wrote:

Hi Santosh,

 

You need to clarify what you mean by ODL here. If you mean OVSDB plugin, no it is not responsible for maintaining config DS entries for remote mcast/ucast macs. It is up to the application using the OVSDB/HWVTEP plugin to listen for Local ucast/mcast changes in HWVTEP operational datastore and accordingly add/remove remote ucast/mcast mac entries.

 

If you mean ODL to include applications too, it depends on which application you’re using. If you’re using the new netvirt which has implementation for L2GW, then yes, ODL does take care of update remote ucast/mcast mac entries based on changes on swtiches’ local ucast/mcast mac entries, whether at runtime or through reconciliation on reconnect.

 

Regards,

Vishal.

 

From: ovsdb-dev-bounces@...ylight.org [mailto:ovsdb-dev-bounces@lists.opendaylight.org] On Behalf Of Santosh Singh
Sent: 17 April 2017 10:46
To: Anil Vishnoi <vishnoianil@...>
Cc: ovsdb-dev@...rg; K.V Suneelu Verma <k.v.suneelu.verma@...m>
Subject: Re: [ovsdb-dev] ODL behavior when connectivity with HW-VTEP's ovsdb-server goes down and comes back after sometime

 

Hi Anil 

As part of reconciliation does ODL takes care of sending delete request for the Macs( which were removedfrom local ucast table during the period when ODL was  disconnected), from the remote vtep ovsdb store I.e. remote ucast Macs.

 

Thanks

Santosh

 

On 17-Apr-2017 1:51 am, "Anil Vishnoi" <vishnoianil@...> wrote:

Hi Arun,

 

Please see inline ...

 

On Fri, Apr 14, 2017 at 7:24 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

HI Anil,

 

Thanks for looking into this!

 

A clarification on your comment:

Arun: 1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

Anil: "​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​"

Arun: So any Ucast_macs_local from the HWVTEP with which the connectivity went down, would be cleared immediately and hence the other VTEPs will also see a corresponding delete of Ucast_macs_remote entry. Am I right?

​When i say operational state of the device is cleared, i meant the the operational state stored in the controller operational data store and not really the operational state in the device. Once device disconnects from controller, hwvtep will remove the operational data that it learned from device through rpc notifications from it's operational data store , it does not have any way to clear any state in the device itself because it's already disconnected.

 

Thanks,

Arun

 

 

 

On Fri, Apr 14, 2017 at 1:50 AM, Anil Vishnoi <vishnoianil@...> wrote:

+ suneel, vishal 

 

please see inline ..

 

On Wed, Apr 12, 2017 at 11:34 PM, Arunkumar Rg <arunkumar.rg@...> wrote:

Hi,

 

Lets say there is a HWVTEP managed by ODL.

 

In the HWVTEP, the ovsdb-client has added some Ucast_macs_local entry in the vtep.db and thus the ODL gets to learn those mac-entries.

 

1. Now what happens to these Ucast_macs_local entries when the connectivity(ssl/tcp) between the ovsdb-server running in HWVTEP and ODL goes down? Whether the ODL flushes these Ucast_mac_local entries immediately or is there any age-out timer in ODL?

​I believe when the device disconnects from the controller, hwvtep plugin immediately clears out all the operational state learned from the disconnected device.​

 

2. Lets take during the time when there is no connectivity between ODL and HWVTEP, the ovsdb-client in the HW-VTEP has added one more entry in the Ucast_macs_local entries.Now if the connectivity between ODL and HW-VTEP comes back again, whether the ODL will learn all the Ucast_macs_local entry?

​Yes, it always read the existing information from the ovsdb  data store and put in the operational data store. ​

 

Thanks,

Arun.

 


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...rg
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev



 

--

Thanks

Anil

 



 

--

Thanks

Anil


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...rg
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev


_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@....org
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev