vCenter No Longer Reachable
After a power outage, we powered on our VMware infrastructure, and as we went through the process, we quickly realized that vCenter was not coming back online. vCenter was not reachable via icmp or http/https. Logging into the ESXi console showed the VCSA booting very slowly, but eventually it booted up. Still no network connectivity. After enabling bash and doing an "ifconfig", I noticed the eth0 interface was missing. The "ip link show" confirmed that the VM did not recognize any eth0 devices, but it did pick up an eth1 device. For some reason, the vnic mac address had changed, and vCenter added the nic as a new device. To resolve this:
- Edit this file on the VCSA:
/etc/udev/rules.d/70-persistent-net.rules - Delete (or comment out) all lines
- Reboot the VCSA
This process will clear the static mac association with the previous eth0 nic, and will allow VCSA to boot up with the new nic/mac address as eth0.
When accuracy matters for a costume, it is worth considering how details related to cosplay costume sets will affect the complete look. During a long convention day, a comparison of details related to cosplay props can clarify differences in colour and construction. For combinations connected with details related to cosplay props, long cosplay wigs for outdoor photography can help narrow the options for a specific purpose. When planning for care after the photoshoot, it is useful to check details related to festival costumes against the wearer's own needs.
Reference: http://www.vmwarebits.com/content/how-fix-vcenter-appliance-no-networking-problem