Table of Contents
Advertisement
iPATH Agility Controller
C.3 Swapping out an iPATH Agility Controller
Once Agility devices have been configured to run with an iPATH Agility Controller, their default IP addresses are automatically
changed as part of the installation process. In this state the Agility devices become undetectable to any new iPATH Agility
Controller that does not have access to the database of devices. Therefore, if an existing iPATH Agility Controller needs to be
replaced within an installation, follow one of the basic procedures given here to smooth the transition.
The correct procedure to use depends on whether you are using a solo iPATH Agility Controller (firmware versions below 3.0 can
only be used as solo servers) or a pair of iPATH Agility Controllers in a primary/backup redundancy arrangement:
C.3.1 For solo iPATH Agility Controllers (and those with firmware below v3.0)
1 Before connecting the new iPATH Agility Controller to the main network, connect the new iPATH Agility Controller to a
network switch that is isolated from the main network.
2 Use a computer connected to the same switch to login to the new iPATH Agility Controller management suite.
3 Ensure that the new iPATH Agility Controller is running the same firmware version as the one being replaced (upgrade if
necessary). The firmware version is shown in the top right hand corner of every page of the management suite.
4 Set the IP address of the new iPATH Agility Controller to match that of the original unit.
5 Restore a backup file of the original iPATH Agility Controller database to the new device.
6 Remove the original iPATH Agility Controller from the network. Connect the new iPATH Agility Controller in its place and power up.
7 With firmware 4.0, if the solo server is replaced, you need to perform a factory reset on all Agility units. This is because the
Agility units need to inherit the security certificate of the new iPath unit.
The replacement unit will now work directly with the installed Agility units.
C.3.2 For dual iPATH installations using redundancy
The correct procedure depends on which iPATH Agility Controller has failed:
Primary server failure
1 Promote the backup server to be the primary server.
2 Replace the faulty primary iPATH Agility Controller with a replacement unit.
If the replacement iPATH Agility Controller has a firmware version below 3.0 then contact it on the 169.254.1.3 address and
upgrade to 3.0 (or above). After the upgrade, reboot the unit.
3 The replacement server should begin communicating with primary server and download the database so that it can operate as
the backup server.
Backup server failure
1 Replace the failed backup server with a new unit that has firmware version 3.0 or greater and has its default factory settings in
place.
2 The replacement server should begin communicating with primary server and download the database so that it can operate as
the backup server.
C.3.3 Starting from scratch
If none of the above procedures are used, then the following will be necessary. This will require a certain amount of effort
because each Agility unit must be visited and reset, plus the iPATH database will need to be fully reconfigured.
1 Place a new iPATH Agility Controller into the network and then perform a factory reset on every Agility device. This will force
the Agility units back to their default states whereupon they will announce themselves to the new iPATH Agility Controller.
2 Use a computer connected to the same network to login to the new iPATH Agility Controller management suite and begin to
recreate the database of devices and users.
Page 70
724-746-5500 | blackbox.com
Advertisement
Table of Contents
