Does Ignition have a viable network architecture setup similar to this one from VTScada?
I'm thinking this one is the closest that I can find mentioned, can anyone confirm this would work for the application above?
Such a system would be vulnerable to split-brain on comms loss. Any device polling over the VPN would likely be pathologically slow. I don't see how VTscada would avoid the same issues.
Do you know of a good way to accomplish something similar? What if the two plants were connected by fiber and the vpn wasn't necessary? Split brain is still too much of a problem?
Split-brain isn't a latency issue, but a conflicting master issue when comms are out longer than the switchover delay.
When comms goes down, you aren't going to be able to poll the other site anyways, though. I'd just use two normal Ignition instances.
I wouldn't physically separate an Ignition redundant pair unless there was a redundant comms path between the two sites, and that comm setup's "healing" delay was substantially less than (2x ish) the Ignition fail-over delay.
Apologies for the confusion, I was just wondering if we eliminated the slow polling downside to this architecture, would the split-brain issue still be enough to recommend against it? Sounds like the answer is yes.
How would you recommend having both the WTP and WWTP info displayed at both plants? Gateway to gateway communication with no expectations of any redundancy?
If useful to the operators, sure.
1 Like