|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: iSCSI: Logout request> Not necessarily, and that's why I bring up the issue. Sorry, but I do not see an issue as far as the spec is concerned. You are describing what is obviously an implementation possibility - the spec neither suggests nor prohibits it, rightly so. I already agreed that what you describe is a legal possibility per spec - Initiator may login immediately, only the regular timeout considerations described in 6.3 apply. -- 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 11:51 AM Subject: Re: iSCSI: Logout request > Excerpt of message (sent 30 April 2002) by Mallikarjun C.: > > >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. > > Not necessarily, and that's why I bring up the issue. > > If the target has multiple NICs, and one of them has to be taken out > of service, it may be that it can move the address (but not the open > session and connection state) to another NIC. In that case, a "target > request logout" is the mechanism it would want to use to initiate that > operation, and if the initiator then follows up with a new login, > everything works smoothly. > > paul > >
Home Last updated: Tue Apr 30 17:18:25 2002 9903 messages in chronological order |