|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: iSCSI: Logout requestPaul, No, the "target requests logout" Async Message is not an error indication. On the contrary, the reason for its existence is to ensure that an iSCSI connection that the target wants to decommission (for ex., administrator wants to replace the iSCSI NIC servicing the connection) may be gracefully taken out with *no* SCSI errors. It is this quiescing intention that is reflected in the mandatory "close the connection" Logout that the Async Message demands - i.e. recovery Logout is not allowed on this Async Message. >The target may have good reasons to want a > particular connection or session to be closed but allowing a new login > to occur right after that. It is a legal possibility, but I think it's unlikely for the reasons described above. If the NIC is being replaced on the target end, an immediate new Login attempt will fail. Hope that helps. -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Organization Hewlett-Packard MS 5668 Roseville CA 95747 cbm@rose.hp.com ----- Original Message ----- From: "Paul Koning" <ni1d@arrl.net> To: <cbm@rose.hp.com> Cc: <ips@ece.cmu.edu> Sent: Tuesday, April 30, 2002 9:31 AM Subject: Re: Logout request > Excerpt of message (sent 29 April 2002) by Mallikarjun C.: > > Paul, > > > > Logout request can be originated only by an initiator. > > > > If that isn't your question, I am curious about the `disagreement' > > you're referring to. What is the other interpretation? > > Sorry, I wasn't precise enough in referring to messages. > > I was talking about how the initiator reacts to the "target requests > logout" async message. My interpretation of section 2.5.3.3 is that > this shouldn't be viewed as an error indication, only as a > housekeeping request. The target may have good reasons to want a > particular connection or session to be closed but allowing a new login > to occur right after that. > > paul > >
Home Last updated: Tue Apr 30 15:18:25 2002 9894 messages in chronological order |