I am having success if i forward measurements from
OpenHistorian -> SIEGate(internal subscription) ->internet -> SIEGate(TLS Subscription)->OpenHistorian(Internal)
with a mixture of internal subcription and gateway using TLS subscription.
I am having trouble forwarding measurements to a 3rd SIEGate as in this example
SIEGate->SIEGate(internal subscription)->Internet->SIEGate(TLS Subscription)
In this case the 2nd SIEGate receives all the data, but the 3rd one receives nothing, but there are no errors and there are messages about metadata refresh being successful etc. Note this is almost identical to the working example above with data originating from SIEGate instead of OpenHistorian.
Now this works all the way to the last SIEGate
But this doesn’t
The last SIEGate doesn’t receive any data, but no errors or warnings.
This also doesn’t work
The SIEGate with the 2nd TLS subscription doesn’t receive data.
If I pick subscriber status, all the connections have the green light and Stream statistics shows that connection is TRUE.
This all seems to indicate you can only forward data once to another SIEGate but no more?
Is forwarding to a 3rd SIEGate possible, and if so is there any difference in setup after you go past 2? Ive basically been doing the same publisher/subscriber routine for each of the 2 pairs of SIEGates. That is the 1st publishes to the 2nd, and the 2nd publishes to the 3rd, the 3rd subscribes to the 2nd, and the 2nd subscribes to the 1st.
I tried this with OpenHistorian as well(latest stable build) and that also didn’t work, but also gave some errors, so I have gone back to SIEGate.