I need to find out witch firmware version is running on my HBA without rebooting the ESX host.. I thought this was possible by GUI but couldn’t find it, so I decided to check this by console. Give the following commands:
- cd proc/scsi/qla or lpfc820
- ls –lia
To view the HBA information:
- cat 6
- cat 7
It wasn’t so difficult!
To determine if VAAI is enabled service console in ESX or the RCLI in ESXi, run the commands and ensure that the value is 1:
# esxcfg-advcfg -g /DataMover/HardwareAcceleratedMove
# esxcfg-advcfg -g /DataMover/HardwareAcceleratedInit
# esxcfg-advcfg -g /VMFS3/HardwareAcceleratedLocking
Can I check the VAAI status from the command line?
esxcfg-scsidevs -l | egrep "Display Name:|VAAI Status:"
More interesting information: yellow-bricks.com
Source: VMware KB
VMware released the first patches for ESX en ESXi 4.1, more information:
ESX410-201010401-SG Security - KB 1027013
ESX410-201010402-SG Security - KB 1027014
ESX410-201010404-SG Security - KB 1027016
ESX410-201010405-BG Critical - KB 1027017
ESX410-201010409-SG Security - KB 1027019
ESX410-201010410-SG Security - KB 1027020
ESX410-201010412-SG Security - KB 1027022
ESX410-201010413-SG Security - KB 1027023
ESX410-201010414-SG Security - KB 1027024
ESX410-201010415-BG Critical - KB 1027025
ESX410-201010419-SG Security - KB 1027026
ESXi410-201010401-SG Security - KB 1027021
ESXi410-201010402-BG Critical - KB 1027028
Download patches: VMware
Today I did some maintenance in the datacenter. I upgraded last month to vCenter 4.1 and the ESX hosts from 4.0 to 4.1. Today was planned to update some virtual hardware from 4 to 7 but after I upgraded and started some Windows 2008 SP2 VM’s I can’t connect mappings and receiving some errors from the loginscript. After some troubleshooting I saw that some local disks (.VMDK) are offline!
Goto Disk Management > Right click on the offline disk, select: Online
Okay, the disk is online.. my data is back without any dataloss but my shares are gone. You only need to restart the VM again to resolve this issue.
After installing a new VMXNET3 network card my HP MAC based license server didn’t function anymore. To change the MAC address in the VMX file I used a very nice tool, called: Virtual MAC Tool created by Richard Garsthagen.
- Turn off your VM;
- Open Virtual MAC Tool;
- Connect your ESX host or VC;
– Select the VM and vNIC/Network you want to change the MAC address
After receiving some emails from vCenter that my heartbeat is incorrect I decided to troubleshooting this issue, but after some time but didn’t found a good answer to solve this issue so I called VMware..
[VMware vCenter - Alarm Host error] Error detected on esx51 in [clustername]: Agent can’t send heartbeats.msg size: 1014, sendto() returned: Operation not permitted
- Upgrade your ESX Host firmware;
- You need to reset the default sensors once, goto:
ESX Host > Hardware Status > Select: “System event” log and click Reset Sensor. This will clear the sensor status and recheck the hardware sensors again. If there still some errors please check your hardware, if not.. your fake/hanging warning disappears.
Since vSphere 4.1 there’s a possibility to connect your ESX server into Microsoft Active Directory, how do you configure this:
- Connect directly to your ESX host
- Make sure your DNS servers are correct configured on the host + add the host by FQDN in your DNS server in your domain;
Today on the Dutch VMug forum somebody got some trouble to connect a ESX host after changing the “root” permissions from Administrator to Read-only. Nice problem to find a solution, I created the same situation in my test environment.
User: Root – Role: Read-Only
You can’t connect the host anymore with your VI Client..
… but you can still login at the console or putty session.. so what to do:
Edit the authorization.xml file: nano /etc/vmware/hostd/authorization.xml
After installing VMware ESX 4.1 with a connected USB (for USB passtrough in one of my VM’s) disk in my VMware Workstation 7.1 I received this error:
0:00:00:56.791 cpu0:4096)Warning: /vmfs/devices/char/vmkdriver/usbpassthrough not found