VMware; vCenter 6.0 – Quick stats on hostname is not up-to-date

//VMware; vCenter 6.0 – Quick stats on hostname is not up-to-date

VMware; vCenter 6.0 – Quick stats on hostname is not up-to-date

Today we have encounter some issues on our upgraded ESXi 6.0 hosts.

Some of our hosts were with the error “Quick stats on hostname is not up-to-date”.

An example:

This is know issue in 5.0 and 5.5, that is fix in the updates, but in vCenter 6.0.

The workaround to fix this issue is to add this quickStats parameters to the Advanced Settings of vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  •  vpxd.quickStats.ConfigIssues

Note: Adding these parameters to vCenter Server does not affect future upgrades.

So lets add this parameters to the vCenter Advanced Settings.

Connect to your vCenter using vSphere Client and go to Administration > vCenter Server Settings

Add the first key in(vpxd.quickStats.HostStatsCheck) and add a value “False”

Click “Add” and then add the second parameter(vpxd.quickStats.ConfigIssues).

After adding both parameters, restart your vCenter Server services.

Then all messages should go away and the problem is fixed.

Note: For a more detail information about this issue, please read KB-2061008 from VMware

Hope this article can you help fixing this issue.

Note: Share this article, if you think is worth sharing.

By | 2017-12-30T02:50:13+01:00 September 21st, 2015|Virtualization|0 Comments

About the Author:

I am over 20 years’ experience in the IT industry. Working with Virtualization for more than 10 years (mainly VMware). I am an MCP, VCP6.5-DCV, VMware vSAN Specialist, Veeam Vanguard 2018/2019, vExpert vSAN 2018/2019 and vExpert for the last 4 years. Specialties are Virtualization, Storage, and Virtual Backups. I am working for Elits a Swedish consulting company and allocated to a Swedish multinational networking and telecommunications company as a Teach Lead and acting as a Senior ICT Infrastructure Engineer. I am a blogger and owner of the blog ProVirtualzone.com

Leave a Reply

%d bloggers like this: