iscsiadm: No records found!

[nithink...@gmail.com]

Hello all,

i have run
iscsiadm -m discovery -t sendtargets -p 10.129.1.71

after this when i restart open-iscsi, its showing that no records
found
/etc/init.d/open-iscsi restart

* Disconnecting iSCSI
targets
[ OK ]
* Stopping iSCSI initiator
service
[ OK ]
* Starting iSCSI initiator service
iscsid
[ OK ]
* Setting up iSCSI
targets
iscsiadm: No records found!

[ OK ]

Can anybody tell what could be the problem?

[Don Williams]

You provided almost no information about the iSCSI target, the version of
open-iSCSI, Distro or Kernel rev.

When you run the discovery command does it find any targets?

One suggestion. Add :3260 to the end of the discovery command.

Don

[nithink...@gmail.com]

On Feb 14, 8:22 pm, "Don Williams" <don.e.willi...@gmail.com> wrote:
> You provided almost no information about the iSCSI target, the version of
> open-iSCSI, Distro or Kernel rev.
>

kernel :- 2.6.22-14-generic
OS:- Ubuntu Gutsy
open-iscsi version:- 2.0.865-1

> When you run the discovery command does it find any targets?
>

When i run discovery command there is no output.

> One suggestion. Add :3260 to the end of the discovery command.

I tried this. No result
> Don
>
Apart from this i ll show you the iscsid.conf

node.startup = automatic
node.session.auth.authmethod = CHAP
node.session.auth.username = xxxxxx
node.session.auth.password = xxxxxxx
discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = xxxxxxxx
discovery.sendtargets.auth.password = xxxxxxx
node.session.timeo.replacement_timeout = 120
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 10
node.conn[0].timeo.noop_out_timeout = 15

node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768

When i run iscsid -f -d 8
The following was the output
root@venus:/etc/iscsi# iscsid -f -d 8
iscsid: transport class version 2.0-724. iscsid version 2.0-865
iscsid: in ctldev_open
iscsid: created NETLINK_ISCSI socket...
iscsid: InitiatorName==iqn.1993-08.org.debian:01:7b3b391c825
iscsid: an InitiatorAlias= is required, but was not found in /etc/
iscsi/initiatorname.iscsi
iscsid: InitiatorName=iqn.1993-08.org.debian:01:7b3b391c825
iscsid: InitiatorAlias=venus
iscsid: iscsid_exit
iscsid: in ctldev_close
iscsid: reaped pid 6626, reap_count now 0
iscsid: poll result 1
iscsid: poll result 1
iscsid: poll result 1

The last three lines of above output was the result of running the
iscsiadm command for discovery.

> -----Original Message-----
> From: open-...@googlegroups.com [mailto:open-...@googlegroups.com] On
>

> Behalf Of nithinkumar...@gmail.com

[Don Williams]

What iSCSI target are you using?

Are you using a packaged version of the open-iSCSI initiator or did you
build it from the code on the open-iSCSI website?

You should also create an /etc/iscsi/initiatorname.iscsi

Don

[Nithin Dara]

On Thu, Feb 14, 2008 at 10:28 PM, Don Williams <don.e.w...@gmail.com> wrote:

What iSCSI target are you using?

The target machine is the following:-
 http://www.raidstore.com/RaidProductDetail.asp?ItemID=551
Its a NAS Box. The web-interface provides an interface to select which authentication to use and etc

When i do nmap -p3260 on this machine
PORT     STATE SERVICE
3260/tcp open  unknown

its shows that 3260 port is open...

 Are you using a packaged version of the open-iSCSI initiator or did you

iam using the packaged version of open-iscsi

build it from the code on the open-iSCSI website?

 You should also create an /etc/iscsi/initiatorname.iscsi

 Its already there.

[Mike Christie]

nithink...@gmail.com wrote:
> Apart from this i ll show you the iscsid.conf
>
> node.startup = automatic
> node.session.auth.authmethod = CHAP
> node.session.auth.username = xxxxxx
> node.session.auth.password = xxxxxxx
> discovery.sendtargets.auth.authmethod = CHAP
> discovery.sendtargets.auth.username = xxxxxxxx
> discovery.sendtargets.auth.password = xxxxxxx

Maybe we should start with a really simple setup. If you remove all the
CHAP settings from the target and initiator, does it work? If you then
do one way chap does it work?

[nithink...@gmail.com]

On Feb 14, 10:23 pm, Mike Christie <micha...@cs.wisc.edu> wrote:

I have removed all the CHAP setting from both the initiator as well as
target.
Still the same problem.

[sushan...@gmail.com]

Hi Nithin

Are you still facing the same problem?

Try commenting all the lines in open filer machine "/etc/initiator.deny".

And also check iptables you could just stop or edit "# service iptables stop"

Reboot the machine.

[kanha...@gmail.com]

Thanks Nithin,

I was also facing same problem and commented /etc/initiator.conf and now I am able to search devices on linux client nodes.

[vinodm...@gmail.com]

Thanks Sushanth ..... after lot of google, your tips works... Thanks again... heartly thankfull ...