public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <alewis@redhat.com>
To: linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] iSCSI Initiator Core Stack v1.6.1.20
Date: 24 Feb 2005 14:51:03 -0600	[thread overview]
Message-ID: <x05mzttr8aw.fsf@null.msp.redhat.com> (raw)
In-Reply-To: 1109187935.15154.164.camel@haakon

"Nicholas A. Bellinger" <nick@pyxtechnologies.com> 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?

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: alewis@redhat.com
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...


  parent reply	other threads:[~2005-02-24 21:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 19:45 [ANNOUNCE] iSCSI Initiator Core Stack v1.6.1.20 Nicholas A. Bellinger
2005-02-23 21:03 ` Jeff Garzik
2005-02-23 23:11   ` Nicholas A. Bellinger
2005-02-24 20:51 ` AJ Lewis [this message]
2005-02-25  7:50   ` Nicholas A. Bellinger
2005-02-25 15:18     ` AJ Lewis
2005-02-25 19:32       ` Nicholas A. Bellinger
2005-02-27 18:46   ` Dave Wysochanski
2005-02-28  8:22     ` Andre Hedrick
2005-02-28 13:41       ` Dave Wysochanski
2005-02-28 15:16     ` AJ Lewis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x05mzttr8aw.fsf@null.msp.redhat.com \
    --to=alewis@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox