Exactly Ulrich,there can be a better approach.
I am now having iscsiadm version 2.0-870,but still I am having a
problem in case of 2 targets having different NODE authentication.
My scenario
Suppose 2 targets (having different NODE AUTHENTICATION,assuming same
DISCOVERY AUTHENTICATION) from
HIMANSHU wrote:
Exactly Ulrich,there can be a better approach.
I am now having iscsiadm version 2.0-870,but still I am having a
problem in case of 2 targets having different NODE authentication.
My scenario
Suppose 2 targets (having different NODE AUTHENTICATION,assuming same
DISCOVERY
One more question analogues to this.
Suppose I login to 1st target from machine 30.12,it was having node
authentication.so I saved its credentials in iscsid.conf and then I
fired the discovery command followed by login command.It was
successful and those credentials also got stored in nodes and
HIMANSHU wrote:
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still after when I discover using 'iscsiadm -m discovery -t
sendtargets -p 192.168.30.12 -o new -o
delete',nodes and sendtargets entries gets overwritten.
Thank you very much Mike for all this.
Can you please give me the test src rpm for CentOS 5.4?
On Apr 27, 8:50 pm, Mike Christie micha...@cs.wisc.edu wrote:
HIMANSHU wrote:
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still after when I discover using 'iscsiadm -m discovery -t
sendtargets -p 192.168.30.12 -o new -o
delete',nodes and sendtargets entries gets overwritten.
I am also not performing any
Is there any method or should I debug to know the exact cause of this
overwriting problem?
On Apr 24, 6:29 pm, HIMANSHU makhu...@yahoo.co.in wrote:
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still after when I discover using
HIMANSHU wrote:
Thank you really.But I have not got the expected results.
Steps
1. iscsiadm -m discovery -t sendtargets -p 192.168.30.12 -o new -o
delete
2. iscsiadm -m node -T iqn.2009-04.com.systems:Target1 -p
192.168.30.12:3260 -o update -n node.startup -v automatic
so
Thank you very much all.Problem is solved,but I am having doubt.
@Mike
On Apr 21, 5:08 am, Mike Christie micha...@cs.wisc.edu wrote:
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
HIMANSHU wrote:
Yeah.This worked for me.I specified 'node.startup=manual' in
'iscsid.conf'.
so running update command to change it to 'automatic' only on login(or
I will give option for persistent connection across reboot).
But my problem these changes vanish after another discovery command.
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.
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
12 matches
Mail list logo
