VMware

VMware Virtual SAN Health Check Plug-in 6.0.0 Release Notes

VMware Virtual SAN Health Check Plug-in 6.0.0 | 05 May 2015 | Build 2707957

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

In this release, Virtual SAN introduces the health check plug-in. The plug-in includes several preconfigured 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.

The plug-in includes the following key features:

  • Proactive Tests: Run proactive health tests on a Virtual SAN cluster to verify the cluster health and performance, and detect any faulty flash and capacity devices, hardware components, and storage controllers.

  • Update the HCL database: Use VMware HCL database to verify that your Virtual SAN environment uses hardware, software, and drivers that are certified and approved by VMware Virtual SAN.

  • Upload Virtual SAN Support Files: Use health check plug-in to attach your Virtual SAN log bundles to the support requests (SRs) that you have opened with VMware Global Support Services (GSS).

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.

Limitations

The expected behaviour 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.

  • 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.