New Global Collection name not synchronized to DX Operational Observability

Products

• Network Observability
• Spectrum
• DX Operational Intelligence
• DX Operational Observability

Issue/Introduction

When you rename a Global Collection name in Spectrum, the new Global Collection name is not synchronized to DX Operational Observability (O2) via SpectrumDataPublisher. In DX Operational Observability we can still see the old Global Collection name in the synchronized device attributes.  You restarted SpectrumDataPublisher several times, waited several days, but the change in Global Collection name is not synchronized.

The business impact of this is huge as without updating the Global Collection names, the alarms and the services don't assign/work correctly.

 

Environment

DX Operational Intelligence/DX Operational Observability

SpectrumDataPublisher (v24.3.10)

Cause

Renaming a Global Collection in Spectrum does not update the device level member attributes for CollectionsModelNameString and CollectionUniqueKeyString within the SpectroSERVER database.  In the OneClick GUI these attributes are calculated on the fly so appears incorrectly as the updated value.  With the current design, the device level attributes are only updated in the SSdb under the following conditions:

• when the device is added to the Global Collection

or 

• when the device is removed from the Global Collection .

Resolution

As this was done originally by design, it will be changed by a Request For Enhancement instead of by defect.  Until the new functionality is added, we can work around this by either of the following methods.

• Create a new Global Collection with the desired name and add devices to it.  This will give us new  CollectionsModelNameString and CollectionUniqueKeyString attribute values at the device level.

or

• if you need to retain the original CollectionUniqueKeyString attribute values (e.g. for programmatic reasons), do the following.

1. Rename the Global Collection.
2. Create a temporary Global Collection and attach all models that were under the renamed Global Collection to the newly Global Collection in OneClick.
3. Remove all models from temporary Global Collection or remove the Global Collection. 

 

Additional Information

Check back on this KB to get updated details of the progress of the Enhancement Request.

The same improper behavior is seen when renaming topology containers.