Re: [Etherboot-developers] Solaris COMSTAR T10 Interpretation

[John W. <bit...@gm...>]

Hi Michael,

I'm not sure from reading those threads, that COMSTAR is actually
sending error messages with CHECK CONDITION, but this subject is
currently at the edge of my current understanding of
ISCSI/COMSTAR/gPXE.

In any case, your explanation is exactly what I wanted to learn.

Thanks,
John


On Fri, Jul 10, 2009 at 11:59 AM, Michael Brown<mb...@fe...> wrote:
>
> gPXE never scans LUNs, because the LUN must be specified by the user in any
> case as part of the root-path, as per RFC 4173.  It therefore does not
> contain the code to rescan LUNs, and even if it did, would not have anything
> to then do with the information (except possibly to report "this LUN does not
> exist" to the user, which could be better accomplished in other ways).
>
> COMSTAR is behaving badly by reporting spurious error messages in a non-error
> condition, and retrying the same initial command up to 10 times is gPXE's way
> of working around this kind of behaviour.
>
> Michael
>