Hei,
I have redundant front-end gateway with remote tag providers. The tag providers have a outgoing connection to master front-end gateway.
When the clients is connected to backup front-end the tags is not updating, and when I chech status for gateway network on the backup front-end it is not connected to the remote tag providers.
Do I have to set up a outgoing connection from the remote tag providers to the backup front-end also?
In this scenario it sounds like you still need to create an outgoing connection from the tag gateway to the front-end backup. It is the same process as creating an outgoing connection to the Master (but with a different Host).
Alternatively, you can swap the direction of the GAN connection. If the connection is outgoing from the Front-End Master > to the Remote Tag Provider Gateway: it will work on failover as you expect.
Hi,
Thank you for your feedback. I assumed that was the way it had to be done. Remote tag providers were installed before we installed backup front-end GW.
Would you recommend that I change direction on GNC, or is it ok to have it as is?
I'm having the same problem, but my master gateway is doing an outgoing connection to a second gateway. the backup gateway seems to be trying to do the same connection but it is just faulted. I attempted to swap the direction as suggested in this thread, to add an outgoing connection from the other gateway in to the backup gateway, but I can't approve the connection because of the error "can't make configuration changes on a non-master node". So I'm not sure how to fix this.
I believe the most common direction to go is the alternative I mentioned years ago:
Redundant Master >(Gateway Network Connection)> Tag Provider
because the connections made on the Master will copy to the redundant Backup. Which it sounds like you originally had, did you test failing over by shutting down the Master?