000030773 - RSA Administration Server with Operations Console service fails on a VM that has been cloned/restored/moved

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030773
Applies ToAM 8.1
Vmware 
IssueRSA Administration Server with Operations Console service fails on a VM that has been cloned/restored/moved, which leads to the consoles being unavailable. 
TasksBy default (standard VMware behaviour) when a VM is moved from one cluster to another, it is cloned or restored, the MAC address of the network card changes.
This causes the RSA VM to see it as a new adapter and adapter "eth0" to disappear.
RSA services rely on eth0 and are unable to start.
ResolutionResolution attempt 1: Failed
One way of resolving would be to change linux system files so that the new network adapter becomes eth0 (instead of eth1 or eth2). This is not possible as even the RSA Super Admin account does not have root privileges. 
Resolution attempt 2: OK!
On the cloned/restored VM, before starting, modify the .VMX file to set the MAC address to static, forcing the same MAC as the original VM.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=507
When the VM is started, as the MAC has not changed, eth0 is still present and RSA services start normally.
Consoles are working now.
NotesModify VMX files on original Production VMs (shutdown required) to always force static MAC.

Attachments

    Outcomes