-
Bug
-
Resolution: Unresolved
-
Medium
-
7.0.0
When attempting to establish a Netconf connection with a device under unstable network conditions, the device is stuck in `connecting` state.
Steps to reproduce:
- Start testtool with a huge amount of yang models, for example with Junos models.
- Set 50% packet loss for testtool device (tc qdisc add dev eth0 root netem loss 50%).
- Start restconf-netconf Karaf application.
- Connect testtool device.
curl --location --request PUT 'http://192.168.56.100:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=new-netconf-device' \
--header 'Authorization: Basic YWRtaW46YWRtaW4=' \
--header 'Content-Type: application/json' \
--data '{
"node": [
{
"node-id": "new-netconf-device",
"netconf-node-topology:port": 17830,
"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": "admin",
"netconf-node-topology:password": "admin"
},
"netconf-node-topology:host": "192.168.56.200",
"netconf-node-topology:keepalive-delay": 120
}
]
}'
- relates to
-
-
- Resolved
-
