After moving an RSA Authentication Manager 8.x virtual appliance from one ESX host to another, AM services could fail to start because the system fingerprint has changed.

1. attempt to start AM services after the VM move between ESX Hosts
2. If Services fail to start, reset system fingerprint

Usage

1. Using the steps in 000038244 - SSH to an RSA Authentication Manager server, use the rsaadmin account to logon to the operating system hosting the Authentication Manager instance.

login as: rsaadmin
Using keyboard-interactive authentication.
Password: <enter operating system user password>
Last login: Fri Sep 18 18:18:20 2019 from jumphost.vcloud.local
RSA Authentication Manager Installation Directory: /opt/rsa/am

2. Navigate to /opt/rsa/am/utils.
3. Use the command ./rsautil manage-secrets –a recover to restore the system fingerprint.

rsaadmin@app81p:> cd /opt/rsa/am/utils
rsaadmin@app81p:/opt/rsa/am/utils> ./rsautil manage-secrets -a recover
Please enter OC Administrator username: <enter Operations Console administrator name>
Please enter OC Administrator password: <enter Operations Console administrator password>
Machine fingerprint restored successfully.

4. Navigate to /opt/rsa/am/server and restart all RSA Authentication Manager services for the change to take effect:

rsaadmin@app81p:/opt/rsa/am/utils> cd ../server
rsaadmin@app81p:/opt/rsa/am/server> ./rsaserv restart all
Stopping RSA RADIUS Server: **
RSA RADIUS Server                                          [SHUTDOWN]
Stopping RSA Runtime Server: ****
RSA Runtime Server                                         [SHUTDOWN]
Stopping RSA Console Server: ***
RSA Console Server                                         [SHUTDOWN]
Stopping RSA Replication (Primary): *
RSA Replication (Primary)                                  [SHUTDOWN]
Stopping RSA Database Server: **
RSA Database Server                                        [SHUTDOWN]
Stopping RSA RADIUS Server Operations Console: **
RSA RADIUS Server Operations Console                       [SHUTDOWN]
Stopping RSA Administration Server with Operations Console: **
RSA Administration Server with Operations Console          [SHUTDOWN]
Starting RSA Database Server:
Starting RSA Administration Server with Operations Console: ****************************
RSA Administration Server with Operations Console          [RUNNING]
Starting RSA RADIUS Server Operations Console: / RSA Database Server                  [RUNNING   *****************
RSA RADIUS Server Operations Console                       [RUNNING]
Starting RSA Runtime Server: **********************************
RSA Runtime Server                                         [RUNNING]
Starting RSA RADIUS Server: **
RSA RADIUS Server                                          [RUNNING]
Starting RSA Console Server: *
Starting RSA Replication (Primary): ****
RSA Replication (Primary)                                  [RUNNING]*****************************
RSA Console Server                                         [RUNNING]

This was a more common problem with AM 7.1 and AM 8.0, not as much in later versions