The device remains connected in NETCONF even when it is unreachable.
How to reproduce:
1) Connect device:
curl --request GET 'http://192.168.56.100:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netopeer' \ --header 'Authorization: Basic YWRtaW46YWRtaW4=' \ --header 'Content-Type: application/json' \ --data '{ "node": [ { "node-id": "netopeer", "netconf-node-topology:port": 830, "netconf-node-topology:reconnect-on-changed-schema": false, "netconf-node-topology:connection-timeout-millis": 20000, "netconf-node-topology:tcp-only": false, "netconf-node-topology:max-connection-attempts": 5, "login-password-unencrypted": { "netconf-node-topology:username": "netconf", "netconf-node-topology:password": "netconf" }, "netconf-node-topology:sleep-factor": 1.5, "netconf-node-topology:host": "127.0.0.1", "netconf-node-topology:between-attempts-timeout-millis": 2000, "netconf-node-topology:keepalive-delay": 20 } ] }'
2) Verify that the device is in a connected state.
3) Turn off the device.
This issue was introduced with the following commit:
https://git.opendaylight.org/gerrit/c/netconf/+/108253
- relates to
-
NETCONF-1108 Convert NETCONF client-side to transport-api
- Resolved