User Tools
Sidebar
Table of Contents
VMware vSAN General Notes
RVC
Access the RVC
# rvc [email protected]:PASSWORD@localhost
RVC VSAN sync operations
> vsan.resync_dashboard localhost/DATACENTER/computers/CLUSTER/
VSAN 6.1 Auto Unmount
If you are using slow disks on VSAN 6.1 it might be helpful to disable slow device unmounting or device monitoring. The default for both of these is enabled or “1”.
Disable vSAN Slow Device Unmounting (continues monitoring):
# esxcli system settings advanced set -o /LSOM/lsomSlowDeviceUnmount -i 0
Disable vSAN Device Monitoring (and subsequent unmounting of diskgroup):
# esxcli system settings advanced set -o /LSOM/VSANDeviceMonitoring -i 0
http://cormachogan.com/2015/09/22/vsan-6-1-new-feature-problematic-disk-handling/
Locating Disk
The following command can be used on ESXi 6.0U2 to find where a disk is attached to a RAID controller. The RAID controller software can then be used to list the serial number of the disk. This can be useful if you are using disks installed in a case that does not provide location lights and thus can not be located via the vSphere Web Client storage location options.
[root@matx01vmvh02:~] esxcli storage core device raid list -d naa.600605b005175c801d9de8f00560e9c3 Physical Location: enclosure 1, slot 1
You can also use the following command on an LSI HBA to locate where a disk is connected to the HBA. The device id should match up with the controller drive GUID which can be found with LSI sas2ircu.
[root@matx01vmvh02~] esxcli storage core device physical get -d naa.500a0751104211b4 Physical Location: enclosure 0, slot 1
Expanding vSAN
HBAs make it much easier to add drives on the fly since there is no RAID to configure. If you have a RAID controller try to disable JBOD mode and vSAN auto disk add. Using a RAID controller for vSAN on ESXi 5.5 can also make it very difficult to locate physical disk should vSAN report one failed, but the controller reports all RAIDs as healthy.
Upgrading vSAN Disk Format
I found that when upgrading my vSAN disk format from v2 to v3 I had the run the python script that was mentioned in the blog and KB listed below. I also found that even though the precheck option didn't mention I had some CBT issues I still had to run the cbtfix option before the upgrade was able to start. If you are experiencing the same issue I did, you may see it as the Disk Format Upgrade failing at 10%.
http://cormachogan.com/2016/03/31/vsan-6-2-upgrade-failed-realign-objects/
Shutting Down vSAN Cluster
Shutdown
- Shutdown all VMs besides vCenter Server and DNS
- Verify any re-sync operations have finished
- Shutdown all remaining VMs
- Use ESXCLI to enter maintenance mode with no VSAN re-sync operations
- Take a host configuration backup of all hosts
- Properly shutdown all hosts
Startup
- Power on all hosts
- If any host does not successfully boot, resolve issue before continuing (use host configuration backup if needed)
- Verify management services are available and hosts can communicate on vSAN network
- Exit all hosts from maintenance mode
- Verify that vSAN is working and VMs are available
- Start DNS and vCenter Server
- Use vCenter Server to check vSAN status
- Start all needed VMs
Per host health check script
python /user/lib/vmware/vsan/bin/vsan-health-status.pyc
Inaccessible Objects
