The Alarms are not synchronized when failing over back from Secondary to Primary SpectroServer

Document ID:  TEC1047427
Last Modified Date:  07/13/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Spectrum

Releases

  • CA Spectrum:Release:10.2
  • CA Spectrum:Release:10.2.1
  • CA Spectrum:Release:10.1.2
  • CA Spectrum:Release:10.1
  • CA Spectrum:Release:10.1.1
  • CA Spectrum:Release:10.0

Components

  • CORE / SPECTROSERVER:SPCCSS
Issue:

In the Fault Tolerance environment, the failover happened from the Primary SpectroSERVER to the secondary SpectroSERVER. After the Primary SpectroSERVER is back to normal, on the OneClick console, the alarms are not synchronized between the Primary and the secondary SpectroSERVER.

Environment:
Spectrum 10.x; Spectrum 9.4;
Cause:

In order to have the alarm synchronization happen between the primary and secondary SpectroSERVERin the Fault Tolerance environment, we will need to have this following entry in the $SPECROOT\SS\.vnmrc file on both the primary and secondary SpectroSERVER.

ftasv_enabled=true

 

 
Resolution:

By default, the entry "ftasv_enabled=true" doesn't exist in the $SPECROOT\SS\.vnmrc file on the SpectroSERVER.

So we will need to manually add this entry to the $SPECROOT\SS\.vnmrc file on both the primary and secondary SpectroSERVERIf you change this file

while SpectroSERVER is running, the changes take effect when SpectroSERVER is restarted.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >