Re: Initiator-detected format or digest errors

["Matt Wakeley" <matt_wakeley@agilent.com>]

The target can log the reject for further analysis.

Why do you keep trying to eliminate simple things that can be used for
debugging?

-Matt

julian_satran@il.ibm.com wrote:
> 
> Matt,
> 
> 3 reasons:
> 
> a. the initiator drives recovery. What can a target do with the reject?
> (he is probaly in need of a reset)
> 
> b.the initiator is unaware of the target state after thhe error
> 
> c.there is reject command (and response) -:)
> 
> Julo
> 
> Matt Wakeley <matt_wakeley@agilent.com> on 06/04/2001 00:43:08
> 
> Please respond to Matt Wakeley <matt_wakeley@agilent.com>
> 
> To:   IPS Reflector <ips@ece.cmu.edu>
> cc:
> Subject:  Re: Initiator-detected format or digest errors
> 
> Why not send a reject back to the originator of the bad frame, and just let
> the task time out?
> 
> -Matt
> 
> julian_satran@il.ibm.com wrote:
> >
> > Tom,
> >
> > An initiator will pass the appropriate response to the SCSI layer and
> will
> > abort the task if it can identify one.  Further behavior of initiators
> and
> > targets is implementation dependent.
> >
> > 6.2 specifies this.
> >
> > Julo
> >
> > "Thomas McSweeney" <rf42tpme@us.ibm.com> on 04/04/2001 13:57:20
> >
> > Please respond to "Thomas McSweeney" <rf42tpme@us.ibm.com>
> >
> > To:   ips@ece.cmu.edu
> > cc:
> > Subject:  Initiator-detected format or digest errors
> >
> > Section "2.20 Reject" talks about the target receiving a bad frame and
> > sending Reject.  What should an Initiator do if it receives a PDU with a
> > format or digest error?  Should it send Reject?  If so, we'll need to
> > ensure that the Initiator fields of the MIB include an object to count
> > Reject commands transmitted.
> >
> > Tom McSweeney
> > iSCSI Development, Storage Systems Group, IBM
> > Email: rf42tpme@us.ibm.com
> > Phone: (USA) 919-254-5634  (tie line: 444-5634)
> > Fax:   (USA) 919-254-0391  (tie line: 444-0391)