# Gateway Network, Tag Read **URL:** \ **Category:** Ignition\ **Created:** [July 2, 2025, 8:42pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074 "2025-07-02T20:42:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nicholas.gutt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.gutt/32/25670_2.png) [@nicholas.gutt](https://forum.inductiveautomation.com/u/nicholas.gutt)\ **Post date:** [July 2, 2025, 8:42pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/1 "2025-07-02T20:42:36Z")
I have 2 gateways: Gateway A has an ABB IOT OPCUA Server connection and works great. Gateway B needs to read tags from Gateway A ABB IOT OPCUA Server. Gateways A & B are both 8.1.17 Gateways A & B are both agents in a gateway network with EAM. From Gateway B: Can ABB IOT OPCUA Server on Gateway A be read WITHOUT sharing a remote tag provider over gateway network? Nick ---
**Author:** ![brian.mcenulty](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@brian.mcenulty](https://forum.inductiveautomation.com/u/brian.mcenulty)\ **Post date:** [July 2, 2025, 8:50pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/2 "2025-07-02T20:50:25Z")
> [@nicholas.gutt](#): > > Gateway B needs to read tags from Gateway A ABB IOT OPCUA Server. > Gateways A & B are both 8.1.17 > Gateways A & B are both agents in a gateway network with EAM. > > From Gateway B: Can ABB IOT OPCUA Server on Gateway A be read WITHOUT sharing a remote tag provider over gateway network? A remote tag provider connection would be the logical implementation for what you're trying to do. Is there a reason you don't want to use it? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 8:58pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/3 "2025-07-02T20:58:39Z")
The gateway network will support just the remote tag provider. You could use OPC or MQTT outside the GAN if necessary. ---
**Author:** ![nicholas.gutt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.gutt/32/25670_2.png) [@nicholas.gutt](https://forum.inductiveautomation.com/u/nicholas.gutt)\ **Post date:** [July 2, 2025, 9:00pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/4 "2025-07-02T21:00:47Z")
I understand. We are executing some architecture changes and I am trying to avoid technical debt. Also, I feel like I have seen remote tag reads across the gateway network being done before, but I might be mistaken. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 9:02pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/5 "2025-07-02T21:02:34Z")
Well, you could place a message handler in a project in gateway A that gateway B could call to delegate selected operations and return the results. ---
**Author:** ![nicholas.gutt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.gutt/32/25670_2.png) [@nicholas.gutt](https://forum.inductiveautomation.com/u/nicholas.gutt)\ **Post date:** [July 2, 2025, 9:07pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/6 "2025-07-02T21:07:40Z")
Message handler is an interesting idea. I might try a message handler for my own education. Seems the easiest way is to create a tag provider on gateway A, share to Gateway B and suck up the technical debt. Appreciate the feedback! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 9:11pm UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/7 "2025-07-02T21:11:15Z")
> [@nicholas.gutt](#): > > create a tag provider on gateway A ? Do you not already have tags in A pointing at the ABB device? If so, you just need an RTP in B to point at that one in A. Perhaps add more tags to the TP in A to expose to B. If there is no OPC client connection in A pointing at the ABB device, perhaps you should just make that new connection directly over your WAN (VPN, presumably) to the ABB device. ---
**Author:** ![nicholas.gutt](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.gutt/32/25670_2.png) [@nicholas.gutt](https://forum.inductiveautomation.com/u/nicholas.gutt)\ **Post date:** [July 3, 2025, 1:16am UTC](https://forum.inductiveautomation.com/t/gateway-network-tag-read/108074/8 "2025-07-03T01:16:21Z")
Gateway A is in a segmented OT network. Gateway B is on enterprise WAN network. Devices from OT network are permitted to communicate with Gateway B (bad I know). All currently used tag providers are on Gateway B with the exception of ABB IOT Server tags. We are auditing, deleting, updating projects on Gateway B. End game is reworked projects end up on Gateway A inside the segmented OT network. Gateway A does have an ignition tag provider setup with tags from ABB IOT Server connection. Those tags are shared via GAN to Gateway B. However, those tags are hap hazard and I do not want to build from the existing provider. Thinking about the situation more, I think connecting OT devices to Gateway A and build new tag providers. Once complete I can share the providers to Gateway B for reworked projects to leverage. Once the projects are reworked and Gateway A is ready for prime time, make the transfer of projects. The tag providers will already be on Gateway A.