After cloning an API Gateway virtual machine, the NIC assigned to the VM changes its MAC address so networking for that interface (i.e. eth0, eth1, etc.) will be inaccessible.
This issue occurs when a virtual machine is cloned, the network adapter(s) are given new MAC addresses.
Some clients will clone the virtual machine for backup purposes. It is recommended to use "snapshots" instead of cloning to avoid these types of issues which cause a need for re-configuration.
This affects any VMs which are hosted in a VMware environment. This is not CA product-specific.
The instructions for resolution come officially from the VMware KB article, found here: https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2002767
The instructions from that KB article linked to on the VMware website should be followed.
At a high level, the instructions involve the following:
Note: The /etc/udev/rules.d/70-persistent-net.rules file may also need to be updated to the new MAC address.