Monday, November 24, 2008

VMware Update Manager Gotchas

We've got a production and development vcenter area that are both on the same subnet. No problems there. We then installed a dev and prod version of UpdateManager. Uh oh. When I go into VIC -> plugins, which one is showing? There's no way to know until you get the ssl cert warning. How do I change or get rid of the connection? By uninstalling VIC, dumping files and reinstalling. From there, make sure the VUM that you don't want isn't turned on. Yuck.
Did you know that the update signatures command is triggered on VirtualCenter not UpdateManager?

Thursday, June 19, 2008

VMWare ESX lunreset cliffnotes

We had a path failover that caused one of the ESX boxes to not be happy with one of the LUNs (shown as zero bytes in VIC).
Cliffnotes as to what the steps were to remedy it. *This worked fine on our environment with other ESX hosts in the cluster actively using this LUN with running windows and linux guests. Posts in the vmware forum have a warning that this could hoze you. I agree to tread lightly with these commands (I called vmware for the below solution, I didn't want my head on the chopping block if an oracle vm crashed).

Find the LUN that is showing 0.00B:

    71  esxcfg-vmhbadevs
  72  ls /vmfs/devices/disks/

Kick it while watching it's progress:

77  vmkfstools -L lunreset /vmfs/devices/disks/vmhba0:1:1:0
  78  tail vmkernel
  79  vmkfstools -L targetreset /vmfs/devices/disks/vmhba0:1:1:0
  80  tail vmkernel
  81  vmkfstools -L busreset /vmfs/devices/disks/vmhba0:1:1:0
  82  tail vmkernel

Make sure it's there in one spot:
  83  esxcfg-vmhbadevs
  84  less vmkernel

rescan to find it in another:
  85  esxcfg-rescan vmhba0

In VIC, refresh on storage page (not rescan on storage controllers) to have it
really available to the host.

Thursday, June 12, 2008

VMWare ESX 3.5 RHEL5U1

I moved a guest RHEL 5 update 1 from ESX 3.0.1 to 3.5.1 tonight. It wouldn't boot. Well, it would start to boot, get to init and then shut itself off with no error messages on the guest or host.
Culprit: Host options had the OS still set to RHEL4 (from 3.0.1). Switching it to RHEL5 made the world turn again (after much worrying).