We have a variety of Ignition servers running in a hub and spoke model, with a centralized server serving as the proxy from all of the edge servers to an additional gateway that serves as the EAM controller:
Plant <------>
Plant <------> Central ---- EAM
Plant <------>
There is a firewall that prevents the Plant servers from directly accessing the EAM gateway, though we can see it via the Central Ignition proxy. Is there a setting that would force the plant-to-EAM connection to run through the Central gateway network configuration?
It sounds like you've already got this setup as you're describing. You might be able to verify it by looking at Gateway Network Live Diagram on one of the Plant gateways.
You can set the number of proxy hops on the Central gateway to 1, though like I said, it already sounds like you've done that. Additionally, I'd recommend configuring Proxy Rules on that Central gateway such that each plant gateway only sees Central and EAM gateways. This can help prevent extra service discovery and other chatter.
Once proxying is configured on Central, you should be able to configure the Plant gateways as EAM Agents.
Yes, I have proxy hops as 1, and tried 2 as well. When I try to configure the Plant server as an EAM agent, I can see my EAM controller as an option. But when I try to finish that setup, the connection times out. It’s like it is trying to direct connect without going through the proxy.