Wu's Blog

It's been a long time since last post, I was pretty busy on a storage issue, I did a lot of work with hardware vendor and VMware for this weird issue. During our troubleshooting, I noticed a minor problem when I try search VM in vSphere Client, everytime it gave me error message " Unable to connect to web services to execute query ", it requested me " Verify that the VMware VirtualCenter Management Webservices service is running " I tried to reboot vCenter Server, restart Management webservices and even re-installed vSphere Client, no lucky....Finally I fixed the problem by following step: Stop VMware VirtualCenter Management Webservices service on vCenter Server. Backup Data folder in C:Program FilesVMwareInfrastructuretomcatwebappssmsWEB-INFclassescomvmwarevimsms . Remove all sms-*.db files in Data folder. Restart VMware VirtualCenter Management Webservices service. It's simple steps to fix the problem, but this issue confused me and VMware supp

Storage team said the best practics of QFullSampleSize is 32, they want to check how it's going in our environment. It's easy to check individual host, but pretty time consuming if you want to check 300+ hosts. Here is a one line PowerShell script to export QFullSampleSize and QFullThreshold to a csv file. Get-VMHost | %{ $HostName=$_.Name; $HostCluster=$_.Parent; Get-VMHostAdvancedConfiguration -VMHost $_ | % { $_.getEnumerator()| ? {$_.Key -like "* QFull *"} | select Name,Value,@{N='host';E={$HostName}},@{N='Cluster';E={$HostCluster}} } } | export-csv c:qSetting.csv      

Today I see this error message on one ESXi5.0 host: The number of heartbeat datastores for host is 0, which is less than required: 2 No any VM is running on the host by DRS or HA, VMware KB gives a solution but too complicate. Re-configure HA can fixes the problem. Right click the host -> Click Reconfigure for vSphere HA -> Waiting HA configuration complete.

Today, we P2V one vCenter Server, I re-added identify source for some reason, I didn't modified any existing domain group and ACL. After a while I got a interesting case. User reported they got "No permission to login to vCenter Server 5.1 by vSphere Client". I looked into the vpxa.log of vCenter Server, it show that: 2013-05-01T11:08:01.399-05:00 [09108 error '[SSO]' opID=6e704a51] [UserDirectorySso] AcquireToken InvalidCredentialsException: Authentication failed: Authentication failed 2013-05-01T11:08:01.399-05:00 [08644 error 'authvpxdUser' opID=5469f71e] Failed to authenticate user <xxxx> I was not 100% sure that log related to the real problem. but that's indicated it should be something related to authentication components. After compared working SSO with the fault SSO, I noticed Domain Alias was blank on fault SSO: Then I added a domain group on fault vCenter Server and compared the group with working vCenter Server, it's shows format