vSAN Health Service - vSAN iSCSI target service - Home object
Article ID: 326523
Updated On:
Products
VMware vSAN
Issue/Introduction
This article explains the VMware vSAN iSCSI target service – Home object check in the vSAN Health Service and provides details about why it might report an error.
Resolution
Q: What does the vSAN iSCSI target service – Home object check do?
This health check verifies the integrity of the vSAN iSCSI target service home object. It also verifies that the configuration of the home object is valid.
Q: What does it mean when it is in an error state?
This health check includes multiple items, and the status of each item is shown in the Check column. This test checks the existence of the home object, whether the corresponding vSAN object is healthy, whether the storage policy is compliant. It also verifies the uniqueness of the home object, and whether the vSAN iSCSI service daemon can parse the configurations in the home object.
Q: How does one troubleshoot and fix the error state?
The vSAN iSCSI home object is located in the following directory: /vmfs/volumes/vsanDatastore/.iSCSI-CONFIG
The vSAN iSCSI target configuration file is located in the following directory: /vmfs/volumes/vsanDatastore/.iSCSI-CONFIG/etc/vit.conf
You can fix the following error conditions:
Home Object Exists. Verifies that the home object exists. If this file does not exist, disable and reenable the vSAN iSCSI target service.
Health Status. Verifies that the vSAN object corresponding to the iSCSI config file is healthy. If the check for this object reports an error, you might need to repair the related vSAN object.
Storage Policy Compliance. Verifies that the storage policy is compliant and is not out of date. If this check reports an error, select Cluster > Configure > Virtual SAN iSCSI Target Service to reapply the outdated storage policy or choose a compliant storage policy.
Metadata file status. Verifies that the configuration file in the vSAN iSCSI target service home object is present and that it can be parsed. If parser errors are reported, check whether any invalid names for the vSAN iSCSI entities or any invalid characters that might corrupt the configuration file.
Home Object Unique. Verifies that only one result matches type VSAN_ISCSI_TARGET_CONFIG in CMMDS. If more than one result is found, you must remove the incorrect information from CMMDS.
For example, to query the home object UUID, use the following command:
esxcli vsan iscsi homeobject get
Namespace Information
UUID: 23492958-ae67-d70a-9a02-020017f430de
Policy: (("hostFailuresToTolerate" i0) ("CSN" l1))
Is Compliant: true
To query the CMMDS information regarding VSAN_ISCSI_TARGET_CONFIG, use the following command:
cmmds-tool find -t VSAN_ISCSI_TARGET_CONFIG
owner=00000000-0000-0000-0000-000000000000(Health: Unhealthy) uuid=23492958-####-####-####-########0de type=VSAN_ISCSI_TARGET_CONFIG rev=5 minHostVer=0 [content = (i1 23492958-####-####-####-########0de l7)], errorStr=(null)
owner=00000000-0000-0000-0000-000000000000(Health: Unhealthy) uuid=41572958-####-####-####-########0de type=VSAN_ISCSI_TARGET_CONFIG rev=0 minHostVer=0 [content = (i1 41572958-####-####-####-########0de l2)], errorStr=(null)
If you find any other UUID type in this query, you can remove them by using the following command: cmmds-tool delete –u <uuid>
This health check verifies the integrity of the vSAN iSCSI target service home object. It also verifies that the configuration of the home object is valid.
Q: What does it mean when it is in an error state?
This health check includes multiple items, and the status of each item is shown in the Check column. This test checks the existence of the home object, whether the corresponding vSAN object is healthy, whether the storage policy is compliant. It also verifies the uniqueness of the home object, and whether the vSAN iSCSI service daemon can parse the configurations in the home object.
Q: How does one troubleshoot and fix the error state?
The vSAN iSCSI home object is located in the following directory: /vmfs/volumes/vsanDatastore/.iSCSI-CONFIG
The vSAN iSCSI target configuration file is located in the following directory: /vmfs/volumes/vsanDatastore/.iSCSI-CONFIG/etc/vit.conf
You can fix the following error conditions:
Home Object Exists. Verifies that the home object exists. If this file does not exist, disable and reenable the vSAN iSCSI target service.
Health Status. Verifies that the vSAN object corresponding to the iSCSI config file is healthy. If the check for this object reports an error, you might need to repair the related vSAN object.
Storage Policy Compliance. Verifies that the storage policy is compliant and is not out of date. If this check reports an error, select Cluster > Configure > Virtual SAN iSCSI Target Service to reapply the outdated storage policy or choose a compliant storage policy.
Metadata file status. Verifies that the configuration file in the vSAN iSCSI target service home object is present and that it can be parsed. If parser errors are reported, check whether any invalid names for the vSAN iSCSI entities or any invalid characters that might corrupt the configuration file.
Home Object Unique. Verifies that only one result matches type VSAN_ISCSI_TARGET_CONFIG in CMMDS. If more than one result is found, you must remove the incorrect information from CMMDS.
For example, to query the home object UUID, use the following command:
esxcli vsan iscsi homeobject get
Namespace Information
UUID: 23492958-ae67-d70a-9a02-020017f430de
Policy: (("hostFailuresToTolerate" i0) ("CSN" l1))
Is Compliant: true
To query the CMMDS information regarding VSAN_ISCSI_TARGET_CONFIG, use the following command:
cmmds-tool find -t VSAN_ISCSI_TARGET_CONFIG
owner=00000000-0000-0000-0000-000000000000(Health: Unhealthy) uuid=23492958-####-####-####-########0de type=VSAN_ISCSI_TARGET_CONFIG rev=5 minHostVer=0 [content = (i1 23492958-####-####-####-########0de l7)], errorStr=(null)
owner=00000000-0000-0000-0000-000000000000(Health: Unhealthy) uuid=41572958-####-####-####-########0de type=VSAN_ISCSI_TARGET_CONFIG rev=0 minHostVer=0 [content = (i1 41572958-####-####-####-########0de l2)], errorStr=(null)
If you find any other UUID type in this query, you can remove them by using the following command: cmmds-tool delete –u <uuid>
Additional Information
Feedback
Yes
No
Powered by
