RDM Alternative Gateway Settings

Hi James,
Thanks for your question.

In RDM, Alternative Gateways are meant to be used only when the preferred (primary) gateway is completely unreachable. However, there are a few key things to keep in mind regarding how and when failover occurs:
Conditions for Alternative Gateway Selection:

1- Network-Level Unreachability
RDM will only switch to an alternative gateway if the primary one is unreachable at the network level (e.g., no response on the IP/port, connection timeout).

• If the service is stopped but the port is still open or accessible (e.g., firewall/router still responds), RDM may still try to connect to the preferred gateway.
• DNS resolution and cached routing can also influence this behavior.

2- Fallback is not Instant or Interactive
The fallback mechanism is not dynamic or load-balanced. It is a failover-only behavior, not a selection menu.
3- Manual Gateway Selection (Choose from List)
When selecting from the list manually, the gateway is chosen, but if the session or entry itself is still tied to a specific Gateway ID, that may override the manual selection. Also, the manual selection applies per launch and does not persist.
4- Duplicate Entry Behavior
If you’ve created a separate entry with the same target IP but no fallback configuration, it may bypass the preference logic and connect directly using that specified gateway which is why it’s working.

Hi Michel,

You're point is clear in 1 and 2 enough. I've waited > 1 day with the service disabled. Additionally the GW has since reported into hub as down. The entry doesn't seem to use the failover gateway.

re: point 3: The entry is set to inherit from folder. Which is configured to prompt for the list. The list appears but it does not appear to use the chosen gateway. No error is made visible to the user. Is there a log I can check to determine what is happening?

re: point 4. I mention I have duplicate entry in the vault without gateway failback configure using the same gateway I picking from the list. Only to point out that the target asset it available from that gateway and works when gateway failback configuration is not in play. This duplicate entry doesn't affect the entry in point 3 - because that one is not connecting successfully or doing anything at all really.

Thanks,

James

Hello James,
Thank you for your feedback I would suggest you to send us email on service@devolutions.net as troubleshooting here is not possible.

Best regards,