Duplicate alarms generated during Secondary SpectroSERVER startup in Fault Tolerant environments

Products

• Network Observability

Issue/Introduction

In a Fault Tolerant (FT) Spectrum environment, duplicate alarms may be generated immediately after a Secondary SpectroSERVER completes its startup sequence. This behavior occurs because the Secondary server initiates model activation and device polling before receiving the full synchronization state—specifically clear or suppression flags—from the Primary SpectroSERVER.

Environment

24.x and 25.x

Cause

 A timing conflict (race condition) occurs during the Secondary SpectroSERVER startup process. If the Secondary server completes model activation and device re-polling before the synchronization of the latest status flags (such as clear or suppression) is finalized, the Secondary server perceives existing alarm conditions as new, unacknowledged events and re-asserts them.

Resolution

This behavior is a recognized aspect of the fault-tolerant synchronization process. To minimize the likelihood of this timing conflict, verify the following:

1. Optimize Synchronization: Ensure network latency between Primary and Secondary servers is minimized.
2. Tune .vnmrc Parameters: Consider adjusting the following parameters in the $SPECROOT/SS/.vnmrc file to optimize the data volume exchanged during synchronization:
   • sync_all_ext_interface_attrs=false
   • int_copyattr_enable=true