Can anyone provide guidance on how to set up redundancy for two Niagara N4 Supervisor stations on the network? I’m looking for insights on best practices or if anyone has already implemented this type of redundancy. Also, is a specific redundancy license required for this configuration, or does the standard licensing cover it?
1 Like
Here is the documentation you need
docJaceRedundant.pdf (981.3 KB)
3 Likes
I had no idea you could do this. That’s awesome!
Lol yeah was new info for me too. Was in the middle of writing a long post about how you could set up multiple supervisors. Got a work call and when I returned to the post, Jedi Master Johnson had answered with the correct way to do it 
3 Likes
I used to have to do this the hard way, like making a value and having it read from the other server and if didn’t return, fail the supervisor or Jace. This service is noice
1 Like
I was also unaware about the JACE redundancy. I had a large site that required the supervisor to be redundant and we used Stratus Everrun. This service allows for two separate servers to act as a single supervisor. This allows the the two servers to have a single IP address so you don’t have to manage trying to switch the IP address. Since the two supervisors act as a single supervisor, you just process with licensing the same way you would for a single supervisor. Using Stratus made it to where we didn’t have to do anything different than we would do with just a single (non-redundant) supervisor.
2 Likes
Where can i find redundancy jar file module?
1 Like
Does this work for the Niagara Network as well. I read the documentation and it seemed to be geared toward BACnet.