We have lots of automations where we execute ncs_cli commands. We need to make sure ncs_cli exits with an error code only if there is an actual error. Any insights on mysterious "*** CLOSE TIMEOUT ***" are very much appreciated.
"admin@ncs# show cli" only has "idle-timeout". is this anyway related to "*** CLOSE TIMEOUT ***"?
"devices global-settings" also only has connect/write/read timeouts. not sure these would affect "*** CLOSE TIMEOUT ***"
Do you have a hard time staying updated on what's going on due to the massive flow of information?
I recommend that you manage your subscription and notification settings by clicking on your avatar up on the right corner.
Select "My subscriptions" ...
The NSO community is constantly growing. The number of unique visitors on the Developer Hub has been increasing steadily since the beginning and the trend continues. Network Automation is, as we could read in Cisco’s inaugural N...
We're excited to announce our third annual Cisco NSO Developer Days NYC!
Returning to New York City, the two-day event is a tremendous opportunity to learn more about real-world applications of automation, gain a better understanding of NSO technol...
Want to run both python2 and python3 packages at the same time? Maybe you don't want to upgrade all your python2 services at the same time? With some small changes to the "ncs-python-start-vm" script you can. While you are at it maybe you would like...