Andre Hedrick wrote:


Hi Dave,

If the NetAPP target is misconfigured, why would it even allow any unknown
initiator to go beyond discovery session? It appears that a
semi-successful lun scan has happened or am mis reading the report?


I think you're misreading the report and/or don't understand how our target
works.

If I read deeper into your comments, does the target support ACL's?
If yes, then how did any access to the target by an unauthorized initiator
happen?


The LUN mapping and security are technically different lists.  The
default  security policy (unless set otherwise) is AuthMethod=none.
By default though, you don't get any LUNs until you explicitly
map them.

Also would you be kind enough to reveal what device class 31 is to conform
to under scsi?


I'll try to get more information on what's going on here.  I didn't actually
repro this, so I don't have a trace either - was just commenting based
on the mail.

Cheers,

Andre

On Sun, 27 Feb 2005, Dave Wysochanski wrote:

> AJ Lewis wrote:
>
> > "Nicholas A. Bellinger" <[EMAIL PROTECTED]> writes:
> >
> > > The following is the first public release of the PyX Technologies iSCSI
> > > Initiator Core Stack v1.6.1.20 for Linux 2.6.11-rc4. This is a full
> > > featured iSCSI Initiator stack that is capable of mulitplexing coast to
> > > coast across multiple independant backbone providers using various
> > > network transports _TODAY_. This is the first release of the core
> > stack
> > > and assoicated userspace tools, the accompanying authentication daemon
> > > will be released shortly.
> >
> > Very cool - glad you're releasing this. I've gotten this setup and
> > running, but I can't seem to talk to my iscsi target. The initiator
> > detects it, but it can't recognize the type:
> >
> > iCHANNEL[0] - No defined iSCSI Authentication Methods, skipping
> > SecurityNegotiation phase.
> > iCHANNEL[0] - iSCSI login successful on CID: 0 to 192.168.44.19:3260,2
> > iCHANNEL[0] - Incremented iSCSI connection count to 1 to node:
> > iqn.1992-08.com.netapp:sn.33615311
> > iCHANNEL[0] - Established iSCSI session to node:
> > iqn.1992-08.com.netapp:sn.33615311
> > iSCSI Core Stack[1] - Incremented number of active iSCSI sessions to 1.
> > scsi: unknown device type 31
> > Vendor: NETAPP Model: LUN Rev: 0.2
> > Type: Unknown ANSI SCSI revision: 04
> >
> > Any ideas on why this wouldn't be working? Is there a configuration
> > step I'm missing?
> >
> Make sure the initiator name is in the igroup on the filer for
> any luns that you want mapped to the intiator.
>
> I think what you're seeing is not a real LUN, but the config LUN
> or something like that, probably the result of the initiator name
> not being in the igroup (see "igroup add" command on the filer).
>
> > Also, are you planning on updating the docs for the user tools at all?
> > There are several steps missing in the current README, and the man
> > page lists some parameters incorrectly and misses other entirely.
> >
> > I'm looking forward to getting this working.
> > --
> > AJ Lewis Voice: 612-638-0500
> > Red Hat Inc. E-Mail: [EMAIL PROTECTED]
> > 720 Washington Ave. SE, Suite 200
> > Minneapolis, MN 55414
> > > > Current GPG fingerprint = D9F8 EDCE 4242 855F A03D 9B63 F50C 54A8
> > 578C 8715
> > Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
> > many keyservers out there...
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> > the body of a message to [EMAIL PROTECTED]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to