Please refer to diagram below for reference.
A bit of explanation on the diagram.
- 1a and 1b are gateways forming a redundant gateway pair. ‘a’ is master, ‘b’ is backup.
- 2a and 2b are gateways forming a redundant gateway pair. ‘a’ is master, ‘b’ is backup.
- 3 and 4 are independent gateways.
- The arrows indicate how the gateway network connections are established.
Here’s the issue I’m running into:
I would like to have gateway 1 be able directly access the history, tags, and alarm providers running on gateway 4. As it stands:
- Gateway 1 is able to talk to gateways 2 and 3.
- Gateway 2 is able to talk to gateways 1, 3, and 4.
- Gateway 3 is able to talk to gateways 1, 2, and 4.
- Gateway 4 is able to talk to gateways 2 and 3.
- All gateway network connections are configured to act as proxies.
Gateway 1 is used as my primary Ignition server. It talks to all my PLCs, historizes the data, feeds the visual interface for operators, etc… I need to be able to configure a remote history provider on gateway 1 that is mapped directly to a history provider on gateway 4, so I can push history from gateway 1 to gateway 4 via a history tag splitter on gateway 1. Right now, I have to setup a history provider on gateway 3, push from gateway 1 to gateway 3, then have gateway 3 push to gateway 4. The same scenario will be true for the alarm provider. This will force me to procure an additional set of licenses for gateway 3, in addition to the historical provider and alarm provider licenses that will be necessary for gateway 4. All I need is gateway 1 and 4 to have those capabilities. Gateways 2 and 3 are only in the picture to act as gateway network proxies due to IT required network segregation rules I have to work with, but I can’t get gateway 1 to talk directly to gateway 4.
Is that a gateway network limitation? Only meant to be able to talk to another gateway once or twice removed, but not thrice?
I am running Ignition 7.9.9 on all those gateways.
I would appreciate any insight in the matter.