How to add a standby appliance to an single primary running 2.7 SP1?
For the steps below, rkm1 is considered the existing Primary appliance running 2.7 SP1, and rkm2 is the new standby appliance to be added to the cluster.
1. Re-image rkm2 using the 2.7 Appliance ISO. If a failed installation already occured, you can simply run the script /opt/rsa/setup/uninstall to revert back to 2.7.
2. Run the install script in /opt/rsa/setup, and select the option to install a single secondary. Follow the steps as if you were doing a normal standby installation.
3. Download the 2.7.1.2 migration utility. Follow the normal steps to upgrade the appliance to 2.7 SP1 up to the reboot.
4. After the reboot, verify that rkm2 is running as a primary. If it is not, download the cs_scripts_addons.tgz scripts (contact RSA Support) and run /opt/rsa/setup/sh/cs_switchover.sh. This will switch the roles so that rkm2 will now be running as a Primary.
5. Keep going with the Post-Restart steps from the migration guide.
Once completed, verify via the DB Status pages (/status/db) that everything is running as expected.
Related Articles
How to replace a 2.5.0.3 standby appliance with 2.6 appliance in a cluster? 26Number of Views Authentication Manager Log Messages (26151-26185) 26Number of Views Authentication Manager database services do not to start after power outage 189Number of Views Error "Warning NTP and VM Host TimeSync should not be enabled at the same time" in RSA Authentication Manager 93Number of Views '[Ljava.lang.StackTraceElement;@382839bd 0 [main] ERROR com.aveksa.cli.BaseExecCLIModule' error backing up (exporting) th… 485Number of Views
Trending Articles
Troubleshooting RSA MFA Agent for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Deploy an Identity Router Virtual Machine in Microsoft Azure How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device