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. “Unexpected VMware Update Manager (VUM) baseline creation failure” error in vSAN Build Recommendation Engine Health
  4. Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation
  5. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  6. vSAN Health Service – Online Health – Controller Utility Is Installed on Host
  7. VASA Provider Registration Troubleshooting
  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. Unable to upload, copy or create files in a VMware vSAN-backed datastore
  11. “Virtual SAN Disk Balance” warning alarm during vSAN health check
  12. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  13. Network diagnostic mode health check warning in cluster configuration consistency check
  14. Component metadata health check fails with invalid state error
  15. Initializing vSAN during boot takes a longer time
  16. ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration
  17. VMware vSAN 6.x health plug-in fails to load with the error: Unexpected status code: 400
  18. Issues with Custom Certificates from vSAN 6.5 and newer releases
  19. vSAN cluster summary tab shows health alarm ” vSAN object health ” Home Object ” “After 1 additional host failure” ” Host with connectivity issues”
  20.  vSAN Health Service – Cluster health – vCenter state is authoritative