Context: While trying to trouble shoot a remote tag provider on an Ignition Edge installation, I ran into an issue with duplicate remote gateway connections.
I'm trying to trouble shoot an issue with a remote gateway for an Ignition Edge install. When I go Status > Gateway Network, under remote gateways I see two remote gateways with the same name but one of them has a status Defined_NeverConnected status:
Under Config > Networking > Gateway Network, under the Outgoing Connections page, I see only one outgoing gateway connection set up:
Can someone explain why I'm getting two remote gateways in my status screen? I think this issue is interfering with my Edge install's ability to push historian data to the remote gateway.
Hey! Thanks for reaching out. This issue has been around for a bit and something we're currently tracking. The issue you're seeing can manifest a few different ways, mostly when a connection gets added, and then deleted, but the old ones never clear out. I'm going to guess the gateway name changed at some point, given I see it was the same name but with different casing. I've added your post to our tracking system to help bring more visibility to this. I'll update the title with the ticket number too. As a heads up, this fix is currently something we're eying for 8.3, and I'm unsure if it will be back-ported to 8.1.
What sort of issues or errors are you seeing when trying to push historian data to the remote gateway? There should also be some extra information in the logs to help us decipher what's going on. This duplicate connection error you're seeing shouldn't be part of the problem and has been shown to only affect the UI.
Hello! The original issue I was trying to solve was troubleshooting why my historian didn't seem to be working. There's two gateways that I think are relevant here:
Ignition-THEIH01 (Standard Ignition Install, this is where my project files are)
Ignition-THEDFT9ZC14 (Ignition Edge Install, this is where the EdgeTeddy2 tag provider lives)
Looking on the Gateway web pages for both Gateways they look like they are connected:
But I'm running into an issue where I can't seem to query for tag history via a qualified tag path for the tags in the EdgeTeddy2 provider. Below is a screenshot showing that history is enabled on the tag I'm querying for and some tests where I was querying for tag history with the standard tag path and the qualified tag path. Using the standard path I'm getting the results I expect but using the qualified path returns nothing. Additionally I even used a browseHistoricalTags query to see all tag paths on that history provider and I did not see EdgeTeddy2.
Looking at the logs for Ignition-THEDFT9ZC14, I think I can see some warnings about connectivity issues:
Probably haven't constructed the /drv: section correctly. It needs to use the source gateway name and the source tag provider name. Not the name of the remote tag provider.
And forgive me for asking what might be a dumb question, is the Service Security and Edge sync services configured to match the standard gateway? Right under the Config > Data Sync > Settings page.
I'm currently using this as the fully qualified tag path:
histprov:QueryIgnitionHistorian:/drv:Ignition-THEDFT9ZC14:EdgeTeddy2:/tag:strSerialNumber
This tag provider was set up on Ignition-THEDFT9ZC14 and the provider is EdgeTeddy2 so shouldn't the above be correct?
Yes.
So, not syncing at all. 
I've not run into the stale connection situation you have, but seems likely related. Perhaps it's time to open a ticket to get help clearing that (filesystem resource surgery, I suspect).
Thank You for the quick response. I'll open a ticket to see for this.
Not a dumb question. I believe they should be matching.
Edge Data Sync:
Standard Gateway:
Checking the Incoming and Outgoing for both gateways, the two appear to be connected:
If the Service Security is setup to allow this on both gateways and it still doesn't work, I think opening a support ticket is best path going forward. They'll be able to help with a deeper dive and figure out what might be going wrong
