Test iSCSI paths from the host to the storage cluster
To ensure successful storage failover and data mobility, you need to ensure that you have two paths from the host to every node in the storage cluster. Because the number of paths advertised by the iSCSI target is limited, you need to ping the storage cluster ports from the host.
You must know the IP address or host name of all of the logical interfaces (LIFs) to be used for iSCSI paths.
LUNs are mapped to a subset of the initiators in the igroup to limit the number of paths from the host to the LUN.
By default, only paths from the host to the node containing the storage virtual machine (SVM) where the LUN was created, and paths to the HA partner of that node, are visible to the host.
You still must create and test paths from the host to every node in the cluster, but the host can access only those paths on the owning node and its HA partner.
You should use the default LUN mapping behavior.
Only add nodes in other HA pairs to the LUN map in preparation for moving the LUN to a different node.
From the ESX host, use the
pingcommand to verify the path to the first LIF.
pingcommand is available from the ESX service console.
pingcommand to verify connectivity to each iSCSI LIF on each node in the cluster.