vSAN Health Service - iSCSI target service - Network configuration - vSAN iSCSI Virtual IP Ownership
search cancel

vSAN Health Service - iSCSI target service - Network configuration - vSAN iSCSI Virtual IP Ownership

book

Article ID: 389401

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This article explains the purpose and details of Virtual IP network configuration health check for vSAN iSCSI target service and provides details on why it might report the error and how to fix the error state.

Environment

VMware vSAN 9.0

Resolution

Q: What does the 'iSCSI target service health check - Virtual IP ownership check' do?

It checks if the iSCSI target service virtual IP ownership has mistake or not.

  • The column 'Issue' indicates the virtual IP ownership issue detected.
  • The column 'Result' indicates the error level (warning/error).
  • The column 'Error' indicates the detail information about detected issue.

Note: It is expected that if no warning state reported in the check result.

 

Q: What does it mean when it is in a warning state?

The detected issue and it indicate error can refer to the following table.

Issue Error indicated
Owner not found Virtual IP owner host is not found
Virtual IP not bound Virtual IP address is not set to the VMkernel adapter on the owner host
Multiple owner detected Virtual IP is assigned to multiple owner hosts, the invalid owner host name will be listed

In virtual IP ownership check, when the vSAN iSCSI target service virtual IP is enabled, but the virtual IP is not assigned to any host, then the health check will report issue 'Owner not found'. In this case, the virtual IP cannot work as expected.

In virtual IP ownership check, when the backend detects No IP on the iSCSI virtual IP used vmknic on some host(s), then the health check will report issue 'virtual IP not bound'.

In virtual IP ownership check, when the backend detects the virtual IP is assigned to multiple hosts, then the health check will report issue 'Multiple owner detected', with the host name which should not be the owner.

Q: How does one troubleshoot and fix the error state?

Sometimes, the iSCSI target service virtual IP ownership health issue can be caused by other correlated health issues, like 'Host Connectivity failure', 'Cluster partition', 'Consistent Config issue' or 'iSCSI home object status test failure'. Please check the correlation failure firstly and see if they can be fixed. After fixed the correlation issues, re-run the iSCSI target service check and check if virtual IP ownership issue is still there.

If the virtual IP ownership health issue still exists, then try to remediate it with some manual steps as below:

  • 'Owner not found':  Please navigate to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service. (Under this situation, the iSCSI virtual IP essentially not available for iSCSI client,  so re-enable is necessary).
  • 'virtual IP not bound': Please navigate to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service (Under this situation, the iSCSI virtual IP essentially not available for iSCSI client,  so re-enable is necessary).
  • 'Multiple owner detected': Please navigate to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service (Under this situation, the iSCSI virtual IP essentially not available for iSCSI client,  so re-enable is necessary).

Additional Information

Powered by Wolken Software