VMware Virtual SAN Health Check Plug-in 6.0.1 Release Notes

|

VMware Virtual SAN Health Check Plug-in 6.0.1 | 3 August 2015 | Cloud VM RPM build: 2937162 | Windows vCenter Server MSI build: 2940255

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This patch release updates support for the Virtual SAN health check plug-in 6.0.0. The plug-in includes several reconfigured health tests to monitor, troubleshoot, and diagnose the cause of cluster component problems. Download the plug-in installer from the VMware Web site. The health check plug-in is listed under VMware Virtual SAN Tools and Plug-ins. This release provides new installation files for Cloud VM (RPM) and Windows vCenter Server ( MSI). No new ESXi host side bits (VIB) are required because the original 6.0.0 VIB is still valid.

The health check plug-in does not require a special license to run in a production environment. If your vCenter and ESXi hosts support health services, the health check plug-in is enabled automatically.

This release includes following updates:

  • Enhancement for installation status check for Virtual SAN cluster: The health check plug-in detects health check plug-in VIBs that are manually installed on ESXi hosts. No additional installation tasks are required for the health check plug-in to run.

  • Enhancement for Virtual SAN physical disk capacity check.

  • Enhancement for Support Assistant.

  • Enhancement for Customer Experience Improvement Program.

VMware Virtual SAN Community

Use the Virtual SAN Community web site to provide feedback and request assistance with any problems you encounter while using Virtual SAN.

Installation Notes for Virtual SAN Health Check Plug-in

This section provides a general steps for performing an installation or upgrade of the plug-in. For detailed installation instructions, see the Virtual SAN Health Check Plug-in Guide.

Cloud VM

Note: For both new installation and upgrade, you must run the post install script.

  1. Install RPM using the rpm -Uvh command.
  • Install: # rpm -Uvh VMware-vsan-health-6.0.0-*.x86_64.rpm
  • Upgrade: # rpm -Uvh --replacepkgs --force VMware-vsan-health-6.0.0-*.x86_64.rpm
  • Run post-install script to finish installation and restart services: /usr/lib/vmware-vpx/vsan-health/health-rpm-post-install.sh
  • Windows vCenter Server

    Note: The  user  ID  must have  vCenter  SSO  privileges and  local  Windows  administrator privileges.

    Install:

    1. Double-click the downloaded MSI file to install it.
    2. Restart vSphere Virtual Center Server.
    • From the Start menu, select All Programs > Administrative Tools > Computer Management > Service and Applications > Services.
    • In the Services window, right-click VMware Virtual Center Server, and select Restart.

    Upgrade:

    1. Stop VMware vSphere Web Client service.
    • From the Start menu, select All Programs > Administrative Tools > Computer Management > Service and Applications > Services.
    • In the Services window, right-click VMware vSphere Web Client, and select Stop. Note that VMware Performance Charts service also stops.
  • Double-click the downloaded MSI file to install it. The old version is upgraded automatically.
  • Restart vSphere Virtual Center Server, and start VMware vSphere Web Client and VMware Performance Charts services.
    • From the Start menu, select All Programs > Administrative Tools > Computer Management > Service and Applications > Services.
    • In the Services window, right-click VMware Virtual Center Server, and select Restart.
    • In the Services window, right-click VMware vSphere Web Client, and select Start.
    • In the Services window, right-click VMware Performance Charts, and select Start.

    Limitations

    The expected behavior is that each Virtual SAN cluster can be configured to have its own proxy settings so that the proxy for one cluster does not interfere with the proxy of another. However, in this release, you cannot configure different proxy settings for each cluster because when you set a proxy setting for one cluster, the proxy information is automatically applied to other clusters. For example, when you configure proxy settings for cluster A, the proxy settings for other clusters are automatically updated to use the proxy information of cluster A. As a result, all Virtual SAN clusters share the same proxy settings and you cannot specify different proxy settings for each cluster.

    Known Issues

    • Removing Virtual SAN hosts that are configured for health service causes hosts to restart
      After you remove hosts that are configured for health service from your Virtual SAN cluster, the Retry button is enabled. If you browse to the Virtual SAN cluster, click Manage > Virtual SAN > General > Health and click Retry, Virtual SAN initiates automatic removal of the health service plug-in and restarts the hosts that are removed from the cluster in order to complete the uninstall process.

      Workaround: None.

    • Virtual SAN hosts report of using a health service VIB version that cannot be tracked
      After you install the health service plug-in on a Virtual SAN cluster and add hosts that are not configured for health service, the newly added hosts report of using a health service VIB version that cannot be tracked.

      Workaround: Remove the hosts from the cluster and add them back to the cluster.

    • After uploading the support bundle, the Last upload time field is not automatically updated and shows incorrect upload date
      Browse to the Virtual SAN cluster, click Manage > Virtual SAN > Health, and click Upload Support Bundles to Service Request to enter the service request information so that the health check plug-in can collect and upload the support bundle. Typically, after uploading the support bundle, the Last upload time field is updated to display the date when the support bundle was uploaded. However, in this case, the Last upload time field is not updated automatically and shows the incorrect upload date.

    Workaround: None.

    • Unable to place hosts in maintenance mode after enabling health service
      After you enable the health service on Virtual SAN hosts, when you attempt to place the hosts in maintenance mode, you might receive an error. The error occurs when the cluster has utilized all resources available to it, such as memory, CPU, and so on, and the resources currently available in the cluster are not sufficient to place hosts into maintenance mode.

      Workaround: Add more computing resources or reduce your resource utilization so that DRS can initiate rolling restart of all hosts in the Virtual SAN cluster.

    • The storage performance test returns empty test result
      When you enter zero or negative number as the duration for running the storage performance test in your Virtual SAN cluster, the test runs successfully but does not return any result.

      Workaround: Set the duration of the storage performance test to greater than zero minute.