posted

0 Comments

  1. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  2. Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation
  3. Thick-provisioned VMs on vSAN detected on vSAN-health check
  4. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  5. VASA Provider Registration Troubleshooting
  6. “Cannot complete file operation” error during vSAN VM creation
  7. Replacing SSD disk on a vSAN cluster
  8. Using Red Hat Clustering Suite or SUSE Linux on a vSphere 6.x vSAN Datastore
  9. Component metadata health check fails with invalid state error
  10. “Virtual SAN Disk Balance” warning alarm during vSAN health check
  11. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  12. Initializing vSAN during boot takes a longer time
  13. VSAN cluster would display incorrect capacity information with 0 Bytes used and 0 Bytes free
  14. Unable to upload, copy or create files in a VMware vSAN-backed datastore
  15. vSAN HCL DB up-to-date health check is red for the fresh deployment without internet access
  16. Network diagnostic mode health check warning in cluster configuration consistency check
  17. “Unexpected VMware Update Manager (VUM) baseline creation failure” error in vSAN Build Recommendation Engine Health
  18. “The ramdisk “vsantraces” is full” error reports in vSAN logging
  19. vSAN health test fails on Performance Service
  20. The host enters in Maintenance Mode with the “Ensure Data Accessibility ” instead of “Evacuate all data ” or “No Data Migration” when connected directly using the host vSphere client