We had an interesting problem today and I just wanted to get some feedback on what organisations do in this situation.
We have 2 DCs/DNS servers within our ESX4 cluster.
We recently had to power the network down but ran into an issue with our vCenter server not able to authenticate when bringing our Virtual infrastructure back up. This was likely due to the fact that the DCs were still powered off.
As our DCs are virtual is there any best practises with our best to manage this process?
In the end we had to root onto each ESX host until we found which host the DCs were on so we could turn them on and authentication/DNS began working properly. From then on we were able to login to VC and switch on the rest of the machines..
We are thinking of adding a physical DC into the environment but just questioning whether we really need to do this or is there a better way in managing how we start our infrastrucutre up in the event when we next need to do a global powerdown and power on.
Any feedback would be great.
That is a common problem with all services which vCenter depends on, for example the vCenter Database. I usually have the needed VMs start automatically with the ESX Host and then start vCenter VM after that.
In vCenter select the Host -> Configuration -> VM Startup/Shutdown