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.
I am seeking advice on the best practice in managing configuration using both NSO and a third party system, where the third party system adds partial configuration under the container/context created by NSO.Our final goal is to have NSO manage 100% o...
Cisco NSO use netconf NED to manage some juniper routers."show devices device xxx capability" from NSO returns below line, indicating the router is a commit-confirmed capable router."capability urn:ietf:params:xml:ns:netconf:capability:confirmed-comm...
We use nso to configure juniper junos routers via netconf ned.We have a service template to apply interface egress shaper, which is equivalent to the below junos cli command: set class-of-service interfaces xe-0/0/10 unit 2819 shaping-rate 1g The ser...
Thanks Huayyang. I will read more and test the new feature in NSO 6.5. It seems a good solution to our problems. However, our environment is NSO6.3, I wonder how people manage these problems before NSO6.5? It will take time to move to NSO6.5 due to N...
Thanks Cohult. It is very useful. Is it correct to interpret that NSO only uses commit-confirm on a device with capability of RFC6241 confirmed-commit:1.1? Are the flaws mentioned above specific to Juniper, or are they observed on devices with confir...
The reply from the device on capability, containing candidate and confirmed-commit<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:n...
Thanks all. Very good tip of collecting trace. In the trace, the router returned capabilities contain the below line:<capability>urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0</capability>I am now confident that a tac case is needed t...
