Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
This is one of the most tested/used functionalities in ConfD (hence NSO too). So it would be surprising if this is an NSO issue. But you never know. Check that you reply with ITER_RECURSE for parent lists/containers (not ITER_CONTINUE etc.)Subscriber...
Check your port configuration for the device. We have seen XR devices sending a <hello> without capabilities when connecting to the device using SSH port 22 instead of the NETCONF SSH port 830.
commit-confirm is not used by the juniper-junos NED with the device due to the severity of the deviation from RFC 4741.Note that there is a newer juniper-junos_nc "third-party" NED available that workaround this and other Juniper NETCONF interface is...
Looked into this. Juniper devices advertise support for the old NETCONF RFC4741 confirmed-commit:1.0 capability. Not the RFC6241 confirmed-commit:1.1. But it does not conform to the RFC4741 standard. There are several examples where one example with ...
Did the router returned capabilities also contain the candidate capability?<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>The candidate capability is required for confirmed-commit. See https://datatracker.ietf.org/doc/html/r...
