Subject: Re: iSCSI initiator CHAP failure
To: Jeff Rizzo <riz@NetBSD.org>
From: Jay Nelson <jdn@bga.com>
List: current-users
Date: 11/28/2007 13:52:48
On Tue, Nov 27, 2007 at 08:56:29PM -0800, Jeff Rizzo wrote:
> Jay Nelson wrote:
> > sks# iscsifs -u jdn -h acp /iscsi
> > pid 13232:/usr/src/dist/iscsi/src/initiator.c:1912: ***ERROR*** Bad Status-Class: got 2, expected 0
> > Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1912: ***ERROR*** Bad Status-Class: got 2, expected 0
> > pid 13232:/usr/src/dist/iscsi/src/initiator.c:1737: ***ERROR*** initiator_cmd_t failed
> > pid 13232:/usr/src/dist/iscsi/src/initiator.c:566: ***ERROR*** login_phase_i() failed
> > Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1737: ***ERROR*** initiator_cmd_t failed
> > Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:566: ***ERROR*** login_phase_i() failed
> > pid 13232:/usr/src/dist/iscsi/src/initiator.c:1084: ***ERROR*** enqueue_worker: discovery_phase() failed (ignoring command)
> > Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1084: ***ERROR*** enqueue_worker: discovery_phase() failed (ignoring command)
> >
> > And on the target:
> >
> > Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/parameters.c:648: ***ERROR*** Initiator authentication failed 79 1d
> > Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/target.c:1087: ***ERROR*** login_command_t() failed
> > Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/target.c:1207: ***ERROR*** execute_t() failed
> >
> >
> FWIW, I've been playing with the initiator under MacOS 10.5.1 (ppc), and
> this is exactly what I see. I'm looking to see if I can learn anything
> new this evening - I'll be playing with it on an intel machine.
>
> +j
I had trouble configuring an AIX initiator back to a NetBSD target
some time ago -- took it to IBM level 3 support as well with no luck. I
lost experimental access to those machines before I could resolve the
issue. Details are lost and I don't know if that was related to
this problem or not.
In the next couple of days, I'll spin up a target on the other sparc
box and see what results.
-- jay