FAQ: Initialization of Internal variables (Network) in Dominant redundancy mode.
When (re-)starting the dominant Server 1, regardless of their 'Remanence' configuration, internal variables with calculation in 'Network' are initialized first in the dominant Server 1 and only after synchronized with the running Server 2. Modules linked to these variables react to the initialization values in the dominant Server 1.
For example, the same alarm can be cleared and activated twice when restarting the dominant Server 1 while the Server 2 is running:
- Service Engine Server 1 is stopped.
- A new alarm of an internal variable (Network) is triggered (managed by Server 2).
- Restart of the Service Engine in Server 1.
- Server 1 initializes its internal driver queue as configured in the 'Remanence' property (Off, initial value or Remanent) and transfers the respective values to the Service Engine. -> The current alarm is cleared.
- Service Engine Server 1 synchronizes the value of the internal variable (Network) with the Server 2. -> A second alarm is triggered.