The SetDrsState SLNet Message is able to bring a DMA online (by force). This is to avoid disabling the Failover config but still be able to bring the DMA online. The option ForceEventWhenHeartBeatsFailing (bring a DMA online even when the heartbeats fail) combined with the BruteForce option. This option does the following:
- Restarts the DMA that is stuck going offline (via the batch files).
- Brings the DMA online without checking if the VIP is present.
This message should fix the following two scenarios:
- When the DMA is in RTE trying to go offline and is stuck.
- When another device has taken the VIP, we should still attempt to go online (however, this has some pitfalls; other DMAs won't be able to communicate with this DMA anymore as the VIP has been duplicated): you will see notices that heartbeats and syncing are failing and the DMA won't be accessible via the VIP.
You can find this message in the SLNetClientTest tool, by going to the "build message" tab page where you can search for this option, first I would do a ForceEventWhenHeartBeatsFailing; only if that one doesn't allow the DMA to start up, you can use the BruteForce option.