Enterprises using Cisco’s Network Services Orchestrator (NSO) software seeing mystery crashes now have a solution.
NSO is a multivendor system that links network automation and orchestration tools with the underlying physical and virtual infrastructure, with applications in enterprise and service provider environments.
In a recent field notice, the networking giant discovered a process in the software that causes a resources leak and eventual crash – and the time between crashes depends only on the resources allocated to the software.
Twenty NSO 5 versions, ranging from 5.6 to 5.8.2, are affected.
The issue is that subscribers can access an API named cbd-diff-iterate, but Cisco also uses it internally for licencing and notification needs.
Customers that utilise Smart Licensing, notification-kicker, or who directly contact the API through C, Python, Java, or econfd are impacted by this.
According to Cisco’s field notice, “Any change under /kickers/notification-kicker or /devices/device will activate an internal subscription, which results in the leak.”
There is no way to disable the internal subscribers.
