Hi,
We are trying to get an redundancy group working on Ateme. We have added same channel on both Atemes and the service is started at "Prime" and stopped at "Backup" and we are trying to get the redundancy to stop the main and start the backup if there will be any alarms at main.
We have done like this picture, are we totally on wrong way or?
Does any one have any examples how we shall configure this?
// Thomaz
The main wonky part here appears to be the "switching detection" condition, which is the condition that defines which device DataMiner sees as the operational one. These conditions get applied at any time, regardless of any switching logic defined. In the configuration from the screenshot, DataMiner will see the backup device as the operational one as long as it doesn't have any alarm event.
It's probably also not the best idea to trigger on alarm state here: if both devices have alarm states, the redundancy group will end up in limbo.
If there's any parameter through which you can know that a backup device is the operational one, my suggestion would be to put the switch detection on there. e.g. something like "when <service status> is <active>"
Also see Creating a redundancy group | DataMiner Docs . There's a video also on redundancy group configuration.
Another great video is the one from the Administrator training, Bert explains everything and shows a practical example on what do and don’t
https://community.dataminer.services/courses/dataminer-administrator/lessons/redundancy-groups/
As this question has been inactive for a long time, we will now close it. If you want further assistance, could you post a new question?