Re: iSCSI: login issue - partial consensus call

[Sandeep Joshi <sandeepj@research.bell-labs.com>]

John,

Is this what you are referring to ? (Sec 1.3 of Naming & Discovery)

> b) The ISID name space of the iSCSI Initiator should be partitioned  
>       among the intiator portal groups.

How do you perceive this will be achieved in practice ?

This can turn out to be an nightmare for HBA vendors.
IRQ settings, jumpers, or setup programs which run at boot 
instantly come to mind.  

Ideally, ISIDs should work as SCAM works but that would involve 
adding a mid-layer to OSes, to distribute that ISID name space.
Modifying OSes in the field is tough, as we all know.

I realize the standard wont mandate such configuration items
but I'd rather we not add rules which would force such
configuration tweaks to become necessary.  

We should reconsider the above rule and its consequence on
the login issue Nick brought up.

Regards,
-Sandeep

John Hufferd wrote:
> 
> By the way, the OS is also suppose to have a way to hand out (partition up)
> ISIDs to the various iSCSI Initiator functions, whether they are Software
> or Hardware.
> 
> So, even though,  I was initially swayed by Nick's Arguments -- we require
> the OS to partition up the ISID space and hand out specific ISIDs or ranges
> of ISIDs (in some manor) to the iSCSI Initiator functions (regardless of
> whether they are in Software or Hardware) -- I do not now see, if the
> implementation is as specified in our spec., how there is a conflict in
> ISID.
> .
> .
> .
> 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