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. vSAN Health Service – Online Health – Controller Utility Is Installed on Host
  4. VASA Provider Registration Troubleshooting
  5. Unable to retrieve vSAN related information via HTML5 client after upgrading to vSphere 6.7 Update 3
  6. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  7. “Cannot complete file operation” error during vSAN VM creation
  8. Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation
  9. Network diagnostic mode health check warning in cluster configuration consistency check
  10. vSAN cluster displays incorrect capacity information showing 0 Bytes used and 0 Bytes free
  11. vSAN cluster summary tab shows health alarm ” vSAN object health ” Home Object ” “After 1 additional host failure” ” Host with connectivity issues”
  12. Unable to upload, copy or create files in a VMware vSAN-backed datastore
  13. vSAN HCL DB up-to-date health check is red for the fresh deployment without internet access
  14. vSAN Health Service – Cluster – Disk format version
  15. “Virtual SAN Disk Balance” warning alarm in a vSAN 6.2 Stretched Cluster
  16. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  17. vSAN Health Service – Hardware Compatibility – Disk Group Type Check
  18. ESXi host fails to rejoin VMware vSAN cluster following reboot
  19. Initializing vSAN during boot takes a longer time
  20. VMware vSAN 6.x health plug-in fails to load with the error: Unexpected status code: 400