How can SpectroSERVERs be switched in a Fault Tolerant environment?
search cancel

How can SpectroSERVERs be switched in a Fault Tolerant environment?

book

Article ID: 50032

calendar_today

Updated On:

Products

Spectrum Network Observability

Issue/Introduction

There may be a time when you need to swap the primary and the secondary SpectroSERVERS. This document will provide you with the steps to switch them so that you can make the secondary the primary, and the primary the secondary.

 

Environment

Release: SPPREM05900-9.2-Spectrum-Infrastructure Manager-Premium Suite
Component:

Resolution

From within Spectrum OneClick, select the plus symbol (+) next to the VNM icon in the Navigation window. Highlight or select the LocalLscpe model. In the Component Detail of the LocalLscpe model, select the Loaded Landscapes option.

  1. Change secondary precedence to 5

  2. Wait 10 mins

  3. Change old primary precedence from 10 to 20

  4. Wait 5 mins

  5. Change new primary precedence from 5 to 10

  6. Restart the SS and OC (this step may not be needed if everything switches fine).

Verify the map is correct:
From the <SPECROOT>/SS-Tools directory run: ./MapUpdate -v

Verify the correct precedence is set on the correct machine.

If you experience any problems, there is some debugging you can enable:
Add the following line to the .vnmrc file in the <SPECROOT>/SS directory on BOTH the primary and secondary SpectroSERVERS:

This, will require a SpectroSERVER restart. Output will be sent to the VNM.OUT.

Additional Information

Another way:

Note: Perform the steps logged as Spectrum Install owner account.

1. Stop the current secondary SS - Server B

2. Stop the processd on the current SS - Server B

# systemctl stop processd (logged as root account)

3. Run the MapUpdate utility and see if you see Server B in the landscape mapping. If positive remove it.

# cd $SPECROOT/SS-Tools/

# ./MapUpdate -v

# ./MapUpdate -remove <Landscape_Handle> -precedence <Precedence>

4. Take an OnLineBackup on the current primary SS - Server A

5. Stop the current primary SS - Server A.

6. Stop the processd on the current primary SS - Server A

# systemctl stop processd (logged as root account)

7. Transfer the  $SPECROOT/SS-DB-Backup/db_<date>_<time>.SSdb.gz file from Server A to Server B, in the $SPECROOT/SS-DB-Backup/ directory.

8. Unzip the db_<date>_<time>.SSdb.gz file on Server B.

# gunzip db_<date>_<time>.SSdb.gz

9. Start the processd on Server B.

# systemctl start processd (logged as root account)

10. Load the SSdb on Server B and replace the precedence from 20 to 10 (to set it as the new primary SS).

# cd $SPECROOT/SS/ (you must be in the SS directory to run the SSdbload command line)

# ../SS-Tools/SSdbload -il -r 10 ../SS-DB-Backup/db_<date>_<time>.SSdb

11. Start the SpectroSERVER application on Server B.

12. Run the MapUpdate utility and see if you see Server B with precedence 10 in the landscape mapping. I don't expect Server A on this list.

# cd $SPECROOT/SS-Tools/

# ./MapUpdate -v

13. Take an OnLineBackup on the new primary SS - Server B

14. Transfer the  $SPECROOT/SS-DB-Backup/db_<date>_<time>.SSdb.gz file from Server B to Server A, in the $SPECROOT/SS-DB-Backup/ directory.

15. Unzip the db_<date>_<time>.SSdb.gz file on Server A.

# gunzip db_<date>_<time>.SSdb.gz

16. Start the processd on Server A.

# systemctl start processd (logged as root account)

17. Load the SSdb on Server B and add precedence 20 (to set it as the new secondary SS).

# cd $SPECROOT/SS/ (you must be in the SS directory to run the SSdbload command line)

# ../SS-Tools/SSdbload -il -a 20 ../SS-DB-Backup/db_<date>_<time>.SSdb

18. Start the SpectroSERVER application on Server A.

19. Run the MapUpdate utility and see if you see Server A with precedence 20 in the landscape mapping.

# cd $SPECROOT/SS-Tools/

# ./MapUpdate -v

==========================

The following steps are required if the landscape mapping is not correct on Server B.

20. Stop the new secondary SS - Server A.

21. Take an OffLineBackup on the new secondary SS - Server A.

22. Save the SSdb on Server A.

# cd $SPECROOT/SS/ (you must be in the SS directory to run the SSdbsave command line)

# ../SS-Tools/SSdbsave -cm ../SS-DB-Backup/db_<date>_<time>

23. Start the SpectroSERVER on Server A.

24. Transfer the  $SPECROOT/SS-DB-Backup/db_<date>_<time>.SSdb.gz file from Server A to Server B, in the $SPECROOT/SS-DB-Backup/ directory.

25. Unzip the db_<date>_<time>.SSdb.gz file on Server B.

# gunzip db_<date>_<time>.SSdb.gz

26. Stopt the SpectroSERVER on Server B.

27. Load the SSdb on Server B.

# cd $SPECROOT/SS/ (you must be in the SS directory to run the SSdbload command line)

# ../SS-Tools/SSdbload -il ../SS-DB-Backup/db_<date>_<time>.SSdb

28. Start the SpectroSERVER application on Server B.

29. Run the MapUpdate utility and see if you see both Server A and B are in the landscape mapping.

# cd $SPECROOT/SS-Tools/

# ./MapUpdate -v

30. If you are switching the precedence of the MLS, then additional steps are required:

a) In the OneClick Administration page --> SPECTRUM Configuration, switch the Main Location Server Name and Backup Location Server Name. Or edit the $SPECROOT/tomcat/webapps/spectrum/META-INF/context.XML file and bounce the Tomcat service.

b) On each remote landscape switch the MAIN_LOCATION_HOST_NAME and BACKUP_MAIN_LOCATION_HOST_NAME values in the $SPECROOT/LS/.locrc file and bounce the LocServer service

Powered by Wolken Software