|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: iSCSI: Logout hierarchyNothing can come after the login response on the same connection. Times can be set for any values (the negotiated are defaults). Tasks to be recovered are individually set to to Time2Retain. Any other logout can occur on another connection only and affect other tasks. Julo
Quick scenario: A connection receives a logout message with recovery (ReasonCode = 2). The Logout response sets a Time2Wait & Time2Retain as negotiated at login. Within these periods, a new Logout (implicit or explicit) request comes in either to remove that exact connection or to destroy the whole session. Should the target obey the new request or honor the previous?
Home Last updated: Thu Mar 28 04:18:16 2002 9362 messages in chronological order |