Override ActiveGate connection behaviour

[andrew_patterso]

Hi all,
I am wondering whether it's possible to override the behaviour where an AG gets a list of cluster IPs when it first connects?

We have a situation where we have 2 datacentres, the cluster in 1 (DC1) and an AG in the other (DC2) - there are other AGs and agents in different locations, but this is irrelevant to the scenario. The IP addresses where the cluster resides (DC1) is not resolvable from DC2. We can't set up a public AG in DC1 that is exposed to DC2 as it is time and effort prohibitive.

What we would like to do is use their current method of cross-DC connections which would look something like:

AG -> VIP pool -> cluster

Even if we could tell the AG to send to the cluster domain, this would be sufficient since we could add a hostfile translation for the above.
We don't want to override the node endpoint value from the cluster since we only want to update to connection for the AG in DC2.

Any thoughts?

Andrew

[Julius_Loman · Accepted solution]

I don't think this is possible with current versions. You can override the list at installation time, but the list will get updated from the cluster as soon as the gateway (or agent) connects.

But the list normally contains both IP addresses and hostnames. So if you override the IPs using hosts file on the gateway, this should work. But it will still try to connect also via the real IP addresses from the list. If you want to prevent the GW from trying the (nonworking) IP addresses, you will have to block it using local firewall (iptables / windows firewall).