Hi,

For the next OPNFV release (Colorado), we are trying to test SFC with ODL Boron 
but we are hitting some problems. One of them appears in around 50% of the 
deployments and seems as if the problem is in the openflow plugin. We see the 
following in the logs of OVS:
2016-07-25T15:36:37.180Z|00104|rconn|INFO|br-int<->tcp:192.168.0.44:6653: 
connected
2016-07-25T15:36:37.183Z|00105|rconn|INFO|br-int<->tcp:192.168.0.44:6653: 
connection closed by peer

And at the same time, we see the following in ODL logs:


2016-07-25 15:36:29,178 | INFO  | ntLoopGroup-11-7 | ConnectionAdapterImpl      
      | 255 - org.opendaylight.openflowjava.openflow-protocol-impl - 
0.8.0.SNAPSHOT | Hello received / branch
2016-07-25 15:36:29,181 | INFO  | ntLoopGroup-11-7 | DeviceManagerImpl          
      | 265 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | 
ConnectionEvent: Device connected to controller, Device:/192.168.0.43:55981, 
NodeId:Uri [_value=openflow:123294860651030]
2016-07-25 15:36:29,181 | ERROR | ntLoopGroup-11-7 | HandshakeListenerImpl      
      | 265 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | 
ConnectionContext initial processing failed: Role context for master Node Uri 
[_value=openflow:123294860651030] is still not closed.
2016-07-25 15:36:29,184 | INFO  | ntLoopGroup-11-7 | ConnectionContextImpl      
      | 265 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | 
Unregister outbound queue successful.
2016-07-25 15:36:29,185 | INFO  | ntLoopGroup-11-7 | RpcManagerImpl             
      | 265 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | 
Unregister RPCs services for device context closure
2016-07-25 15:36:29,185 | INFO  | ntLoopGroup-11-7 | RoleContextImpl            
      | 265 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | Role 
context closed, unregistering all candidates for ownership for node Uri 
[_value=openflow:123294860651030]

That results in the switch not getting any flow. Restarting ODL solves the 
problem partially: we don't see those connection problems anymore but then we 
only get a few flows and not all of them.

Have you seen this problem? Did you perhaps already found a solution? We are 
working with a ODL build which is around 2 weeks old and perhaps this was 
solved already.

Thanks,
Manuel
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to