I discovered 2 machine,192.168.7.50(containing 10 targets,out of which
performed login on 2) and 192.168.7.51(containing 5 targets,out of
which performed login on 3).I am using IET target and 'iscsi-initiator-
utils-6.2.0.868-0.7.el5' initiator.
So at present there are 5 connections on
On 17 Apr 2009 at 15:22, dave wrote:
Long post, but please bear with me :)
This post is related to my previous post at:
http://groups.google.com/group/open-iscsi/browse_thread/thread/4569bc674383145a/e6c2e4320ec401f5?lnk=gstq=device+not+ready#e6c2e4320ec401f5
My situation:
I have
On 20 Apr 2009 at 2:46, HIMANSHU wrote:
I discovered 2 machine,192.168.7.50(containing 10 targets,out of which
performed login on 2) and 192.168.7.51(containing 5 targets,out of
which performed login on 3).I am using IET target and 'iscsi-initiator-
utils-6.2.0.868-0.7.el5' initiator.
A few more comments on this failure:
This may be a problem with how the check response is being processed
by the iSCSI stack...possibly due to data digest.
The Inquiry command goes out, the response is received with data
digest, and appears to be accepted. A Test Unit Ready command then
goes
HIMANSHU wrote:
I discovered 2 machine,192.168.7.50(containing 10 targets,out of which
performed login on 2) and 192.168.7.51(containing 5 targets,out of
which performed login on 3).I am using IET target and 'iscsi-initiator-
utils-6.2.0.868-0.7.el5' initiator.
So at present there are 5
Joer wrote:
A few more comments on this failure:
This may be a problem with how the check response is being processed
by the iSCSI stack...possibly due to data digest.
The Inquiry command goes out, the response is received with data
digest, and appears to be accepted. A Test Unit Ready
