| Author |
Message |
YQ
Guest
|
 Posted:
Thu Jun 23, 2005 12:18 am Post subject:
MS iscsi initiator 2.0 LUN RESET issue |
|
|
Hi,
It's nice that MS software iscsi initiator v2.0 is finally out. More
features have been introduced, and some functions are done differently,
e.g., LUN RESET.
In v1.x, initiator will disconnect and reconnect after each LUN RESET. Now
v2.0 seems no longer do that, just does LUN RESET itself. However, seems
sometimes the initiator isn't able to recover from the LUN RESET condition -
the traffic will halt after serveral consecutive LUN RESETs. I watched the
traffic between initiator and target, seems target behaves correctly by
responding "Function Complete". I'm wondering what the initiator is
expecting besides target's "Function Complete" response.
BTW, sometimes it works fine.
Thanks,
Yiqiang |
|
| Back to top |
|
 |
Alan Warwick [MSFT]
Guest
|
| Posted:
Fri Jun 24, 2005 12:18 am Post subject:
Re: MS iscsi initiator 2.0 LUN RESET issue |
|
|
You are correct that LUN RESET handling has changed between 1.0 and 2.0.
Initiator expects a response to the LUN RESET and that the target will
actually perform the LUN RESET.
--
--------------------------------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
"YQ" <ding_yiqiang@yahoo.com> wrote in message
news:elv7673dFHA.1612@tk2msftngp13.phx.gbl...
| Quote: | Hi,
It's nice that MS software iscsi initiator v2.0 is finally out. More
features have been introduced, and some functions are done differently,
e.g., LUN RESET.
In v1.x, initiator will disconnect and reconnect after each LUN RESET. Now
v2.0 seems no longer do that, just does LUN RESET itself. However, seems
sometimes the initiator isn't able to recover from the LUN RESET
condition - the traffic will halt after serveral consecutive LUN RESETs. I
watched the traffic between initiator and target, seems target behaves
correctly by responding "Function Complete". I'm wondering what the
initiator is expecting besides target's "Function Complete" response.
BTW, sometimes it works fine.
Thanks,
Yiqiang
|
|
|
| Back to top |
|
|
YQ
Guest
|
| Posted:
Sat Jun 25, 2005 12:16 am Post subject:
Re: MS iscsi initiator 2.0 LUN RESET issue |
|
|
Alan,
Thanks for your reply. As far as I know from the sniffer, the target
responses every LUN RESET, but initiator won't continue the traffic after
several LUN RESETs.
By the way, initiator doesn't know if target actually perform the LUN RESET
or not. The only thing initiator cares is target's response and no further
response for those aborted commands.
YQ
"Alan Warwick [MSFT]" <alanwar@online.microsoft.com> wrote in message
news:%23$$za7DeFHA.2520@TK2MSFTNGP09.phx.gbl...
| Quote: | You are correct that LUN RESET handling has changed between 1.0 and 2.0.
Initiator expects a response to the LUN RESET and that the target will
actually perform the LUN RESET.
--
--------------------------------------------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights.
"YQ" <ding_yiqiang@yahoo.com> wrote in message
news:elv7673dFHA.1612@tk2msftngp13.phx.gbl...
Hi,
It's nice that MS software iscsi initiator v2.0 is finally out. More
features have been introduced, and some functions are done differently,
e.g., LUN RESET.
In v1.x, initiator will disconnect and reconnect after each LUN RESET.
Now v2.0 seems no longer do that, just does LUN RESET itself. However,
seems sometimes the initiator isn't able to recover from the LUN RESET
condition - the traffic will halt after serveral consecutive LUN RESETs.
I watched the traffic between initiator and target, seems target behaves
correctly by responding "Function Complete". I'm wondering what the
initiator is expecting besides target's "Function Complete" response.
BTW, sometimes it works fine.
Thanks,
Yiqiang
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in