Home > Blogs > Support Insider


Top 20 vSAN articles for March 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. “The ramdisk “vsantraces” is full” error reports in vSAN logging
  6. Replacing SSD disk on a vSAN cluster
  7. vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
  8. Diskgroups fail to mount due to heap exhaustion
  9. On vSAN 6.6 and 6.6.1 cluster, Testing health check fails randomly
  10. VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
  11. 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
  12. vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
  13. Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x
  14. Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
  15. Initializing vSAN during boot takes a longer time
  16. Deployment guidelines for running VMware vSAN and VMware vSphere VMFS datastores on a Dell H730 controller with the lsi_mr3 driver
  17. Cannot view or add vSAN Storage Providers in the vSphere Web Client
  18. “Virtual SAN objects available for provisioning” task fails
  19. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  20. “Virtual SAN Disk Balance” warning alarm during vSAN health check