Any chance you misplaced one of the NEDs, and it's missing from the packages directory?
If you have a CLI device configured in NSO, then it's holding a reference to the NED.
If you try to reload packages while the NED is not there, then this reference cannot exist anymore, as the NED is not there anymore. As the ned-id parameter is mandatory when you set the device type to CLI, then you are essentially trying to create an illegal state in CDB, and this is why reload fails.
If you wanted this NED removed, then you'll have to remove all devices configured to use this NED before reloading packages.
A great question! Before I finalize the NSO Developer Days agenda and share the details, I'd like to make a final call to get your input!
Like most things in life, Network Automation is not a trivial thing. Since you are here you have probably decided tha...
Our next stop on the virtual NSO Developer Days tour will be Asia Pacific, March 3 (at noon Singapore Time). We would like to make this a special event and we are asking for your input. It may be a topic that you think is challenging and still haven't got...
For those of you who are using Python for you code, knows that there is only one way to be sure and it is to run the code. But how do you know what parts of you code have been executed?! I do very often put in print statements and look at the output and v...
Join us and an amazing line-up of speakers at NSO Developer Days on Wednesday, December 16from 9 to 11 am PT.
NSO customers and experts will be live and answering questions during the two-hour event.
Register now, it’s free!