RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.7 Service Pack 1

There is an instance where the upgrade from RSA Authentication Manager 8.7 to RSA Authentication Manager 8.7 SP1 fails and the Authentication Manager instance is left with a GRUB prompt. 

• An unknown or outdated rpm package where SUSE prompts for request to update rpm.
• SUSE is prompting for a request to update an .rpm where an unknown or outdated .rpm package is present on the server.
• RSA Support has not been able to recreate the issue.

Please contact the RSA Customer Support team if you have any questions with the workaround provided. 

1. Promote an existing replica instance in the Authentication Manager deployment to be a primary instance.
2. Upgrade the promoted replica instance (now a new primary instance) with RSA Authentication Manager 8.7 SP1 software. Where the Authentication Manager deployment has one or more replica instances then apply the RSA Authentication Manager 8.7 SP1 software to each replica instance, one at a time.
3. Deploy and attach a new RSA Authentication Manager 8.7 SP1 replica instance that matches the hostname and network configurations of the primary instance that failed the upgrade.
4. Promote the replica instance (using the hostname and network configurations of the primary instance that failed the upgrade back) to be a primary instance.

Be sure to watch output from the DRAC to get additional details on the upgrade. The TSE assigned to your case may request the file(s).

Online References

Promotion for Maintenance at URL https://community.rsa.com/s/article/Promotion-for-Maintenance-91b2cbc6

NOTE: This procedure is used to change the identity of the instances in an Authentication Manager deployment. For example, a replica instance becomes a primary and the original primary is demoted to a replica instance.

Replica Instance Promotion for Disaster Recovery at URL https://community.rsa.com/s/article/Replica-Instance-Promotion-for-Disaster-Recovery-7391071a

NOTE: Promoting a replica instance for disaster recovery will delete the malfunctioning primary instance from the Authentication Manager deployment. Should the primary instance be shutdown to perform the replica promotion for disaster recovery then that primary becomes standalone and you would end up with two primary instances. The original primary and a promoted replica instance as a primary.

Generate a Repllca Package - URL https://community.rsa.com/s/article/Generate-a-Replica-Package-67022165

Attach the Replica Instance to the Primary Instance - URL https://community.rsa.com/s/article/Attach-the-Replica-Instance-to-the-Primary-Instance-b6f63997

Documentation References

RSA Authentication Manager 8.7 SP1 Setup and Configuration Guide - URL https://community.rsa.com/s/article/RSA-Authentication-Manager-8-7-SP1-Setup-and-Configuration-Guide

• Chapter 2 : Deploying a Primary Appliance
• Chapter 3 : Deploying a Replica Appliance