Friday, September 23, 2011

ESXi5 Myricom 10g driver install

We are upgrading ESXi 4.1 hosts to ESXi 5 - some of which have Myricom 10g network cards installed.
Once the host is upgraded to ESXi 5 we need to install the new driver:
1) scp net-myri10ge-1.5.3-1OEM.500.0.0.406165.x86_64.vib root@esxi5-02:/var/log/vmware
2) ssh esxi5-02 as root
3) /var/log/vmware # esxcli software vib install -d
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: Myricom_bootbank_net-myri10ge_1.5.3-1OEM.500.0.0.406165
VIBs Removed:
VIBs Skipped:
4) reboot and verify the card is discovered (vCenter Config->Network->Network Adapters->Add)

There is also a new method to import these as "patch extensions" into vCenter, then attach them like baselines to hosts. My first pass at this went well, except the remediation step reported the patch was not applicable and it was skipped!

Monday, September 12, 2011

VUM upgrade SQL DB connection fails

I've upgraded two vCenter 4.x's to vCenter 5 now and ran into this both times.

While upgrading the Update Manager the error returned is (paraphrasing):

"Can not connect to the database, please verify username and password..."

If your vCenter has been through a series of upgrades (like mine) the installer may be referring to a DSN (32bit vs 64bit DSN) you have not updated with the correct credentials.

To update the DSN the installer is referring to, you need to run the 32-bit ODBC tool which is located at C:\Windows\SysWOW64\odbcad32.exe. Do NOT use the default odbcad32.exe located in the C:\Windows\System32 folder. While it has the same file name, they are two different files!!

Also, if you get an error generating the JRE SSL keys, re-running that step should succeed.

Again, check your DSN with the C:\Windows\SysWOW64\odbcad32.exe, not the default path odbcad32.exe

Sunday, September 11, 2011

VM start error Cannot open the disk

We ran into this issue when a VM went down unexpectedly and it would not restart cleanly - the error was:

"Cannot open the disk '/vmfs/volumes/4cf0daa-10489d5-4e6b-00219ba51425/ttw-db-09/ttw-db-09_3.vmdk' or one of the snapshot disks it depends on."

To debug, I ssh'ed into the ESXi 4.1 box to check out the file it was referring to (it was fine and readable and touchable per KB10051) and the vmware.log which indicated the actual issue:

"Cannot open the disk '/vmfs/volumes/4cf0daa-10489d5-4e6b-00219ba51425/ttw-db-09/ttw-db-09_3.vmdk' Failed to lock the file"

None of of the related KB's helped resolve the issue.
What turned out to be the solution came from a forum posting - just creating a temp snapshot and deleting cleared the condition and allowed the VM to power on cleanly.

thanks again to the vmware community forums - truly a great 24x7 resource!