A few weeks ago I wrote about using iSCSI as a backup repository target. While still running this POC in my environment I came across an error in the vSAN Health Checker stating the vSAN iSCSI target service was in a Failed state. Drilling down into the vSAN Health check tree I could see a Service Runtime status of stopped as shown below against the host.
This host had recently been marked as unreachable in vCenter and required a Management Agent reset to bring it back online. There is a chance that that process stopped the iSCSI Target service but did not start it. In any case there is an easy way to see the status of the services and then get them back online.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
# #Check Status of iSCSI Target Service [root@TPM03-142:~] /etc/init.d/vitd status vitd is not running vitsafehd is not running #Restart or Start Service [root@TPM03-142:~] /etc/init.d/vitd restart vitd is not running Loading vit module vitsafehd is starting vitd is starting #Check Status again [root@TPM03-142:~] /etc/init.d/vitd status vitd is running vitsafehd is running # Check to see if iSCSI Target Service is Enabled at Boot [root@TPM03-142:~] esxcli vsan iscsi status get Enabled: true [root@TPM03-142:~] |
Once that’s been done, a re-run of the vSAN Health checker will show that the issue has been resolved and the iSCSI Target Service on the host is now running.
References:
https://kb.vmware.com/s/article/2147603
