码迷,mamicode.com
首页 > 其他好文 > 详细

iscsi target CLEANUP_WAIT

时间:2020-05-18 15:55:20      阅读:65      评论:0      收藏:0      [点我收藏+]

标签:either   cte   sso   orm   intern   diff   ubunt   命令   sage   

1 target端如何进入CLEANUP_WAIT状态的

- target: One or more of the following events caused this
         transition:

         a) Internal event that indicates that a transport connection
            timeout was received, thus prompting a transport reset
            or transport connection closure.

         b) An internal event of a failed connection/session
            reinstatement was received.

         c) A transport reset was received.

         d) A transport disconnect indication was received.

         e) An internal emergency cleanup event was received, which
            prompts an Async PDU with AsyncEvent "Drop connection" (for
            this CID), or event "Drop all connections".
- target: One or more of the following events caused this
         transition:

         a) An internal event that indicates a failure of the
            Logout processing was received, which prompts a
            Logout Response (failure, i.e., a non-zero status)
            to be sent.

2 当target端的session进入cleanup_wait状态时,是无法通过targetcli命令进行清理。下面的输出由targetcli sessions detail输出。

alias: ubuntu2105    sid: 5 type: Normal session-state: LOGGED_IN
    name: iqn.1993-08.org.debian:01:5cfb20ba85f0 (NOT AUTHENTICATED)
    mapped-lun: 0 backstore: fileio/lun1 mode: rw
    address: 10.0.2.27 (TCP)  cid: 0 connection-state: CLEANUP_WAIT

只有当initiator明确或者非明确地logout连接,target才会从CLEANUP_WAIT进入IN_CLEANUP或FREE状态。

"An initiator must initiate an explicit or implicit connection logout
   for a connection in the CLEANUP_WAIT state, if the initiator intends
   to continue using the associated iSCSI session."

M1: One or more of the following events was received:

       - initiator:

         * An internal event that indicates connection state timeout.

         * An internal event of receiving a successful Logout Response
           on a different connection for a "close the session" Logout.

       - target:

         * An internal event that indicates connection state timeout.

         * An internal event of sending a Logout Response (success) on a
           different connection for a "close the session" Logout
           Request.

   M2: An implicit/explicit logout process was initiated by the
       initiator.

       - In CSM-I usage:

         * initiator: An internal event requesting the connection (or
           session) reinstatement was received, thus prompting a
           connection (or session) reinstatement Login to be sent,
           transitioning CSM-I to state IN_LOGIN.

         * target: A connection/session reinstatement Login was received
           while in state XPT_UP.

       - In CSM-E usage:

         * initiator: An internal event was received that indicates that
           an explicit logout was sent for this CID in state LOGGED_IN.

         * target: An explicit logout was received for this CID in state
           LOGGED_IN.

   M3: Logout failure was detected.

       - In CSM-I usage:

         * initiator: CSM-I failed to reach LOGGED_IN and arrived into
           FREE instead.

         * target: CSM-I failed to reach LOGGED_IN and arrived into FREE
           instead.

       - In CSM-E usage:

         * initiator: either CSM-E moved out of LOGGED_IN, or Logout
           timed out and/or aborted, or Logout Response (failure) was
           received.

         * target: either CSM-E moved out of LOGGED_IN, Logout timed out
           and/or aborted, or an internal event that indicates that a
           failed Logout processing was received.  A Logout Response
           (failure) was sent in the last case.

   M4: Successful implicit/explicit logout was performed.

       - In CSM-I usage:

         * initiator: CSM-I reached state LOGGED_IN, or an internal
           event of receiving a Logout Response (success) on another
           connection for a "close the session" Logout Request was
           received.

         * target: CSM-I reached state LOGGED_IN, or an internal event
           of sending a Logout Response (success) on a different
           connection for a "close the session" Logout Request was
           received.

       - In CSM-E usage:

         * initiator: CSM-E stayed in LOGGED_IN and received a Logout
           Response (success), or an internal event of receiving a
           Logout Response (success) on another connection for a "close
           the session" Logout Request was received.

         * target: CSM-E stayed in LOGGED_IN and an internal event
           indicating a successful Logout processing was received, or an
           internal event of sending a Logout Response (success) on a
           different connection for a "close the session" Logout Request
           was received.
 

https://tools.ietf.org/html/rfc7143#section-8.2.1

 

iscsi target CLEANUP_WAIT

标签:either   cte   sso   orm   intern   diff   ubunt   命令   sage   

原文地址:https://www.cnblogs.com/longchang/p/12910836.html

(0)
(0)
   
举报
评论 一句话评论(0
登录后才能评论!
© 2014 mamicode.com 版权所有  联系我们:gaon5@hotmail.com
迷上了代码!