vSAN Health Service - iSCSI target service - Network configuration - Virtual IP network configuration
Article ID: 389286
Updated On:
Products
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 network configuration' do?
The virtual IP network configuration is under the 'vSAN iSCSI target service' - 'Network configuration' health check group. Only when the vSAN iSCSI virtual IP is enabled, the virtual IP network configuration check will be covered and reported.
This check covers the following health check items:
- Check the virtual switch for virtual IP is the same as configuration.
- Check the port group(s) network status.
- Check VLAN ID is consistent with virtual IP configuration.
- Check the port group(s) network status.
- Check the virtual IP used vmknics on hosts.
- Check the network for distributed virtual switch.
The health check will show as green status if all the network configurations are expected, below is the example:
If virtual IP for vSAN iSCSI target service is not enabled, the virtual IP related network health check will not be triggered. The network configuration health check will be similar as below without virtual IP:
Q: What does it mean when it is in an warning state? How does one troubleshoot and fix the error state?
| Warning | Details | |
| 1 | The vmknic for virtual IP is not found or not expected on some host(s) |
Description: Remediation: Navigate to "vSAN Services" page and go to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service. Please note that, reconfiguring virtual IP may cause temporary IO failure if the initiator is configured with virtual IP. Please pause the initiator workload before reconfiguring the virtual IP and checking if the health issue is resolved. |
| 2 | Cannot find the virtual switch used by virtual IP on some host(s) |
Description: vSAN reports this issue when detecting that the virtual switch used by virtual IP is not found or not expected on some host(s). Diagnose: Check the detected host(s), navigate to "Virtual switches" view of the detected hosts to check if the virtual switch is created successfully. Remediation: Navigate to "Virtual switches" view to create the virtual switch for virtual IP firstly, then navigate to the "vSAN cluster configuration consistency" health check and click the remediation button. After the remediation, re-run the health check service. |
| 3 | Cannot find the port group used by virtual IP |
Description: vSAN reports this issue when detecting that the port group used by virtual IP is not found or not expected on some host(s). Diagnose: Check the detected host(s), navigate to "Virtual switches" view of the detected hosts to check if the port group is created successfully. Remediation: Navigate to "vSAN Services" page and go to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service. Please note that, reconfiguring virtual IP may cause temporary IO failure if the initiator is configured with virtual IP. Please pause the initiator workload before reconfiguring the virtual IP and checking if the health issue is resolved.
|
| 4 | Unexpected VLAN ID on the port group used by virtual IP |
Description: vSAN reports this issue when the VLAN ID of virtual IP used port group mismatches with the VLAN ID used for enabling virtual IP. Diagnose: Check the detected host(s), navigate to "Virtual switches" view of the detected hosts to see if the VLAN ID is expected. Remediation: Navigate to the detected port group(s), set the VLAN ID to the one stored in the virtual IP configurations. |
| 5 | Virtual switch is not expected as virtual IP configuration |
Description: vSAN reports this issue when the actual virtual switch used by virtual IP on some host(s) is inconsistent with virtual IP configuration. Diagnose: Check the host(s) detected, navigate to "Virtual switches" view of the detected hosts to see the port group used by virtual IP is created on the expected standard switch. Remediation: Navigate to "vSAN Services" page and go to the "vSAN iSCSI Target Service" section, then disable and re-enable vSAN iSCSI target virtual IP service. Please note that, reconfiguring virtual IP may cause temporary IO failure if the initiator is configured with virtual IP. So please pause the initiator workload before reconfiguring the virtual IP and checking if the health issue is resolved. |
| 6 | No valid uplink bound on the virtual switch used by virtual IP |
Description: vSAN reports this issue when no valid physical network adapter assigned to the virtual IP used standard switch. Diagnose: Check the detected host(s), navigate to "Virtual switches" view of the detected hosts to check which physical network adapter is used. Navigate to "Physical adapters" view to check the physical network adapter status. Remediation: Assign the virtual IP used virtual switch with valid physical network adapter. |
| 7 | Some host(s) in this cluster are not managed by the given distributed virtual switch |
Description: vSAN reports this issue when some host(s) in the cluster are not managed by the distributed virtual switch used by virtual IP. It is likely that some host(s) are removed from the management of the distributed virtual switch after configuring the virtual IP. This issue will possibly make the virtual IP and iSCSI target not work normally, if the host out of management is assigned to the virtual IP owner. Diagnose: Check the detected host(s), navigate to the "Virtual switches" view and see the list of managed hosts. Remediation: Re-add the missing host(s) under the management of the distributed virtual switch used by virtual IP, and then trigger a new run for vSAN health check, see if the issue is resolved. |
| 8 | The given port group is not found in this cluster |
Description: vSAN reports this issue when the port group is not found in this cluster. It is likely that the port group is removed from the cluster after the virtual IP is enabled successfully. This issue will cause the virtual IP network not work properly and possible I/O failure. Diagnose: Check the "Virtual switches" view, see if the detected port group is missing or not. Remediation: If the detected port group is missing, create a new port group in the VC level, then re-configure the virtual IP in the "vSAN iSCSI Target Service" section with the new created port group. Please note that, reconfiguring virtual IP may cause temporary IO failure if the initiator is configured with virtual IP. So please pause the initiator workload before reconfiguring the virtual IP and checking if the health issue is resolved. |
| 9 | Host(s) in the cluster and managed by the port group without uplink for virtual IP is not allowed |
Description: vSAN reports this issue when some host(s) in the cluster and managed by the configured distributed port group used for virtual IP, but no uplink bound to the host(s). This issue will essentially break the virtual IP service, if the detected host is assigned to the virtual IP owner. Diagnose: Navigate to "Physical adapters" view of each detect host, check if the physical network adapter status bound on the configured port group. Remediation: Assign the active uplink for the detected host(s), and then re-run the health check service to see if the issue is resolved. |
Additional Information
Feedback
