|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Asynchronous Message: Session TerminationMathhew, Mark, Matt & Santosh: Here is the new text for 2.17.1 1.1.1 iSCSI Event The codes used for iSCSI Asynchronous Messages (Events) are: 0 No iSCSI Event 1 Target is being reset. 2 Target requests Logout - the Parameter1 field indicates on what CID. 3 Target indicates it will drop the connection - the Parameter1 field will indicate on what CID while the Parameter2 field indicates, in seconds, the minimum time to wait before attempting to reconnect and Parameter3 the maximum time to reconnect after the initial wait (Parameter2). If the initiator does not attempt to reconnect within the time specified by Parameter 3 or Parameter 3 is 0 no other responses should be expected from the target for outstanding commands on this connection and the initiator should terminate them appropriately. A value of 0 for Parameter 2 indicates that reconnect can be attempted immediately. 4 Target indicates it will drop all connections - the Parameter2 field indicates, in seconds, the minimum time to wait before attempting to reconnect and Parameter3 the maximum time to reconnect after the initial wait (Parameter2). If the initiator does not attempt to reconnect within the time specified by Parameter 3 or Parameter 3 is 0 the session is terminated - in which case no other responses should be expected from the target for outstanding commands on this session and the initiator should terminate them appropriately. A value of 0 for Parameter 2 indicates that reconnect can be attempted immediately. Initiators can attempt to set/modify the values a target will use for Parameter2 and Parameter3 However - I am unclear if we should leave the initiator the degree of control implied by (innocuous looking) last statement. Thanks for helping make this text better. Julo
Home Last updated: Tue Sep 04 01:04:37 2001 6315 messages in chronological order |