https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-1031 netvirt <p>Should the the two values are used to configure how the ovs nodes connect to ODL be changed from the defaults?</p> <ul> <li>controller-max-backoff: max time between connection attempts from the nodes to ODL</li> <li>controller-inactivity-probe: time between sending inactivity probes on connections</li> </ul> <p>The defaults are 8s and 5s. If the inactivity-probe hits, then the switches disconnect from ODL. That cleans up the openflowplugin operational data for the node. That is then relayed to networking-odl that the node is down and networking-odl marks the node as inactive. When a node is down, networking-odl driver would mark port-binding as failed, so VM would enter ERROR state</p> <p> </p> NETVIRT-1031

Review controller-max-backoff and controller-inactivity-probe values

Sub-task NETVIRT-1006 Medium Resolved Done Unassigned Sam Hague csit:3node Tue, 28 Nov 2017 15:09:34 +0000 Mon, 17 Sep 2018 18:59:26 +0000 Mon, 17 Sep 2018 18:59:26 +0000 General 0 1 <p><a href="https://git.opendaylight.org/gerrit/#/c/51763/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/51763/</a></p> <p>controller-inactivity-probe was bumped to 30s</p> Relates OPNFLWPLUG-1007 Development Rank 0|i038hz: