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 <[email protected]> wrote: > > 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 (Lithium design) or just > openflow plugin (Helium design)? > >> On Thu, Mar 3, 2016 at 3:04 PM, Luis Gomez <[email protected]> wrote: >> 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 <[email protected]> wrote: >>> >>> 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 | ConnectionAdapterImpl >>> | 173 - org.opendaylight.openflowjava.openflow-protocol-impl - >>> 0.7.0.SNAPSHOT | received unexpected rpc response: RpcResultKey >>> [xid=3613138056, >>> outputClazz=org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.GetFeaturesOutput] >>> This seems to be related to the bug #5090 which can be found here: >>> https://bugs.opendaylight.org/show_bug.cgi?id=5090 >>> However, this is not my main problem. The main problem is that the >>> notifications about the OpenFlow switches arrive with a delay. >>> It takes about 30-50 seconds after the above warnings are logged in order >>> the controller to receive the new switch notifications. >>> Can I configure someway the notifications not to be delayed? Is it some >>> possible bug that causes the above? >>> >>> Thank you in advance, >>> Chris >>> _______________________________________________ >>> openflowplugin-dev mailing list >>> [email protected] >>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >> >> >> _______________________________________________ >> openflowplugin-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >> >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
