karaf.log
[NETCONF-1201] Long delay in connection status update after connection issue for multiple devices Created: 21/Nov/23 Updated: 09/Jan/24 Resolved: 28/Nov/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | 7.0.0, 5.0.10, 6.0.6 |
| Fix Version/s: | 7.0.0, 5.0.10, 6.0.6 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Peter Suna | Assignee: | Ivan Hrasko |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pt, regression | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
karaf.log
|
| Description |
|
This issue is identical to https://jira.opendaylight.org/browse/NETCONF-966, but it is necessary to initiate more than one device. Steps to reproduce: 1. Start Karaf: feature:install odl-restconf-all odl-netconf-topology 2. Initialize 2 devices with auto-connect: 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 3. Verify the connected state. 4. Drop the packet from one of the NETCONF devices: sudo iptables -I INPUT -p tcp --dport 17831 -j DROP |
| Comments |
| Comment by Peter Suna [ 28/Nov/23 ] |
|
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 keepalive-delay to 0. As indicated in the documentation, "If a value <1 is provided, no keepalives will be sent". This unintended behavior might be the root cause of the issue. When I try to connect the device with a keepalive-delay set higher than 0, the connection state changes immediately after the expiration of the keepalive RPC. |