public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Santhapur Naveen <naveens@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: ISCSI says "Session Doesn't Exist"
Date: Fri, 24 Feb 2017 13:58:42 +0000	[thread overview]
Message-ID: <625A2455CC232F40B0F38F05ACED6D978C4E1F3B@VENUS1.in.megatrends.com> (raw)

Hello all,

    I've a question about IScsi and any suggestions would be helpful

[Issue Summary]
If I add an ISCSI attempt and on the next reboot, a connection will be established in between the initiator and the target. Till now, it is fine. Now if I do an immediate reset with in 20 seconds, on the next boot, the initiator is trying to establish a session, but the target rejects saying "Session does not exist". If I reset after 20 seconds or so, the connection would have been established with the same login details.

To dive deeper, I've checked the RFC documentation on this and found the following information. But when I checked the wireshark capture, I found my TSIH is ZERO even for the immediate session. If I want to make my immediate session also into a successful one, what should I be doing? I'm aware that there's a function available IScsiSessionAbort(). Would it help me or provide your suggestions to get me going.


   +------------------------------------------------------------------+

   |ISID      | TSIH        | CID    |     Target action              |

   +------------------------------------------------------------------+

   |new       | non-zero    | any    |     fail the login             |

   |          |             |        |     ("session does not exist") |

   +------------------------------------------------------------------+

   |new       | zero        | any    |     instantiate a new session  |

   +------------------------------------------------------------------+

   |existing  | zero        | any    |     do session reinstatement   |

   |          |             |        |     (see section 5.3.5)        |

   +------------------------------------------------------------------+

   |existing  | non-zero    | new    |     add a new connection to    |

   |          | existing    |        |     the session                |

   +------------------------------------------------------------------+

   |existing  | non-zero    |existing|     do connection reinstatement|

   |          | existing    |        |    (see section 5.3.4)         |

   +------------------------------------------------------------------+

   |existing  | non-zero    | any    |         fail the login         |

   |          | new         |        |     ("session does not exist") |

   +------------------------------------------------------------------+


Thanks,
Naveen


             reply	other threads:[~2017-02-24 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 13:58 Santhapur Naveen [this message]
2017-02-27  7:53 ` ISCSI says "Session Doesn't Exist" Ye, Ting
2017-02-27 20:03   ` Santhapur Naveen
2017-02-28  8:52     ` Ye, Ting
2017-03-14  1:54       ` Zhang, Lubo
2017-03-14  5:00         ` Santhapur Naveen
2017-03-14  5:06           ` Zhang, Lubo
2017-03-01  6:35     ` Zhang, Lubo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=625A2455CC232F40B0F38F05ACED6D978C4E1F3B@VENUS1.in.megatrends.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox