1. Component metadata health check fails with invalid state error
  2. vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message:
  3. Retrieve a ticket to register the vSAN VASA Provider
  4. vSphere Web Client displays alerts for network partitions of a vSAN cluster
  5. vSAN 6.2 hybrid disk group performance degradation
  6. FAQ: Support statement for 512e and 4K Native drives for VMware vSphere and vSAN
  7. vSAN Health Service – Cluster Health – Deduplication and compression configuration consistency check
  8. Enabling or disabling a vSAN cluster
  9. ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration
  10. Using vSAN Health Service on vCenter Server causes vpxd memory to grow
  11. vSAN observer fails with the error: “Failed to generate HTML bundle: Gem::Package::TooLongFileName:”
  12. vSAN Health Service – Performance Service – Stats DB object check
  13. vSAN Health Service – Cluster health – vSAN disk balance
  14. Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters
  15. vSAN proactive rebalance
  16. How to add a host back to a vSAN cluster after an ESXi host rebuild
  17. After removing and re-inserting a disk associated with vSAN, the disk is not re-added to the vSAN disk group
  18. vSAN memory or SSD congestion reached threshold limit
  19. VMware vSAN 6.2 fulfillment
  20. Understanding Congestion in vSAN