Using the vSphere Web Client to display Software iSCSI Initiator properties reveals that one of two configured paths is Not Used.
The ESXi syslog events are as shown:
-- Exhibit —
-- Exhibit —
What is the root cause of the problem?
A. The VMkernel adapter named vmk3 is on a subnet different from the iSCSI server’s subnet.
B. The path will only become Active if the VMkernel adapter named vmk1 loses connectivity.
C. The VMkernel adapter named vmk3 has lost network connectivity.
D. The VMKernel adapter named vmk3 is on a different vSwitch from vmk1.
Correct Answer: A
Explanation/Reference:
Explanation:
A: When configuring a network for the Software iSCSI Initiator you also need to configure the IP settings because the IP address of the VMkernel and the subnet mask of the network are both required fields and you also need to enter a gateway if your IP address resides on a network other than the one on which you are configuring the port group. You must make sure when you enter the subnet mask that the NIC is set to the subnet of the storage system it connects to. I f the NIC you use with your iSCSI adapter, either software or dependent hardware, is not in the same subnet as your iSCSI target, your host cannot establish sessions from this network adapter to the target. The exhibit shows that one of the two configured paths are not used then this could be because vmk3 is on a different subnet.
Incorrect Answers:
B: When configuring a network for the Software iSCSI Initiator you need both vmk1 and vmk3 to be active and not just one of the two.
C: vmk3 did not loose connectivity from the network, it is in fact on a different subnet and thus only one path is being used by vSphere Web Client.
D: It is not the switch that is the issue, rather it is the subnet on which vmk3 and vmk1 resides.
References:
Lowe, S. & Marshall, N., Mastering VMWare vSphere 5.5, Wiley and Sons, Indianapolis, 2014, p. 334
