Device Certification catalogs in DSS are in conflict

Products

• Network Observability

Issue/Introduction

The Device Certification menu displays a conflict message when device identification settings differ between any two SpectroSERVERs in a DSS environment․​

 

SYMPTOMS:

• Tools/Device Certification Menu indicates a catalog conflict․

• Conflict persists even after loading a catalog from the Main Location Server (MLS) to a specific node․

• The specific server causing the conflict is not explicitly identified by the software․

Environment

 

• OS: Linux

• Product Release: 25.4.5

• Deployment: Distributed SpectroSERVER (DSS) environment

 

Cause

Spectrum flags conflicts at the DSS level when device identification settings differ between any two SpectroSERVERs․ Because all catalogs must be identical across the environment, any discrepancy triggers a global conflict alert rather than identifying a single server․

Resolution

PREREQUISITES:

• Access to the Main Location Server (MLS) and all primary SpectroSERVERs․

• Administrative permissions to stop/start SpectroSERVER services․

• Access to the $SPECROOT/SS/ss-Tools directory․

STEPS:

1. CREATE CATALOG BACKUP ON MLS: Generate a clean catalog-only file from the source of truth․

   • Shut down the SpectroSERVER on the MLS server․

   • Navigate to the SS directory: cd $SPECROOT/SS

   • Run the backup command: ../ss-Tools/SSdbsave -c MLS_catalog

   • Restart the SpectroSERVER on the MLS server․

   EXPECTED: An MLS_catalog.SSdb file is created and the MLS is back online․

2. DISTRIBUTE CATALOG FILE: Copy the clean catalog to all other nodes․

   • Copy the MLS_catalog.SSdb file to the %SPECROOT%/SS directory on every other primary SpectroSERVER in the DSS․

3. UPDATE PRIMARY SPECTROSERVERS: Apply the MLS catalog to each node while preserving local models․

   Perform these sub-steps on each primary SpectroSERVER (excluding the MLS):

   • Shut down the SpectroSERVER service․

   • Navigate to the directory: cd $SPECROOT/SS

   • Save current models: ../ss-Tools/SSdbsave -m models_only

   • Load the MLS catalog: ../ss-Tools/SSdbload -ic MLS_catalog.SSdb

   • Restore local models: ../ss-Tools/SSdbload -m models_only.SSdb

   • Restart the SpectroSERVER service․

   EXPECTED: The SpectroSERVER starts with the synchronized catalog and existing local models intact․

4. SYNCHRONIZE FAULT TOLERANT SERVERS: Ensure secondary servers are updated․

   • Run an online backup on the primary servers to synchronize these changes to any secondary/Fault Tolerant servers․

VERIFY SUCCESS:

• Open the Tools/Device Certification Menu․

• Confirm the conflict information is no longer present․

• Verify device identification settings are consistent across the DSS environment․