I have an ESXi server running basic network services, i.e. firewall, domain controller, dhcp, dns, disk shares, etc. The guest OS's are set up to come online in the following order: firewall, domain controller, everything else.
We recently experienced a power failure. All OS's came online in (I presume) the correct order, however, the internal network was disconnected. All OS's have the box checked for "connect at power on", however, no services were available, and when I finally set my desktop to a manual IP address and logged in to the VMWare server, I discovered that the checkbox for "Connected" on all interfaces for the internal network were unchecked. The external network (internet) seemed to be just fine.
Needless to say, this is not an ideal situation. If I had not been in the office at the time this power failure occurred, all internal services would be more or less unrecoverable.
Is this a setting somewhere or a bug, and how to make sure it does not happen again? (it seems a bug - how can you have "connect at power on" not connect you at power on?)
- ESXi version is 5.1.0, build 799733.
- Guest OS's are:
- 3X Ubuntu 12.10 server, (file storage, databases, internal web services)
- Firewall is a custom FreeBSD implementation (pfSense 2.0.3-RELEASE)
- DC/ DNS/ DHCP is Windows 2003 Standard SP2
Networking is set up as follows: