Search the VMware Knowledge Base (KB)
View by Article ID

vCenter Server Appliance (VCSA), vSphere Data Protection (VDP) Appliance or vSphere Management Assistant (vMA) has no network connection after re-registering, cloning, or restoring from backup (2012451)

  • 22 Ratings
Language Editions

Symptoms

  • After unregistering or registering the vCenter Server Appliance, vSphere Data Protection appliance or the vSphere Management Assistant (vMA) and selecting I copied it, the Appliance is unable to set an IP address.
  • After restoring the vCenter Server Appliance, vSphere Data Protection appliance or the vMA from backup or cloning the appliance fails set an IP address.
  • When powering on the Appliance you see errors on the console:

    Waiting for mandatory devices:   eth0 __NSC__
    29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
           eth0                                                No interface found           failed
    Setting up service (localfs) network . .  .  .  .  .  .  .  .  .  .                     failed


  • During power on, you see an entry on console similar to:

    eth0: error fetching interface information: Device not found

Cause

A new MAC address is generated for the Appliance when re-registering, cloning or restoring from backup. This happens when registering the Appliance selecting I copied it in the Summary tab. The MAC address is stored in a configuration file that does not get updated with the new MAC address, which causes the appliance to not be able to find the correct NIC.

The operation creates a new UUID and so a new Mac Address is assigned for the virtual NIC. As a result, the virtual NIC is now detected as eth1 rather than an eth0.

For example, in the /etc/udev/rules.d/70-persistent-net.rules file on a vSphere Management Assistant (vMA):
# This file was automatically generated by the /lib/udev/write_net_rules

# program run by the persistent-net-generator.rlules rules file.

# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:aa:52:39", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" --> original entry

# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:34:89:e8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" --> new entry
The Mac Address [00:50:56:aa:52:39] is statically linked to the interface [eth0], which does not exist anymore.

Resolution

To resolve this issue on the vCenter Server Appliance:
  1. Right-click the vCenter Server Appliance Virtual Machine and click Edit Settings.
  2. Click Network adapter 1 and record the new MAC Address value. Click OK.
  3. Power on the vCenter Server Appliance and click the Console tab.
  4. Log into the vCenter Server Appliance with root credentials.
  5. Change directory to /etc/udev/rules.d/:

    cd /etc/udev/rules.d/

  6. Back up the /etc/udev/rules.d/70-persistent-net.rules file.
  7. Open the /etc/udev/rules.d/70-persistent-net.rules file in a text editor, and change the MAC address to the value recorded in step 2 for eth0.

    For example:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}==" xx:xx:xx:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

  8. Comment out the line corresponding to the eth1 interface.
  9. Save and close the file.
  10. Restart the vCenter Server Appliance.

To resolve this issue on the vSphere Data Protection appliance:
  1. Right-click the vSphere Data Protection Appliance Virtual Machine and click Edit Settings.
  2. Click Network adapter 1 and record the new MAC Address value.
  3. Click OK.
  4. Power on the vSphere Data Protection Appliance Virtual Machine and click the Console tab.
  5. Log in to the vSphere Data Protection Appliance Virtual Machine with root credentials.
  6. Change directory to /etc/udev/rules.d/:

    cd /etc/udev/rules.d/

  7. Back up the /etc/udev/rules.d/70-persistent-net.rules file.
  8. Open the /etc/udev/rules.d/70-persistent-net.rules file in a text editor, and change the MAC address to the value recorded in step 2 for eth0.

    For example:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}==" xx:xx:xx:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

  9. Comment out the line corresponding to the eth1 interface.
  10. Save and close the file.
  11. Restart the vSphere Data Protection Appliance.

To resolve this issue on the vMA:
  1. Right-click the vMA Virtual Machine and click Edit Settings.
  2. Click Network adapter 1 and record the new MAC Address value.
  3. Click OK.
  4. Power on the vMA and click the Console tab.
  5. Log in to the vMA with vi-admin credentials.

    Note: The commands in these steps must be run as root, so you must use the sudo utility in front of the commands.

  6. Change directory to /etc/udev/rules.d/:

    cd /etc/udev/rules.d/

  7. Back up the /etc/udev/rules.d/70-persistent-net.rules file:

    sudo cp /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.orig

  8. Open the /etc/udev/rules.d/70-persitent-net.rules file in a text editor:

    sudo vi /etc/udev/rules.d/70-persistent-net.rules

  9. Change the MAC address to the value recorded in step 2 for eth0.

    For example:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}==" xx:xx:xx:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

  10. Comment out the line corresponding to the eth1 interface.
  11. Save and close the file.
  12. Restart the vMA.

After the reboot of either Appliance, do a final check by running this command on the console:

ifconfig -a
 
Note: vSphere Management Assistant (vMA) 5.0 is a Suse Enterprise 11 SP1 appliance, this method can be applied to other Linux distributions.

Additional Information

vSphere Management Assistant (vMA) 5.0 is a Suse Enterprise 11 SP1 appliance, this method can be applied to other Linux distributions.

See Also

Language Editions

ja,2099877;zh_cn,2102778

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 22 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 22 Ratings
Actions
KB: