Best Practice for Adding New SpectroSERVERs in Spectrum

Products

• Spectrum
• Network Observability

Issue/Introduction

We have recently added 2 new landscape servers to our existing Spectrum environment.

We are able to see those landscapes present under the default events in the Event Configuration GUI. When we checked the custom events (0xfff....), we cannot see those newly added landscapes. We want to know if there are any steps needed such as copying custom files from an existing landscape to the new one.

In the new landscape server, we are not able to see any files under Events folder.  Not able to see newly created landscapes in Event configuration of custom events

 

Cause

The catalog and custom events need to be populated to the new SpectroSERVER.

Resolution

 When setting up new Spectrum landscapes:

 

1. Import the catalog from the MLS.  This will keep attribute handles in sync: 
   a.  Copy the latest SSdb save from the MLS to the new SS.  Place it in the $SPECROOT/SS-DB-Backup directory and unzip it.
   b.  On the new SS, stop the SpectroSERVER process.
   c.  Load only the catalog portion from the SSdb file using the "-c"command line option in the SS directory as the spectrum install owner:
       ../SS-Tools/SSdbload -c ../SS-DB-Backup/SSdb_savefile_from_the_MLS
   
   

2. Copy the $SPECROOT/custom/Events folder from the MLS to the new landscape.
3. Start the SpectroSERVER
4. If you need to add Users, Global Collections, or other containers/devices from other landscapes you may need to utilize Spectrums Modeling Gateway.  Using Modeling Gateway you can Export the models to an xml export file from the MLS (or other SpectroSERVER if needed).  On the new SpectroSERVER you can use Modeling Gateway and import the data contained within the xml you exported from the other SS.

Additional Information

Additional configuration items for adding the new landscape:

Troubleshooting Checklist when adding a new landscape to a Spectrum DSS environment