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.
Explanation:
The first sentence in the screen-dump says it all:
connection to discovery address 10.1.2.20 failed (You do not have to look any further)
0
0
Really? I don’t get that information here. How are you determining the different subnets?
0
0
How to tell the iSCSI server’s subnet from the screenshot?
0
0
I was wondering this too! No idea how you can find out the subnet from this screenshot.
0
0
Stared at this for a while, but look at the address of the putty session you have open (10.1.1.65)
10.1.2.20 is a different subnet
0
0
THANK YOU! i couldnt figure out how there was a different subnet shown. Didnt see the title bar up top!
0
0
Well, I’m not sure because you can have one VMKernel adapter to Management and other one to Storage, so a IP session from Putty dosen’t mean that you have a different subnet…
0
0
Oh my gosh
0
0
So what the putty session is to the MGMT interface, the iSCSI network need not be on the same network, in fact should not be. Bogus answer. A or C could be correct.
0
0
C – vmk0 can reach 10.1.2.20, vmk3 cannot, the code below shows 0008 = transport issue
0008 0000
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012171
0
0
the 10.x.y.z range, whilst private is actually a class A address and therefore a default 8 bit subnet mask. Given that, esxi host 10.1.1.165 and lefthand array 10.1.2.20 are on the same subnet unless a default class C 24 bit subnet mask is used, and no subnet mask is given, nor is the absence of a router / firewall stated so if that is the right answer, shame on you vmware!
that link says 0008 is a timeout, perhaps caused by congestion or delay, and 0004 is network failure.
not convinced any way although A is likely but not proved – crap question 🙁
0
0
Adding my voice – shame on you VMware for the crappy question (if it was the only one or there were a few, it wouldn’t be as bad…)
0
0
routing not supported for port binding:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038869
0
0
Also for me the answer is C: look this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012171
0
0
perhaps c is incorrect because a vmkernel adapter can’t lose connectivity?
0
0
ターミナルセッションのウインドウタイトルが10.1.1.165なので。
0
0
A : The VMkernel adapter named vmk3 is on a subnet different from the iSCSI server’s subnet.
0
0
Almost same question as #255.
Answer is A since the initiator must be able to reach the target directly on the same subnet.
See: http://blogs.vmware.com/vsphere/2011/08/vsphere-50-storage-features-part-12-iscsi-multipathing-enhancements.html
0
0