[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to deal with PROTOCOL ERROR on iscsi target side

To: <ips@xxxxxxxx>
Subject: How to deal with PROTOCOL ERROR on iscsi target side
From: HUJason <hzj_wuying@xxxxxxxxxxx>
Date: Thu, 17 Apr 2008 16:22:08 +0800
Delivered-to: ips@xxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <BAY135-W8D5029F9222302060E3B2F3EA0@xxxxxxx>
References: <4804B03C.6060507@xxxxxxxxxxxx> <OFA528E763.71479425-ON8525742C.005B02F4-8825742C.005F18F1@xxxxxxxxxx> <BAY135-W8D5029F9222302060E3B2F3EA0@xxxxxxx>
Sender: ips-bounces@xxxxxxxx

Dears,

If target works on ERL == 0 and meets a PROTOCOL ERROR condition that it can not figure out PDU length any more(no FIM...), what should the target do for session recover? Can it simply drop the TCP connection?

Many Many Thanks!
Jason

“七件武器，七种完美” 立刻体验！

_______________________________________________
Ips mailing list
Ips@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ips

Follow-Ups:
- Re: How to deal with PROTOCOL ERROR on iscsi target side
  - From: Black_David

References:
- Calculating the VA in iSER header
  - From: Erez Zilber
- Re: Calculating the VA in iSER header
  - From: Mike Ko
- Send Reject PDU when orignal to-be-rejected PDU is not available
  - From: HUJason

Prev by Date: Re: Send Reject PDU when orignal to-be-rejected PDU is notavailable
Next by Date: Re: [ofa-general] Re: Calculating the VA in iSER header
Previous by thread: Re: Send Reject PDU when orignal to-be-rejected PDU is notavailable
Next by thread: Re: How to deal with PROTOCOL ERROR on iscsi target side
Index(es):
- Date
- Thread

[IETF] [Linux iSCSI] [Linux SCSI] [Linux Resources] [Yosemite News] [IETF Announcements] [IETF Discussion] [SCSI]