[error] Failed to Read Network Interface Files for 'eth1 Vami

No network connection afterward re-registering VCSA using the I've copied it answer

May 24, 2016 5428 views

Paulo Coelho once stated "Life moves very fast. It rushes from Heaven to Hell in a matter of seconds" Well I recall he perfectly described a solar day working in the lab and rushing through a migration. I'm upgrading the lab and I moved the vCenter Server Appliance (VCSA) to its new home. While trying to practise a one thousand thousand things all at in one case, I didn't pay attention to the question whether I moved the virtual machine or whether I copied information technology. I selected the option "I copied it". And that'southward when the fun started, vCenter down.
TL;DR:
Selecting "I copied it" implies that this automobile is a duplicate and that a new identity should be generated. This means that the VM is getting a new UUID and a new MAC address. SUSE Linux Enterprise Server xi detects this new MAC address and views this as a new Ethernet Device. The VCSA does not allow the creation of a new ethernet controller. Rename lxx-persistent-net.rules file and reboot to have SUSE auto-generate a new lxx-persistent-net.rules file with the right MAC Address that allows you restore network connectivity via the panel.
Troubleshooting the trouble
Both the web customer and the VCSA config spider web page are unreachable, time to open upward the VM console (Alt-F1). When logging in and pinging the gateway the error, the system returns the error message "Network is unreachable"

Before tinkering with the configuration files, I like to restart the services and see if the condition report exposes interesting information.

"No configuration constitute for eth1". The VCSA is configured with a unmarried NIC and SUSE Linux Enterprise Server 11, which is the Os for the appliance, assigns the characterization eth0 to the start Ethernet adapter. VCSA networking is configured through the Virtual Appliance Management Interface (VAMI). Executing the command "/opt/vmware/share/vami/vami_config_net allows you lot to call up the current network configuration

When selecting pick half-dozen "IP Address Allocation for eth1" VAMI reveals that it cannot read the interface files for 'eth1'

The networking interface files are stored in the directory /etc/sysconfig/networking/devices. When listing the files (ls) only ifcfg-eth0 shows up. Reviewing the ifcfg-eth0 file with cat shows that the correct networking configuration is all the same applied to eth0.

It looks like the problem occurs due to the way SUSE handles devices. The following text is copied straight from the SUSE documentation:

When the Kernel detects a network carte and creates a corresponding network interface, it assigns the device a proper noun depending on the order of device discovery, or order of the loading of the Kernel modules. The default Kernel device names are simply anticipated in very uncomplicated or tightly controlled hardware environments. Systems which allow calculation or removing hardware during runtime or support automatic configuration of devices cannot expect stable network device names assigned by the Kernel beyond reboots.
However, all system configuration tools rely on persistent interface names. This trouble is solved by udev. The udev persistent net generator (/lib/udev/rules.d/75-persistent-net-generator.rules) generates a rule matching the hardware (using its hardware address by default) and assigns a persistently unique interface for the hardware. The udev database of network interfaces is stored in the file/etc/udev/rules.d/70-persistent-cyberspace.rules. Every line in the file describes one network interface and specifies its persistent name

Source: https://www.suse.com/documentation/sled11/book_sle_admin/information/sec_basicnet_manconf.html
When the ESXi host assigns the VM a new MAC Address, SUSE assigns a new unique interface to this MAC accost and stores this in the file etc/udev/rules.d/lxx-persistent-net.rules.

It shows two Ethernet adapters, eth1 is using the MAC address currently assigned to the VM.

Nosotros are now entering a twilight zone, where there is one ethernet interface configured with an IP-accost (ifcfg-eth0) while SUSE is applying all rules to a device it created and using the MAC Accost assigned to the only NIC attached to the VM (Network Adapter 1). Fourth dimension to clean up. Luckily udev rules are automatically generated during kick. To solve the mac address assignment fast, rename the file seventy-persistent-cyberspace.rules

After rebooting the VCSA, review the 70-persistent-net.rules file to verify that SUSE assigned the MAC address to eth0.

Y'all can at present safely customize the organisation (Press F2 in the console) and configure the management network

A reboot of the VCSA is necessary as it appears that a restart of the management services is not enough to restore all services. Funny how times modify, nowadays y'all go really happy seeing a blue screen.