We have a very small installation running ESXi-5.1.0-799733-standard with a vSphere Essentials license on a single physical machine. We run 10 very different servers that support our software development needs.
We haven't had any problems with the hypervisor, perhaps for over a year. However, this morning first we noticed some of the VMs stopped responding, and about a half-hour later the hypervisor itself (accessed through vSphere Client) became unresponsive, including the hardware console itself.
We power-cycled the hypervisor hardware and everything came up fine with no error conditions or messages. All the VMs are working fine now.
What happened? How do I find out what happened? How would I copy the system logs to another system where I can study them?
The "Events" tab in the vSphere Client displays only a limited span of the most recent events. Is there a way to enlarge this log? Is there a file behind this display that retains more history?
Thanks for any advice,
If you are on 5.1 U3, your build version should be 2323236 or higher. Assuming you are, your driver version should be ahci version 3.0-15vmw, as 3.0-13 stopped being compatible from 5.1 U2.
I would consider updating that driver.
It looks like I didn't actually apply Update 3 even though I was set to do it, probably because of issues regarding scheduling downtime.
I will do that as soon as I can schedule the downtime.
You could run:
#All servers can apply VMware patches by running lines 1-6 and lines 11-12
esxcli network firewall ruleset set -e true -r httpClient
esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep ESXi-6
# Determine latest appropriate build of ESXi for your host and insert it in place of ESXi-X.X.X-XXXXXXXXXXX-standard on the next line
esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-X.X.X-XXXXXXXXXXX-standard
#The next two lines are specific to HP servers ONLY
#esxcli software vib install -d http://vibsdepot.hp.com/hpq/latest/index-drv.xml
#esxcli software vib install -d http://vibsdepot.hp.com/hpq/latest/index.xml
#The last two lines need to be run with all servers
esxcli network firewall ruleset set -e false -r httpClient
I saw this online somewhere and the step by step instructions with screenshots at: Patch your ESXi Hosts from the command line easily and quickly | JohnBorhek.com
The host needs to be in maintenance mode, which means no VM's will be hosted on it. The host should be rebooted, but since it has no VM's, it won't matter.... i.e., no impact.
After updating, but before removing it from maintenance mode, check the host out, then apply the new driver.