RE: Review of the 07 draft

["John Hufferd" <hufferd@us.ibm.com>]

I am not sure that I feel real good about what you are stating here.  I
think the iSCSI Mode Pages are the persistent location for the iSCSI Modes,
but I think iSCSI will have the values in variables that they have in
memory/cache that iSCSI uses ongoing.  If a SCSI command was to change
those values I am not sure that iSCSI will see the changes.

I thought we had previously agreed (for the reasons above) that iSCSI sets
its pages and SCSI sets its pages.

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136
Internet address: hufferd@us.ibm.com


"Robert Griswold" <rgriswold@Crossroads.com>@ece.cmu.edu on 08/09/2001
01:36:14 PM

Sent by:  owner-ips@ece.cmu.edu


To:   "Eddy Quicksall" <ESQuicksall@hotmail.com>, Jim
      Hafner/Almaden/IBM@IBMUS
cc:   <ips@ece.cmu.edu>
Subject:  RE: Review of the 07 draft



Eddy:

I actually have no problem with all mode pages (SCSI and iSCSI) being
accessible and changeable from standard SCSI mode commands.  My initial
response to this section was to propose a method that would be
acceptable to the authors of the iSCSI draft.  If there is desire in the
group to allow mode pages for the entire target to be manipulated from
the SCSI level, I think that is a better idea that the one I proposed.
I would assume that an iSCSI aware SCSI utility would understand the
iSCSI specific settings, and allow the user to make those changes.  What
I am really against, is the ability to modify standard SCSI mode page
settings from text messages, as that could lead to target behavior
changes outside of the understanding of the SCSI nexus.

To recap your thinking:  Allow iSCSI text messages to modify and read
iSCSI only mode settings (potentially allowing the reading if SCSI mode
settings), but allow SCSI mode commands to modify and read all target
mode settings, including iSCSI settings.  Is that what you are saying.
If so, I agree.

Bob

Robert Griswold
Technologist
Crossroads Systems, Inc.
512-928-7272

 -----Original Message-----
From:     Eddy Quicksall [mailto:ESQuicksall@hotmail.com]
Sent:     Thursday, August 09, 2001 2:08 PM
To:  Robert Griswold; Jim Hafner
Cc:  ips@ece.cmu.edu
Subject:  Re: Review of the 07 draft

I don't like the idea of not letting a user of a SCSI utility be able to
change some of the parameters for iSCSI. Because they may be relevant to
him
and there may not be a user interface to the iSCSI driver. pSCSI sets
these
low level parameters via a standard mode set, so why not iSCSI?

It would be best if we could work out something where only the SCSI
layer
can set the mode pages. That would solve everything.

Eddy

----- Original Message -----
From: "Jim Hafner" <hafner@almaden.ibm.com>
To: "Robert Griswold" <rgriswold@Crossroads.com>
Cc: <ips@ece.cmu.edu>
Sent: Friday, August 03, 2001 5:26 PM
Subject: Re: Review of the 07 draft

> Well, in fact, the draft is supposed to say that MODE_SELECT for the
> transport-specific mode page will NOT be done via SCSI, only via Text
> commands.  I read that as saying that from the SCSI layer, all fields
in
> these pages are "unchangeable" (even though they can change in the
iSCSI
> layer).  Of course, the draft doesn't say whether MODE PARAMETERS HAVE
> CHANGED unit attentions get thrown up at the SCSI layer when this
happens
> at the iSCSI layer.... You later have a clarifying question (Section
3) on
> this as well.
>
> Regards,
> Jim Hafner
>
>
>
>