OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [NETCONF-1201] Long delay in connection status update after connection issue for multiple devices https://jira.opendaylight.org/browse/NETCONF-1201 netconf <p>This issue is identical to <a href="https://jira.opendaylight.org/browse/NETCONF-966" class="external-link" rel="nofollow">https://jira.opendaylight.org/browse/NETCONF-966</a>, but it is necessary to initiate more than one device.<br/> With a single device, it works correctly.</p> <p>Steps to reproduce:</p> <p>1. Start Karaf: </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>feature:install odl-restconf-all odl-netconf-topology</pre> </div></div> <p>2. Initialize 2 devices with auto-connect:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>java -jar netconf-testtool-7.0.0-SNAPSHOT-executable.jar --device-count 2 --ssh true --md-sal true --controller-ip 127.0.0.1 --controller-port 8181</pre> </div></div> <p>3. Verify the connected state.</p> <p>4. Drop the packet from one of the NETCONF devices:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>sudo iptables -I INPUT -p tcp --dport 17831 -j DROP</pre> </div></div> NETCONF-1201 Long delay in connection status update after connection issue for multiple devices Bug Medium Resolved Won't Do Ivan Hrasko Peter Suna Tue, 21 Nov 2023 11:21:05 +0000 Tue, 9 Jan 2024 12:58:08 +0000 Tue, 28 Nov 2023 15:28:14 +0000 7.0.0 5.0.10 6.0.6 7.0.0 5.0.10 6.0.6 netconf 0 2 <p>Upon further investigation, it appears that there is an error in the Steps to reproduce that I provided for this task. I apologize for any confusion this may have caused. The mistake lies in the utilization of the testtool auto-connect with the default configuration, which sets the <b><tt>keepalive-delay</tt></b> to <b>0.</b></p> <p>As indicated in the documentation, "<em>If a value &lt;1 is provided, no keepalives will be sent</em>". This unintended behavior might be the root cause of the issue.<br/> <a href="https://github.com/opendaylight/netconf/blob/1d54816dbaf3cbc14c72ec80e643bf6fda1fc093/plugins/netconf-client-mdsal/src/main/yang/odl-netconf-device.yang#L198" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/1d54816dbaf3cbc14c72ec80e643bf6fda1fc093/plugins/netconf-client-mdsal/src/main/yang/odl-netconf-device.yang#L198</a></p> <p>When I try to connect the device with a <tt>keepalive-delay</tt> set higher than 0, the connection state changes immediately after the expiration of the keepalive RPC.</p> Development Rank 0|i046v3: