Error starting the secondary SS - CsCorbaMgr Exception CosNaming NamingContext InvalidName

Products

• Network Observability
• Spectrum

Issue/Introduction

DX NetOps Spectrum throws error "ERROR TRACE at CsCorbaMgr.cc(1271): Exception: ::CosNaming::NamingContext::InvalidName " when trying to start after upgrade to version 24.3. This occurs only when starting the secondary/fault tolerant server , the primary SpectroSERVER does not have any issue.

 

Environment

This was only seen on the secondary SpectroSERVER of a Fault Tolerant pair. 

Cause

The migrated database on the secondary was causing the issue.

Resolution

Run OnLineBackup on the primary SS to sync the SSdb with the secondary (Ensure the $SPECROOT/SS/.VNMDBLOCK file is not present if the SpectroSERVER is stopped). Or manually copy over the backup file to the secondary SS and restore it.

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/24-3/administrating/database-management/spectroserver-database-maintenance/restoring-your-database/load-a-database.html

In the customer's environment they had a standalone server, i.e both SpectroSERVER and OneClick were running on it.  As this was caused by a migration the OneClick was also misconfigured and pointing to the wrong MLS.  This also needed to be resolved.

Edit the $SPECROOT/tomcat/webapps/spectrum/META-INF/context.xml file and update the locServerName field. Supply the primary hostname instead of secondary hostname.

Then stop/start the Spectrum Tomcat service on the secondary SS.

cd $SPECROOT/tomcat/bin/

./stopTomcat.sh

./startTomcat.sh