My Network Interface Card (NIC) Appears to be Removed From My CA API Gateway Virtual Appliance Form Factor.

Article Id: 8075
Status: Published
Updated On: 23-09-2019 12:03
Legacy Id: TEC1371839
Products:
STARTER PACK-7 , CA Rapid App Security , CA API Gateway , CA API Gateway , CA API Gateway
Issue/Introduction:

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.

Symptoms include:

  • The interface may appear to be "down" or otherwise inaccessible. Networking will not work in the cloned environment.
  • The network configuration on the guest operating system will still refer to the original MAC address.
  • There may be a mismatch between the MAC address in the virtual machine configuration at the VMware level, and the guest operating system.

 

Cause:

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.

Environment:

This affects any VMs which are hosted in a VMware environment. This is not CA product-specific.

Resolution:

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:

  1. Connect to the ESX server to manage the virtual machine settings of the node which isn't working.
  2. View the network adapter settings and note the MAC address.
  3. Login to that virtual machine and navigate to /etc/sysconfig/network-scripts
  4. Edit the appropriate file representing the interface affected, such as ifcfg-eth0 for eth0. Update the MAC address to reflect the address found in step 2 above.
  5. Save the changes to that file, then re-activate the interface by running this command (replacing eth0 with the interface affected): ifup eth0

Note: The /etc/udev/rules.d/70-persistent-net.rules file may also need to be updated to the new MAC address.

Additional Information:

  • The source information for this page, published by VMware: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002767