000037853 - VMware Quick Setup fails at Configuring Appliance with the error Unable to find SMBIOS for RSA Authentication Manager 8.4

Document created by RSA Customer Support Employee on Aug 30, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037853
Applies ToRSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4.x
IssueAfter going through Quick Setup, the process fails at Configuring Appliance and gives an option to download the install logs. The Quick Setup logs can be found in the downloaded logs at <log_directory>/install_logs/config/config.sh_InstallAM_completeInstallAfterQuickSetup_<timestamp>.log.

When checking the log file, you will find the following error stack:

17751  2019-08-20 20:52:01,142 INFO: Generating operations console key pair
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/rsa/am/utils/lib/linux-x86_64/libsystemtools.so
which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Unable to find SMBIOS
Exception in thread "main" com.rsa.ims.security.keymanager.sys.SystemValuesMissingException: getSSVS error: Resource
temporarily unavailable
at com.rsa.ims.security.lockbox.crypto.SystemTools.getSSVSEx(Native Method)
at com.rsa.ims.security.lockbox.crypto.h.a(h.java:94)
at com.rsa.ims.security.lockbox.crypto.j.a(j.java:10)
at com.rsa.ims.security.lockbox.crypto.j.d(j.java:15)
at com.rsa.ims.security.lockbox.crypto.h.b(h.java:89)
at com.rsa.ims.security.lockbox.crypto.h.b(h.java:12)
at com.rsa.ims.security.lockbox.b.a(b.java:349)
at com.rsa.ims.security.lockbox.b.saveFields(b.java:171)
at com.rsa.ims.security.lockbox.b.saveFields(b.java:160)
at com.rsa.ims.security.keymanager.sys.FieldsManager$saveFields$1.call(Unknown Source)
at Secrets.populateInitialSecrets(Secrets.groovy:167)
at Secrets.create(Secrets.groovy:143)
at Secrets$create$1.call(Unknown Source)
at InstallAM.installAfterSoftware(InstallAM.groovy:23)
at InstallAM.refreshExceptSoftware(InstallAM.groovy:46)
at InstallAM.completeInstallAfterQuickSetup(InstallAM.groovy:88)
at com.rsa.plugins.install.GroovyInstallEngine.invokeScript(GroovyInstallEngine.groovy:68)
at com.rsa.plugins.install.GroovyInstallEngine$_runTask_closure2.doCall(GroovyInstallEngine.groovy:57)
at com.rsa.plugins.install.GroovyInstallEngine.runTask(GroovyInstallEngine.groovy:56)
at com.rsa.plugins.install.GroovyInstallEngine$_runTasks_closure3.doCall(GroovyInstallEngine.groovy:106)
at com.rsa.plugins.install.GroovyInstallEngine.runTasks(GroovyInstallEngine.groovy:105)
at com.rsa.plugins.install.GroovyInstallEngine$runTasks.call(Unknown Source)
at com.rsa.plugins.install.CommandLineInstallEngine.main(CommandLineInstallEngine.groovy:40)
Configuration step InstallAM:completeInstallAfterQuickSetup [FAILED]


Check the ESXi using the vSphere Web Client by going into Edit Settings > VM Options > Boot Options.  You will find that the Firmware Type is set to UEFI / EFI.

CauseThis is a compatibility issue. If the installer cannot obtain stable system values (SSV), then the system is not suitable for Authentication Manager. The SSV are used as a factor in handling the applications secrets. In this case, the Virtual Machine Firmware type is set to UEFI instead of BIOS
ResolutionThe Firmware Type should be kept as BIOS, as that is the default setting. 

From ESXi, try the following:
  1. Delete the Virtual Machine that is showing this issue.
  2. Create a new Virtual Machine by importing a new Authentication Manager 8.4 OVA.
  3. Navigate to Edit Settings > VM Options > Boot Options, and make sure the Firmware Type is BIOS.
  4. Boot the new Virtual Machine, enter the network settings and let the machine boot to show the Quick Setup URL and Access Code.
  5. You should be able to go through Quick Setup with no issues.

Attachments

Outcomes