|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Recovery Within Connection - Command Restart
- To: <ips@ece.cmu.edu>
- Subject: Recovery Within Connection - Command Restart
- From: "shaileshm" <shaileshm@aarohicommunications.com>
- Date: Wed, 19 Dec 2001 14:06:44 -0800
- content-class: urn:content-classes:message
- Content-Type: multipart/alternative;boundary="----_=_NextPart_001_01C188D9.71D58E0A"
- Sender: owner-ips@ece.cmu.edu
- Thread-Index: AcGIEiO5npEh3bGLQLeDQBNdN6r5MAAxv22g
- Thread-Topic: Recovery Within Connection - Command Restart
- The
draft says a) Requests not acknowledged for a long time….. Does the
SCSI timeout’s introduce the notion of time, or does iscsi has to
have timeout’s at the transport layer. Also for detecting connection
failures don’t the NOP’s have to be timed.
- Request
not acknowledged would be most of the time due to a header digest errors
at the target end. If the header is bad how would one know at the target,
that this was a command PDU v/s a Data PDU, since the target will have to
implement a command scoreboard if it is a command PDU.
- Usage
of Reject PDU talks about Reject on Command PDU : however the error codes
for Reject PDU do not indicate a command PDU error.
- Is the recovery R2T different
from the usual R2T.
These things are not clear from the draft !
Shailesh Manjrekar.
|
Home
Last updated: Sat Dec 22 00:17:48 2001
8190 messages in chronological order
|
