This issue is present on current main branch targeting NETCONF 7.
Invoke PUT:
http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf
With content:
{
"topology": {
"topology-id": "topology-netconf",
"node": [
{
"node-id": "netopeer2A",
"netconf-node-topology:key-based": {
"username": "netconf",
"key-id": "device-key-A"
},
"netconf-node-topology:schemaless": false,
"netconf-node-topology:port": 830,
"netconf-node-topology:tcp-only": false,
"netconf-node-topology:keepalive-delay": 0,
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:max-connection-attempts": 5
},
{
"node-id": "netopeer2B",
"netconf-node-topology:key-based": {
"username": "netconf",
"key-id": "device-key-B"
},
"netconf-node-topology:schemaless": false,
"netconf-node-topology:port": 830,
"netconf-node-topology:tcp-only": false,
"netconf-node-topology:keepalive-delay": 0,
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:max-connection-attempts": 5
}
]
}
}
Despite setting max-connection-attempts, the device is in connecting state on forever as we see from GET.
http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node/node-id;node/netconf-node-topology:connection-status&content=all
With body:
{
"network-topology:topology": [
{
"node": [
{
"node-id": "netopeer2A",
"netconf-node-topology:connection-status": "connecting"
},
{
"node-id": "netopeer2B",
"netconf-node-topology:connection-status": "connecting"
}
]
}
]
}
We expect status to be unable-to-connect after some time.
- blocks
-
NETCONF-1114 Incorrect operational state of device configuration with Invalid encrypted password
-
- Confirmed
-
- relates to
-
-
- Resolved
-
