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?
? 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.
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.