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.
We're in the process of renaming a number of devices across our network. When renaming the devices in NSO this seems to present challenges for any services that are already deployed on them. I'm opening this thread to explore gather opinions and sugg...
Greetings,We're experiencing issues with Cisco ASR920 devices when applying configuration changes through NSO. NSO appears to get stuck with a device prompt during the commit phase. The configuration is then rolled back. This happens most frequently ...
Greetings, We've run into a number of examples of differences appearing between the NSO CDB and the running config on certain devices. This appears to be caused by the device accepting a certain syntax, but storing a different but equivalent syntax i...
We're using a certain service which creates a service instance on an interface on an ASR920. The service instance uses the command mac security sticky in order to restrict the device able to connect to the circuit. When first deployed on the service ...
When executing commands on the device CLI through NSO, is there a way to handle additional prompts or questions from the device? Our use case is upgrading the IOS software on all of our ASR920 devices. We upgrade the IOS software using a copy command...
Hi @emsmith ,Unfortunately, no other responses were received.We use aliases for each renamed device such that the new name will "expand" to the old name on the NSO CLI. This allows users on the NSO CLI to enter the new device name and have NSO accept...
The timeout would have occurred first, and was the source of the error. The rollback would have been attempted following the timeout. In fact, we could see in the trace logs that many times the error would occur again when issuing the write memory co...
This did end up being resolved. We actually involved Cisco TAC to investigate. What was found is that the ASR920s are notorious for taking a very long time to write their configuration. The "read timeout after 20 seconds" in the error indicates that ...
I think this covers our use case. We were able to test this on a physical device and we did get it to work after a few iterations. Thanks for the quick reply!
