KB Digest Top 20

Top 20 vSAN articles for February 2018

  1. Component metadata health check fails with invalid state error
  2. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  3. vSAN Build Recommendation Engine Health fails
  4. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  5. How to manually remove and recreate a vSAN disk group using esxcli
  6. vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
  7. Replacing SSD disk on a vSAN cluster
  8. vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider
  9. Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
  10. vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
  11. On vSAN 6.6 and 6.6.1 cluster, Testing health check fails randomly
  12. Diskgroups fail to mount due to heap exhaustion
  13. Cannot view or add vSAN Storage Providers in the vSphere Web Client
  14. “The ramdisk “vsantraces” is full” error reports in vSAN logging
  15. Initializing vSAN during boot takes a longer time
  16. “Unexpected status code: 503” error in vSAN health check plug-in
  17. “Virtual SAN objects available for provisioning” task fails
  18. vSAN host may encounter a purple diagnostic screen during performance statistics updates
  19. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  20. “Virtual SAN Disk Balance” warning alarm during vSAN health check