Failed transactions due to expected disruption of management connectivity

[inivan]

Hello colleagues,

There are a plenty of scenarios when it’s expected that NSO can’t gracefully commit a transaction. For instance, if we change a device’s management IP address via NSO, or making some changes on uplink interface which disrupt a device’s management connectivity temporary etc. In all of that cases the transaction can’t be successfully finished because NED never get a CLI prompt (or any other kind of execution’s confirmation) from the device under management.

I would clarify are there any best practices or recommended design patterns for services which invoke that kind of transactions, or maybe some NSO enhancements have been developed specifically for that scenarios?

Thank you in advance for your suggestions

Ivan

[hniska · Accepted solution]

Best practice is to not cut the management connection. Just add another IP, change the IP in NSO to the new one, remove the old. 

Did a small package that does exactly that a long time ago https://github.com/NSO-developer/ipchange-service