by Duncan Epping
Duncan Epping · ·
Today I noticed the following error at a customer site when I wanted to install the new patch bundle, “Metadata for patch missing”. After a close inspection I noticed VirtualCenter was installed with a different http port number. For VMware Update Manager to work you will have to open up the firewall manually:
esxcfg-firewall -o 81,tcp,out,UpdateManager
(Change the port number, in red, according to the used portnumber for VirtualCenter.)
Duncan Epping · ·
Today I received the following error at a customer site when applying patch via the Update Manager:”Metadata for patch missing.” After a close inspection I noticed VirtualCenter wasn’t running on port 80 but on 81 for some reason. Opening up the ESX Firewall and restarting the VMware Update Manager service seems to fix this problem. The firewall was opened up as follows
esxcfg-firewall –openport 81,tcp,out,updatemanager
Duncan Epping · ·
I was just testing the new patches on a couple of servers when I noticed that when I pressed “remediate” the first patch(ESX350-200802403-BG) was installed without the ESX host going into maintenance mode. When the second patch(ESX350-200802409-BG) was installed the server went into maintenance mode. According to the VUM Documentation(vi3_vum_10_admin_guide.pdf) the server should always go into maintenance mode before installing the patches:
Update Manager puts ESX Server in maintenance mode before applying updates. Virtual machines cannot continue to run when an ESX Server is in maintenance mode. To ensure a consistent user experience, Update Manager migrates virtual machines to other ESX Server hosts before the server being remediated is put in maintenance mode.
I can imagine this happens because the system impact of the first patch is “No VM Shutdown & No Host Reboot” and for the second patch it is “VM Shutdown & Host Reboot”. Anyway, it would be a nice addition if one could choose to always enter maintenance mode before applying patches. It definitely gives me a more save feeling.
Duncan Epping · ·
I just noticed that VMware released a new version of ESX 3i on the 10th of January. The current build number is “70348” and the previous was “67921”. It’s just a minor update:
EULA Update—The reissued version of ESX Server 3i Installable incorporates an updated, corrected version of the EULA.
Licensing Fix—The reissued version of ESX Server 3i Installable lets you apply appropriate host-based licenses to servers that have more than two CPUs.