About jmaruschak

jmaruschak · 04-07-2021

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...

jmaruschak · 03-09-2020

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 ...

jmaruschak · 02-25-2020

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...

jmaruschak · 01-09-2020

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 ...

jmaruschak · 02-07-2019

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...

jmaruschak · 07-11-2023

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...

jmaruschak · 08-14-2020

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...

jmaruschak · 08-14-2020

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 ...

jmaruschak · 02-08-2019

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!

Member Since	‎09-27-2017 06:38 AM
Date Last Visited	‎07-12-2023 12:04 AM
Posts	11
Total Helpful Votes Received	15

User Statistics

User Activity

Rename NSO Device and Maintain Associated Services

NSO Configuration Errors and Rollbacks Due to Device Prompt Following Write Command

Differences Between NSO CDB and Device Running Config Due to Device Interpretation

Service out-of-sync Due to Automatically Generated Configuration on ASR920

Executing CLI Commands With Additional Prompts Through NSO

Re: Rename NSO Device and Maintain Associated Services

Re: NSO Configuration Errors and Rollbacks Due to Device Prompt Following Write Command

Re: NSO Configuration Errors and Rollbacks Due to Device Prompt Following Write Command

Re: Executing CLI Commands With Additional Prompts Through NSO