Top 20 articles for NSX, December 2019
January 8, 2020Microsoft Azure Training Day: Fundamentals
January 8, 2020- Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
- Thick-provisioned VMs on vSAN detected on vSAN-health check
- “Host cannot communicate with all other nodes in vSAN enabled cluster” error
- vSAN Health Service – Online Health – Controller Utility Is Installed on Host
- vSAN Health Service – Limits Health – After one additional host failure
- Unable to retrieve vSAN related information via HTML5 client after upgrading to vSphere 6.7 Update 3
- Network diagnostic mode health check warning in cluster configuration consistency check
- vSAN cluster displays incorrect capacity information showing 0 Bytes used and 0 Bytes free
- “Cannot complete file operation” error during vSAN VM creation
- Virtual Machines running on VMware vSAN 6.6 and later report guest data consistency concerns following a disk extend operation
- vSAN Health Service – Cluster Health – Time Synchronization Across Hosts and VC
- Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
- vSAN cluster summary tab shows health alarm ” vSAN object health ” Home Object ” “After 1 additional host failure” ” Host with connectivity issues”
- vSAN HCL DB up-to-date health check is red for the fresh deployment without internet access
- VMware vSAN 6.x health plug-in fails to load with the error: Unexpected status code: 400
- Initializing vSAN during boot takes a longer time
- “Virtual SAN Disk Balance” warning alarm in a vSAN 6.2 Stretched Cluster
- Unable to upload, copy or create files in a VMware vSAN-backed datastore
- VMkernel log is filled with messages “Admission failure in path: vsan-scripts/python.****” events
- vSAN Health Service – Online Health – vSAN Support Insight