Table of Contents
Advertisement
APPENDIX C - REDUNDANT SERVERS
This appendix contains two main sections related to the creation and repair of iPATH Agility Controller installations that employ
redundancy.
• Setting up iPATH Agility Controller redundancy - below
• Swapping out an iPATH Agility Controller - on next page
C.1 SETTING UP IPATH AGILITY CONTROLLER REDUNDANCY
This section details the steps required to successfully configure two iPATH units as primary and secondary servers.
1 Set the Role entry to Primary on the primary server.
2 Configure its Ethernet port 1 Address.
3 Ensure that password requirements is set to NO.
4 Add the new secondary iPATH Agility Controller 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 identified as being Unconfigured.
5 Wait five 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 Role 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
firmware version of the backup will be reported as V. After five 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 configure the secondary server in either of two ways:
• Click the
icon to configure the server remotely from the primary server.
• Click the
icon to open a restricted page in order to configure the server directly from its own IP address. If you use this
option, the configuration options are limited to: view the logs; update/reset the iPATH Agility Controller and configure this
server.
C.2 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 Agility extenders will start communication
with the second IP address that is stored in their configuration and the redundant server will take control of the Agility units.
When the redundant server is acting as the primary it is not possible to add any new devices or change the configuration. 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. 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 configuration will not be maintained by the backup
server.
70
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
Advertisement
Table of Contents
