SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    iSCSI delay for session shutdown


    • To: ips@ece.cmu.edu
    • Subject: iSCSI delay for session shutdown
    • From: Pierre Labat <pierre_labat@hp.com>
    • Date: Mon, 16 Oct 2000 15:26:50 -0700
    • Content-Transfer-Encoding: 7bit
    • Content-Type: text/plain; charset=us-ascii
    • Organization: Hewlett Packard ATM-SISL
    • Sender: owner-ips@ece.cmu.edu

    Julian,
    
    Consider the following case:
    - an host  system has two NICs (NIC1 and NIC2)
    - the target has only one NIC.
    - the host (initiator) establishes one session through
        one of its NIC  (NIC1) to the target.
    
    After a while, NIC1 fails.
    The host, to recover, decides to use NIC2, it opens a new
    TCP connection (same session) through NIC2 to the target.
    
    My question are:
    
    1) how much time a target will keep a session "valid"
    from the time the TCP(s) connection(s) can't pass
    any traffic  (because
    on the other side (initiator)  it is broken)?
    
    It is no sure that it will be the time till TCP gives up depending
    on the target implementation.
    
    If this time is too short, when the initiator will open
    a new TCP connection to recover, the target would
    have dropped the session and the recovery will not work.
    
    2) Could it be possible to specify a minimum delay before
    the target drops the session?
    Only in the case where the target doesn't receive
    a logout notification of course.
    
    This minimum delays would secure the initiator recovery
    mechanism.
    
    Regards,
    
    Pierre
    
    
    
    
    


Home

Last updated: Tue Sep 04 01:06:37 2001
6315 messages in chronological order