VCenter Server 5.5 displays a yellow warning in the Summary tab of hosts: Quick stats on hostname is not up-to-date

Problem:

  • When connecting to VMware vCenter Server 5.5 using the VMware vSphere Client or VMware vSphere Web Client, the Summary tab of the ESXi 5.5 host shows a yellow warning.
  • You will see the  following error:Configuration issues. “Quick stats on hostname is not up-to-date”

Note: This issue does not occur if you connect directly to the ESXi host.

Resolution

This is a known issue in vCenter Server 5.5.

To work around this issue, you have to add these quickStats parameters to the Advanced Settings of the vCenter Server:

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

To add the quickStats parameters to the Advanced Settings of the vCenter Server:

  1. In the vSphere Web Client, navigate to the vCenter Server instance.
  2. Select the Manage tab.
  3. Select Settings > Advanced Settings.
  4. Click Edit.
  5. In the Key field, enter this key: vpxd.quickStats.HostStatsCheck
  6. In the Value field, enter: False
  7. Click Add.
  8. In the Key field, enter this key: vpxd.quickStats.ConfigIssues
  9. In the Value field, enter: False
  10. Click Add.
  11. Click OK.
  12. Restart the vCenter Server services.

To work around this issue in the event that vSphere Web Client is inaccessible, add these quickStats parameters to the vpxd.cfg file:

  • <HostStatsCheck>false</HostStatsCheck>
  • <ConfigIssues>false</ConfigIssues>

To add the quickStats parameters to the vpxd.cfg file:

  1. Back up the existing vpxd.cfg file. Do not skip this step.
  2. Open the the vpxd.cfg file using a text editor.
  3. By default, the vpxd.cfg file is located at:
  • Windows-based vCenter Server – C:\ProgramData\VMware\VMware VirtualCenter\
  • vCenter Server Appliance – /etc/vmware-vpx/
  1. Add these entries between the <vpxd>…</vpxd> tags:<vpxd>

    <quickStats>
    <HostStatsCheck>false</HostStatsCheck>
    <ConfigIssues>false</ConfigIssues>
    </quickStats>

    </vpxd>
  2. Save and close the vpxd.cfg file.
  3. Restart the vCenter Server services

 

Posted in: Vmware.
Last Modified: October 22, 2013

Leave a reply