I think that is not this bug but this one: https://bugs.opendaylight.org/show_bug.cgi?id=4614 <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 > <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
