ADDER Infinity - Appendix C - Redundant Servers: Setting up and Swapping out; Setting up A.I.M. Server Redundancy; Operation of Redundancy

49
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
APPENDIX C - Redundant servers: Setting up and swapping out
This appendix contains two main sections related to the creation and repair of A.I.M.
server installations that employ redundancy.
• Setting up A.I.M. server redundancy - below
• Swapping out an A.I.M. server - on next page
Setting up A.I.M. server redundancy
This section details the steps required to successfully congure two A.I.M. units as
primary and backup servers.
1 Set the Rôle entry to Primary on the primary server.
2 Congure its Ethernet port 1 Address.
3 Ensure that password requirements is set to NO.
4 Add the new secondary A.I.M. server to the network. The secondary server must have
the same license as the primary. It is not possible to have two servers with different
licenses in a cluster. This unit must have its factory default settings in place. The new
server will appear within the main Servers tab and be identied as being Uncongured.
5 Wait ve minutes for automatic server replication to take place and the backup
database to be transferred from the primary unit. After this period, the new secondary
server will be added to the list on the main Servers tab. Its Rôle will be shown as
backup and its Status as standby.
Note: If the transfer of the backup database is interrupted and only a partial database is
transferred, then the problem will be reported within the management server page. If this
occurs, it will not be possible to log in to the backup database and the rmware version of
the backup will be reported as V. After ve minutes, you should be given the options of Reboot
and Factory Reset. Choose the Factory Reset option in order to clear this issue.
6 You can now congure the secondary server in either of two ways:
• Click the
icon to congure the server remotely from the primary server.
• Click the icon to open a restricted page in order to congure the server
directly from its own IP address. If you use this option, the conguration options are
limited to: view the logs; update/reset AIM and congure this server.
Operation of Redundancy
If the Primary server fails for any reason (for example, loss of power or a network
issue) then the secondary server will failover. This will happen automatically without
any user intervention, however it is not instantaneous. The failover time required is the
value entered in the primary timeout plus 30 seconds for the process to happen. The
AdderLink Innity extenders will start communication with the second IP address that is
stored in their conguration and the redundant server will take control of the AdderLink
Innities. When the redundant server is acting as the primary it is not possible to add any
new devices or change the conguration. If this is required then the backup server can be
promoted to be the primary.
When the primary server comes back online then it will resume its role as the primary.
If however the backup server has been promoted to primary, when the primary server
comes back its role will need to be factory reset back to the backup. After doing this the
AdderLink Innity endpoints will need to be rebooted. It is not possible to have two
primary servers on the same network.
Both the primary and the backup server periodically synchronize their databases to
ensure that they are identical. If for any reason the backup server is powered down then
any changes to the system conguration will not be maintained by the backup server.