I have an Ignition 7.3.2 (b533) system and I want to set the system up with redundancy, I have a second server and second licence but can’t seem to get it to work. Both servers are in a DMZ and have a second NIC facing on to a domain that have a third public IP address for accessing the system. The following is a summary of what I have:
Server1 has two NICs:
NIC1 = DMZ_IP1
NIC2 = DOMAIN_IP1
Server2 has the same:
NIC1 = DMZ_IP2
NIC2 = DOMAIN_IP2
So I’ve tried setting up the redundancy with the auto detect on everything selected and with binding the interfaces - all that happens is that the backup node appears for a few seconds, then disappears. It does this for 3 or 4 times then it shuts down the ignition service on the backup machine.
Also when I have server1 set up as a master I can’t launch the client or designer from outside the domain (ie, via the Public IP address)
I get the entries below in the console. ( I have since added the Modbus module that was causing the imcompatible module manifest but I haven’t tried the redundancy since )
Could the imcompatible module manifest have caused the redundancy to fail?
Is the problem to do with the fact that the public IP address is being used to access the system?
What settings should I have for this knid of system?
(I) 11:23:15 MasterTCPChannel (id=101) Shutting down channel.
(I) 11:23:15 MasterTCPChannel Error occured while communicating with backup client. Client has likely become unavailable.
(I) 11:23:14 MasterTCPChannel (id=102) Shutting down channel.
(I) 11:23:13 MasterStateManager System UID has been updated to ‘c7cb287a-ecc8-4a87-853a-6713a0f98256’
(I) 11:23:08 ENGINE Successfully backed up instance ‘settings’ to ‘C:\Windows\System32\config\systemprofile\AppData\Local\Temp\tempdir1833838871640661806340882722101\db_backup.tar.gz’
(I) 11:23:04 ENGINE Initiating backup of instance ‘settings’
(I) 11:23:04 ENGINE dataFileCache commit start
(I) 11:23:04 ENGINE Checkpoint end
(I) 11:23:04 ENGINE defrag end
(I) 11:23:04 ENGINE open end
(I) 11:23:04 ENGINE open start
(I) 11:23:03 ENGINE dataFileCache commit start
(I) 11:23:03 ENGINE defrag start
(I) 11:23:03 ENGINE Checkpoint start
(I) 11:23:03 MasterStateManager Backup node has requested a ‘full’ restore.
(I) 11:23:03 MasterTCPChannel System restore initiated by backup node. System will provide a ‘full’ restore file.
(I) 11:23:02 MasterStateManager Successfully registered new connection to redundant master from ‘/10.49.31.83:49600’
(I) 11:23:02 MasterTCPChannel Starting redundancy channel id 102
(I) 11:23:02 MasterTCPChannel (id=102) Connected to address ‘/10.49.31.83’
(I) 11:23:02 MasterTCPChannel Backup node’s module manifest is incompabile with the master’s. A full backup will be performed. Value: [(fpmi/5.3.2 (b301)), (fsql/5.3.1 (b86)), (help/1.3.1 (b127)), (mobile/1.3.1 (b55)), (modbus-driver2/2.3.2 (b166)), (rept/1.3.2 (b46)), (siemens-drivers/1.3.1 (b110)), (symfact/2.5.1 (b26)), (udp-driver/1.3.1 (b64)), (xopc/1.3.2 (b317)), (xopc-drivers/1.3.2 (b148))]
11:23:02 MasterTCPChannel The module ‘modbus-driver’ is missing from the backup system.
(I) 11:23:01 MasterTCPChannel Peer node information has been updated: ClusterNode(address=10.49.31.83, httpAddresses=[10.49.31.83:8088/main], sessionCount=0, loadFactor=1, activityLevel=Cold)
(I) 11:23:01 MasterTCPChannel Reporting master start time of Tue Feb 14 11:22:08 GMT 2012
(I) 11:22:59 MasterStateManager Successfully registered new connection to redundant master from ‘/10.49.31.83:49599’
(I) 11:22:59 MasterTCPChannel Starting redundancy channel id 101
(I) 11:22:59 MasterTCPChannel (id=101) Connected to address ‘/10.49.31.83’
(I) 11:22:25 MasterStateManager Join-wait time has expired, will refresh system state.
(I) 11:22:21 MasterTCPChannel (id=99) Shutting down channel.