VMWare Quick stats not up-to-date


VMWare Quick Stats Not Up-to-date Fix

This message is only displayed when you connect to vCenter server using vSphere client or Web Client. However, the error does not show up if you connect to one of the VMware ESXi host(s) directly.
This is a commonly known issue within vSphere version 5.5 and 6.0. The issue was fixed within update to VMware ESXi 5.5.0b and ESXi 6.0.0b. Not sure why VMware has not taken initiatives to fix the bug in it’s first release and had to release an update?

In order to resolve this issue you will need to add few advanced parameters to vCenter server settings. The following parameters will need to be entered manually via vSphere client or Web client:
  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues
You can do these changes with these simple steps:
  1. Connect to your vCenter using IP or hostname along with your credentials. Typically the username will be administrator@vsphere.local and whatever your SSO password you set it to.
  2. In vCenter 6.0 you go to Administration from the top menu and then vCenter server settings which will open up a dialog box. In vCenter 5.5 it will be under Manage > Settings > Advanced settings.
  3. Click on Advanced Settings from this dialog box at bottom right hand corner of the window.
  4. There are two fields called key and value. You need to enter the two parameters mentioned below with value of “false”.  Enter key vpxd.quickStats.HostStatsCheck with value of false and Add. Enter the second key vpxd.quickStats.ConfigIssues with value of false and Add. To finish press OK.
  5. These advanced settings will not take effect until you have restarted vCenter services. RDP/Remote desktop to your vCenter server and go to services to find your vCenter server instance. Right click and restart the service to apply these settings. You will lose connectivity to vCenter when you restart but the VMs and hosts will remain online.
 
Configuration issues quick stats
 
In an event where web client and vCenter client is inaccessible you can hard code it to the VPXD configuration file.
vpxd.cfg contains all the information about your vCenter setup so make sure you take a backup before even attempting to change it. Typically the file will be in the following locations:
  • Windows installations of vCenter: C:\ProgramData\VMware\VMware VirtualCenter\
  • vCenter appliance instance (Linux): /etc/vmware-vpx/
Enter the following lines in between the opening tag of vpxd and closing tag of vpxd.

<vpxd>
…
<quickStats>
<HostStatsCheck>false</HostStatsCheck>
<ConfigIssues>false</ConfigIssues>
</quickStats>
…
</vpxd>

Once you have saved the vpxd.cfg file then don’t forget to restart the vCenter services.
You should see no more errors or warning within your vCenter server regarding Quick Stats is not up-to-date.

Comments

Post a Comment

Popular posts from this blog

MS Outlook: Can't See Manage Rules

MS Outlook:  Can't See Manage Rules Screen By: Danny Garner of Geaux Techie LLC geauxtechie.com Issue:  When you try to go into Outlook and select Manage Rules and Alerts, you get just a flash of the screen and it goes away. The Manage Rules won't fully open. Cause:  One of your rules is causing the module to hang.  Likely have too many rules defined. Fix: Go to Start>Search and type "outlook /cleanrules" and hit enter.  Relaunch Outlook and you should be able to select the Manage Rules screen. Reference: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_other/outlook-2010-manage-rules-dialog-box-wont-open-any/9f62b456-fbf8-4163-97d6-dd6c3143f6d4
Read more

Cisco Firepower FMC Wildcard SSL Certificate Remote Access AnyConnect VPN

                 Changing the Wildcard SSL on a Cisco Firepower FMC for a AnyConnect VPN   When changing or renewing a Wildcard SSL for Cisco AnyConnect on the FMC you want to use the appropriate export function on the originating device so you don't run into errors.   Exporting the Wildcard SSL can be tricky if you use the wrong process.  If you are exporting from a Windows based server, DON'T export from the IIS Console.  Open up the MMC and open the Certificates module and export from that method.  It will export the correct path with the cert into the pfx file.   Importing into FMC will be seamless and both the CA and ID will be correct.   Otherwise, if you use the IIS export method the path for the CA is incorrect and you will get a red X on the CA status.  Hope this helps someone save some time.  
Read more