Applicable Systems
Wonderware System Platform
Symptoms
The Wonderware System Platform reports a redundancy switch failure. The failover from the primary to the backup Galaxy node did not complete successfully during a planned or unplanned switchover.
Possible Causes
- The backup Galaxy node was not synchronized with the primary, causing a state mismatch during failover
- Network heartbeat between primary and backup nodes was lost, triggering an unintended switchover
- The backup node application engine failed to start due to a corrupted checkpoint file
Troubleshooting Steps
- Step 1: Check the synchronization status between primary and backup nodes in the Galaxy
Synchronization is complete and both nodes show the same checkpoint sequence number - Step 2: Verify the heartbeat network is functional by pinging between the two nodes
Ping round-trip time is under 50ms with no packet loss, confirming a healthy heartbeat path - Step 3: Inspect the backup node application engine startup log for checkpoint errors
Checkpoint loads successfully and the engine reaches Running state within 30 seconds
How to Reset
To reset: 1) Resolve the checkpoint corruption on the backup node. 2) Force a full synchronization from the primary. 3) Re-initiate the redundancy switchover. 4) Verify the backup node becomes the active primary.
Comments (0)
Share your experience to help others facing the same problem.
Leave a Comment
Source: Wonderware System Platform Manual, AVEVA (formerly Wonderware)
Category: SCADA
No comments yet. Be the first to share your experience!