Orphaned Spectrum Landscape Listed in OneClick Administation > Landscapes page with name of null

Products

• Spectrum
• Network Observability

Issue/Introduction

There are two common symptoms caused by retired or orphaned landscapes remaining in the system​​​​​​‌​, but is not referenced in the landscape map (MapUpdate -v) of the main landscape server or anywhere else on the Spectrum system.

ERROR MESSAGES:

"UserModelDomainList: could not obtain the name for domain <LANDSCAPE_NAME>"

"DataSourceIsTooBusyException: Sync attempted when one or more SpectroSERVERS are not connected to the OneClick server" "SPC-OCA-10362 - unknown landscape in OneClick"

 

SYMPTOMS:

• Tomcat starts but the log references a non-existent landscape

• The retired landscape is visible in OneClick web administration as a null entry

• NetOps Portal datasource integration is stuck in state "busy"

• The OneClick server shows "null" landscapes

   

CONTEXT: Occurs during normal operation or when attempting to register a Lab Spectrum environment as a datasource within NetOps portal․

The retired landscape is still visible in the OneClick web administration landscapes page, as a null entry, 

IMPACT: Prevents NetOps Portal integration and clutters OneClick Administration views․

Environment

Release: All Supported Releases

Component: SPCOCK - Spectrum OneClick

Cause

The DuplicateList attribute (0x11cd5) on the master model contains invalid entries mapping to removed landscapes․

Resolution

PREREQUISITES:

• CLI access to Spectrum MLS server

• Spectrum Install Owner account credentials

 

STEPS:

STEP 1: VERIFY AND FIX THE SPECTRUM INSTALL OWNER MODEL

Path: $SPECROOT/vnmsh

Connect CLI as the install owner: ․/connect

Find the model handle: ․/show models | grep <username>

Check the DuplicateList attribute for invalid entries: ․/show attributes mh=<model_handle> | grep 0x11cd5

Send action code 0x10103 (CHECK_HOME_INTEGRITY) to fix the issue: ․/update action=0x10103 mh=<model_handle>

EXPECTED: Command returns "update action: successful"․

Verify the attribute is cleared: ․/show attributes mh=<model_handle> | grep 0x11cd5

 

STEP 2: RESTART TOMCAT SERVICE

Restart the Spectrum Tomcat web server service․

$SPECROOT/tomcat/bin/stopTomcat.sh

ps -ef | grep tomcat | grep -v webtomcat    (to ensure the tomcat service was successfully shutdown)

$SPECROOT/tomcat/bin/startTomcat.sh

EXPECTED: Null landscapes no longer appear and NetOps portal connects successfully ․

 

ALTERNATIVE SCRIPT METHOD: 

The attached script (user_model_sync.sh) can be used to do this automatically for all user models. It should be placed in a custom directory under the $SPECROOT/vnmsh/custom directory on the MLS server in a distributed Spectrum environment:

STEP 1: RUN AUTOMATED SCRIPT

Stop the Spectrum Tomcat web server service․ ($SPECROOT/tomcat/bin/stopTomcat.sh)

Place user_model_sync․sh in $SPECROOT/vnmsh/custom․

Make it executable and run it using the Spectrum Install Owner․

Start the Spectrum Tomcat web server service․ ($SPECROOT/tomcat/bin/startTomcat.sh)

 

VERIFY SUCCESS:

• NetOps Portal integration completes successfully․

• OneClick Administration Landscapes page shows only active landscapes ․