Issues syncing Tag History from Ignition Edge to Standard Gateway (History Sync)

Ignition
,
1

Hi everyone,

I'm having trouble synchronizing tag history from an Ignition Edge (v8.3.1) to a central Ignition Standard Gateway.

Current Architecture:

  • Edge Gateway: Has a local historian named edHistorian.

  • Standard Gateway (Name: igResidual): Has a Historian Splitter named pgHubSpoke (which points to a local SQL DB and a remote Hub).

  • The Gateway Network connection is established and "Running" between both nodes.

The Issue: I have configured the Edge Sync Settings to point to the Remote Gateway igResidual and the Remote History Provider pgHubSpoke. However, data is not flowing and I see the following symptoms:

  1. Logs in Edge: I see I/O exception (org.apache.http.NoHttpResponseException) when trying to reach the Standard Gateway on port 8060.

  2. Store & Forward: On the Edge side, I see many data points going into Quarantine.

  3. Logs mention: Historian syncable 'edHistorian' is starting. Will synchronize data to remote historian 'pgHubSpoke' on server 'igResidual'.

What I've checked so far:

  • The System Name of the Standard Gateway matches the "Remote Gateway Name" in Edge Sync Settings.

  • The provider name pgHubSpoke exists and is running on the Standard Gateway.

  • The Tag History module is running on both Gateways.

Questions:

  1. Are there specific Service Security settings in the Standard Gateway (under Gateway Network Services -> History Sync) that I should verify beyond setting the Access Level to "Allow All"?

  2. Does the fact that the remote provider is a Historian Splitter instead of a direct SQL Historian affect the Edge Sync capability?

  3. Why would I be getting NoHttpResponseException if the Gateway Network status shows as "Connected"?

Any advice on how to debug the quarantine or the connection would be greatly appreciated. Thanks!

2

That suggests that the gateway network is not set up correctly.

Also, is the central gateway also v8.3? If not, it won't work at all.

3

Yes, both Gateways are running in version 8.3