Re: [openflowplugin-dev] Delay in notifications

Sorry for spamming, but the versions in my previous message is incorrect. Please ignore the parenthesis. Chris 2016-03-04 9:43 GMT+02:00 Chris Grivas : > Update/edit: > The delay happens in both openflowplugin-li and openflowplugin. > > One can easily reproduce the delay by installing just > odl

Re: [openflowplugin-dev] Delay in notifications

Update/edit: The delay happens in both openflowplugin-li and openflowplugin. One can easily reproduce the delay by installing just odl-openflowplugin-flow-services-rest feature and trying to connect a topology to it using cpqd (version 2.4.9). I inspect the topology through restconf/operational/ne

Re: [openflowplugin-dev] Delay in notifications

Thanks! Good to know. On Thursday, March 3, 2016, Chris Grivas wrote: > > I am using openflow plugin (helium) design and the delay only happens with > cpqd. The notifications do NOT delay when I use openvswitch. There is also > NO delay with either switch when I use openflowplugin-Ii. > > Regard

Re: [openflowplugin-dev] Delay in notifications

I am using openflow plugin (helium) design and the delay only happens with cpqd. The notifications do NOT delay when I use openvswitch. There is also NO delay with either switch when I use openflowplugin-Ii. Regards, Chris > On 04 Mar 2016, at 01:45, Abhijit Kumbhare wrote: > > Thanks Luis.

Re: [openflowplugin-dev] Delay in notifications

Thanks Luis. But I think his message (unexpected rpc response in GetFeaturesOutput) seems to be different than the bug (which has unexpected rpc response in BarrierOutput). Also he seems to be having issue with the delay in the switch notifications. Chris - are you running the openflow-plugin-li (

Re: [openflowplugin-dev] Delay in notifications

I think that is not this bug but this one: https://bugs.opendaylight.org/show_bug.cgi?id=4614 . Please make sure your switch properly handles xid. BR/Luis > On Mar 3, 2016, at 3:28 AM, Chris Grivas wrote: > > Hi all, > I am trying to move f

[openflowplugin-dev] Delay in notifications

Hi all, I am trying to move from lithium to beryllium. Using beryllium, when a mininet topology using OF 1.3 switches gets connected to the controller the following warnings appear in the log for every switch in the topology: 2016-03-02 11:45:50,405 | WARN | entLoopGroup-7-2 | ConnectionAdapterI