posted

0 Comments

  1. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  2. Thick-provisioned VMs on vSAN detected on vSAN-health check
  3. Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation
  4. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  5. VASA Provider Registration Troubleshooting
  6. vSAN Health Service – Online Health – Controller Utility Is Installed on Host
  7. “Virtual SAN Disk Balance” warning alarm during vSAN health check
  8. “Cannot complete file operation” error during vSAN VM creation
  9. VSAN cluster would display incorrect capacity information with 0 Bytes used and 0 Bytes free
  10. Using Red Hat Clustering Suite or SUSE Linux on a vSphere 6.x vSAN Datastore
  11. Replacing SSD disk on a vSAN cluster
  12. Unable to upload, copy or create files in a VMware vSAN-backed datastore
  13. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  14. VMware vSAN 6.x health plug-in fails to load with the error: Unexpected status code: 400
  15. Component metadata health check fails with invalid state error
  16. vSAN baseline recommendation is not generated for the ESXi 6.7 U1 release
  17. Initializing vSAN during boot takes a longer time
  18. Network diagnostic mode health check warning in cluster configuration consistency check
  19. vSAN memory or SSD congestion reached threshold limit
  20. OVA deployment using Webclient creates always thick provisioned vmdk