- Component metadata health check fails with invalid state error
- “Host cannot communicate with all other nodes in vSAN enabled cluster” error
- vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider
- Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
- The ramdisk ‘vsantraces’ is full
- Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
- Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x
- Cannot view or add vSAN Storage Providers in the vSphere Web Client
- Replacing SSD disk on a vSAN cluster
- “An error occurred while consolidating disks: msg.disklib.NOSPACE” in vSAN
- ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration
- “Virtual SAN Disk Balance” warning alarm during vSAN health check
- vSAN host may encounter a purple diagnostic screen during performance statistics updates
- Creating or editing a virtual machine Storage Policy to correct a missing vSAN VASA provider fails
- “Unable to register file system <UUID> for APD timeout notifications: Inappropriate ioctl for device” message in vSAN
- vSAN disk components are marked ABSENT after enabling CBT
- “The ramdisk “vsantraces” is full” error reports in vSAN logging
- vSAN 6.2 hybrid disk group performance degradation
- vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
- VMware vSAN datastore not listed as a matching datastore when creating a storage based policy
Comments