We have a redundancy group with 1 element as primary and 1 element as backup. When the backup is in Timeout (e.g. due to missing communication) the redundancy group still shows, that the backup element is “available”, even though this is in fact not the case. This may be caused by the fact, that the element in Timeout still holds the values, that were polled from the data source, before it went into Timeout. These values may even match the switchover conditions.
A workaround to avoid switching to a element in timeout would be to add the “AND – element state – {backup} – not equal to -Timeout” to the switching logic. But this is only visible for the users with sufficient rights. A normal operator with “view only” rights would still see, that the backup is available for this particular redundancy group.
Is there any configuration, that I can add to tell the redundancy group, that the backup is “unavailable”, when it is in Timeout?
Hi André. As far as I know, there’s no such functionality available in the redundancy group configuration.
The closest you could probably get would be to set up a correlation rule on the timeout alarm to automatically put the backup element into “maintenance” mode (through an automation script). Having the device in maintenance mode will prevent the switching logic from using it and would also be visible in the redundancy state overview.