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 not able to see them in OneClick and/or after being able to see them in OneClick 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 directory need to be populated to the new SpectroSERVER.

Resolution

When setting up new Spectrum landscapes:

1. All SpectroSERVERs must point to the same Main Location Server (MLS), including all secondary fault tolerant SS. If you install and kept the main location hostname as it's local name then you will need to change the $SPECROOT/LS/.locrc to point to the MLS:

MAIN_LOCATION_HOST_NAME=hostname_of_the_mls

If you update this entry you will need to find the pid of the LocServer process and kill it. Processd will automatically restart the LocServer process.

2. The $SPECROOT/.hostrc file allows communication access between the SpectroSERVERs. The format of the file should be either a + symbol on the first line with the mls hostname on the second line:

+
mlshostname

Or only hostnames with the MLS SS on the first line:

mlshostname
SS1
SS2
SS1a
SS2a

3. Verify/edit your etc/hosts to include all hostnames and IP addresses.

4. Once the SS is installed and configured you will need to 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

5. Copy the $SPECROOT/custom/ folder from the MLS to the new landscape.

6. Start the SpectroSERVER

7 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.

a. An alternative to using modeling gateway for Users and Global Collections is to login to OneClick as the spectrum install owner. Then navigate to the Users tab and select each group, one by one. In the lower right select the Landscapes tab and select the new landscape. For the Global Collections you can select each GC, one by one and click Edit Global Collection. Click the Landscapes... tab and add the newly created landscapes.

8. After performing the above you will need to stop and restart all OneClick tomcat and webtomcat services.

From $SPECROOT/webtomcat/bin: ./stopWebTomcat.sh
From $SPECROOT/tomcat/bin: ./stopTomcat.sh

From $SPECROOT/tomcat/bin: ./startTomcat.sh
From $SPECROOT/webtomcat/bin: ./startWebTomcat.sh

Additional Information

Additional configuration items for adding the new landscape: