You can migrate secondary Access Manager Appliance using the existing IP address. Consider a scenario where Access Manager Appliance has three nodes, perform the following steps for migration:
Select one of the three nodes from the cluster. Do not select the primary node.
Delete the selected node from the cluster.
Remove any traces of the Access Manager Appliance replica from the primary console using the information in Prerequisites for Migrating Access Manager Appliance.
Clean up the eDirectory objects left in the environment.
Power off the system.
Install the Access Manager 5.0 Service Pack 1 Appliance using the IP address of the powered off system.
Add this as a secondary node in the current environment.
NOTE:It is recommended to use a different host name during the installation if you are planning to use the existing IP address. This is to avoid any failure because of remaining eDirectory objects in the primary console from the old node. To restore custom files, see Managing Configuration Files.
Perform the migration. The Access Manager Appliance 5.0 Service Pack 1 node will now be the primary node after the migration.
Switch off the other nodes one after the one after deleting from the cluster.
Perform a fresh install and add it to the existing cluster.
All the devices will now be on the Access Manager 5.0 Service Pack 1 version.
Perform the migration on only the first node of Access Manager 5.0 Service Pack 1 node and the remaining nodes must be freshly installed.
If you have multiple network interfaces configured in the existing appliance and want to keep all network interfaces in the migrated Access Manager Appliance, ensure that you have configured the required network interfaces in the virtual machine or physical machine before installing Access Manager Appliance.