|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Aug 20, 2007, at 11:18 AM, RAMS wrote:
Please see below between <RAM> </RAM>
DefaultTime2Retain has a default value, so if you're happy with that, you don't need to negotiate. Ever.
If the target makes an offer, the initiator has to answer.
In my opinion, ERL 1 doesn't change DefaultTime2Retain's meaning much. ERL 1 is about recovery within a connection, and leaves what happens when a connection fails up in the air. Since DefaultTime2Retain deals with what happens when a connection fails, they deal with orthogonal concepts.
In my experience, the thing that adds lots of complexity isn't directly going to ERL 2, it's supporting MaxConnections > 1. A session with two FFP connections and ERL 0 has a lot of recovery stuff going on. Put another way, most of what people think of for ERL 2 actually comes with ERL 0 && MaxConenctions > 1.
DefaultTime2Retain directly matters for ERL 0 as it sets a timer for the session to fail out. Session failure constitutes an I-T Nexus loss, which can have SCSI consequences.
If all your target supports is READ(10) and WRITE(10) (or READ(16) and WRITE(16)) and one connection, you won't notice DefaultTime2Retain much. But if you support more features, say multiple connections and/or SCSI Reservations (Persistent or otherwise), then it becomes important.
_______________________________________________ Ips mailing list Ips@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ips