|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI: clearing SCSI objectsThanks, that was the missing link I think ... I thought since DefaultTime2Wait & DefaultTime2Retain were only for ErrorLevel 2 because that is said in the logout regarding Time2Wait and Time2Retain. But if the default versions apply to ErrorLevel 0, that is exactly what I want. Also, paragraph 12.16 does not talk about exceeding DefaultTime2Retain causing an I_T Nexus Loss notification (which is the only iSCSI thing that can clear a SCSI object). Can you confirm that the following would be correct? - I negotiate for ErrorLevel 0 - I negotiate for DefaultTime2Wait and DefaultTime2Retain = 0 - I get a logout - I clear all SCSI objects other than the ones you mention below. Eddy -----Original Message----- From: Mallikarjun C. [mailto:cbm@rose.hp.com] Sent: Thursday, May 01, 2003 8:34 PM To: ips@ece.cmu.edu Subject: Re: iSCSI: clearing SCSI objects > First, am I correct in the above? Not completely. If there are no active FFP connections in the iSCSI session, the session will eventually come to an end ([Default]Time2Wait/Return). That is when the associated I_T Nexus Loss notification is generated, and with it, all the SCSI objects that are considered attributes of that instance of I_T Nexus are cleared. Note however that there may be SCSI objects that are not linked to the life of an instance of I_T Nexus - this is a SCSI issue (and F.2 does refer to it). -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Hewlett-Packard MS 5668 Roseville CA 95747 cbm@rose.hp.com ----- Original Message ----- From: "Eddy Quicksall" <eddy_quicksall@ivivity.com> To: <ips@ece.cmu.edu> Sent: Thursday, May 01, 2003 11:58 AM Subject: clearing SCSI objects > I have a concern regarding a logout followed by login's with a different > ISID from the same initiator device. > > Here is my concern: > > - the target must keep state information for the initiator port > after a logout (such as a reservation - but not limited to that). This is > because section F.2 says only an I_T Nexus Loss can effect clearing actions > on SCSI objects. > - If a target receives a logout, then another login from another > initiator (or even another login from the same initiator device but a > different ISID) then it must have resources available because it can't clear > the SCSI objects from the logged out session. > - The resources can become stale and the target could run out of > resources. > > First, am I correct in the above? If not please explain. > > If this is correct, I have not found anything in the spec that says how long > the SCSI objects must be kept around. > > Eddy > >
Home Last updated: Thu May 01 22:19:18 2003 12565 messages in chronological order |