As promised I remembered to dig into my virtual center event logs to pull out the error message that I received after upgrading my 3 esx servers. “An error occurred during configuration of the HA Agent on the host.” “hostmisconfigured : failed to resolve hostname/ip using short hostname yourdomain.”Simply add your hostnames and ip’s to /etc/hosts
I’m happy to report that upgrading vmware esx from 3.01 to 3.02 was a breeze. I was able to utilize maintenance mode and for the first time in my career do mid day operating system upgrades with zero affected production systems! I was also successful in upgrading Virtual Center from 2.0 to 2.02.
I utilized the patch update program I previously mentioned for the esx upgrades… flawless.
During our VMware VI3 deployment I’ve been very impressed with Virtual Center. I was however very surprised to not find a patching or update mechanism that is so ancient. One must run commands from the console to query what patches are installed and maintain their own local patch repository if they have more than one esx servers and require speedy patching. Crazy! Us windows admins have been point and clicking updates since Win2k!
VMTS came to my rescue..A patch program for ESX that utilizes Virtual Center. The program has been great so far and have erased a nightmare that is CLI patching. Besides…have you seen how many patches were released for 3.0.1? Give me a break!
If you want to make you’re life easier like mine check out: http://vmts.net
TAC9858: Patching and Updating VMware ESX Server 3
Evan Chan, VMware and Govindarajan Soundararajan, VMware
Powered by WordPress | Aeros Theme | TheBuckmaker.com WordPress Themes
