After 7 month of doing siemens TIA I might possibly be doing Ignition perspective project 
Can you please share your tips and tricks, gotcha regarding redundancy?
Redundancy will be used for running perspective with dashboard functionality and no critical control.
1: Forgive me if I am not precise but i believe there are 2 types of clients - thick (normal or low spec pc) and thin (needs server to operate) - what will happen if 1 gateway fail - will redundancy swap the path and allow both types (thick and thin client) to automatically reconnect ?
2: how quickly can redundancy kick it - will somebody notice it happened at all?
Best Regards
Hello,
Here are some tips that are commonly overlooked when configuring redundancy:
- Make sure both gateways are on the same versions of Ignition.
- Setting the Standby Activity Level to warm would allow the system to run as if it were active, with the exception of logging data or writing to devices, allowing for faster fail-over.
- Test failover in a development gateway before putting it into production.
- System configurations like database and opc connections must use explicit IP addresses instead of "localhost" for the master and backup gateway.
In theory, a failover event should occur fairly quickly, although the speed can vary from system to system. That's why it's crucial to test failovers in a development gateway.
A failover event is seamless for users since the perspective session would automatically change it's path to the backup's gateway without refreshing.
Can you give a specific example of thick and thin clients that you are concerned about in a failover event?
Helpful Docs:
1 Like