Monday, April 2, 2012

Introduction

So this is my first attempt at blogging.  I am creating this blog site to share my experiences with virtualization, technology and my other personal experiences along the way.

I have been working with technology for as long as I can remember but only professionally for a little over 11 years.  I concentrate on virtualization whether it is Citrix or VMware, not to much on the Hyper-V.  I also work with storage a whole lot and it doesn't really matter the vendor.  I also work a lot with backup recovery and archiving (BURA) technologies and Disaster Recovery (DR) planning. 

One thing I am not is a network engineer.  When it comes to route switching and things of that nature I leave to those guys. 

As far as my personal life I am married to my high school sweetheart and have 2 kids and live in Oklahoma.  I really enjoy soccer and coaching my son's team and watching formula 1 racing.  I also like working outside and trying to stay active as much as I can.

vSphere HA not working after vCenter 5 Upgrade

We had a customer recently that experienced issues with HA not working after upgrading vCenter to version 5.  They were going to upgrade all the hosts to version to vSphere 5 at a later date.  This happened on 2 clusters with 4 or more hosts per cluster and 75+/- VMs per cluster.  Error is listed below.


Taken from the recent tasks pane:

vSphere HA agent for this host has an error:  vSphere HA agent cannot be correctly installed or configured    WARNING
The vSPhere HA availability state of this host has changed to initialization error.  INFO
Cannot upgrade vCneter agent.  Unknown installer error ERROR


Below are the troubleshooting step we tried.
The customer contacted VMware support while we were working through this with them and so far they were still combing the logs for errors.  After 2 days or so VMware found the solution and it was very odd.

This is the resolution below.

KB 2009546 - Cannot configure HA after disabling the Host Welcome login page on an ESXi host

When we first went to this page it was blank except for the title and affected vSphere versions.  Now it is fully populated with information.

So when we were searching looking for a fix this KB wouldn't populate since it had no contents. This is now one of the errors I will ever forget.