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 RSA SecurID Software Token 2.4 for iOS Quick Start (Italian) 4Number of Views RSA MFA Agent 3.0 for Microsoft AD FS Release Notes (Italian) 6Number of Views Unable to join a new cluster to a group; no failures are reported when joining the clusters 33Number of Views Unable to create schema. (class java.sql.SQLSyntaxErrorException: ORA-00959: tablespace 'INDX_256K' does not exist) initia… 20Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators