CM_NIMBUS_PACKAGE not always up to date

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We use "enable_cm_nimbus_package = true" to have CM_NIMBUS_PACKAGE table up to date. The CM_NIMBUS_PACKAGE doesn't seem to update all the time and in a timely manner when a package is deployed. Seems that, in some scenario that is yet to be identified, the table is not updatded whether in other cases is updated immediately.  

Environment

DX UIM 20.4.* / 23.4.*

Cause

Duplicated packages. discovery_server might be erroring on some duplicate entries for the a probe. For example, some of the custom packages used, including superpackages, might have a probe name mispelled. For example with a capital letter:

Processes  

Cdm

Ntservices 

This duplication is causing, in some cases where this exists, that changes to the probe packages are NOT propagated to the DB cm_nimbus_pakage table. 

Resolution

To resolve the issue, the probe package identified with a capital letter must be uninstalled from all the controllers where it is running. 

Note: When the bad package is removed, before redeploying the good package again, wait for the BAD DB Entry to be deleted first, otherwise the issue will not be resolved. 

Additional Information

Related KBs:

• After deploying some custom packages, CM_NIMBUS_PACKAGE is not updated (broadcom.com)
• Discovery queue is not draining - error in discovery logs mentions duplicate key in CM_NIMBUS_PACKAGE (broadcom.com)