No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


S5600T's host windows initiator was inactive

Publication Date:  2013-06-17 Views:  247 Downloads:  0

Issue Description

ISCSI initiator of host turned to be inactive, thus the host can’t visit the storage LUN.

Alarm Information

[2013-06-03 18:58:42][1626420472][1500000290617][WARN][FrontDo_70_1 No reply for 1 NopIns, delta=754][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:45][1626421227][1500000290617][WARN][FrontDo_70_1 No reply for 2 NopIns, delta=755][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:48][1626421977][1500000290617][WARN][FrontDo_70_1 No reply for 3 NopIns, delta=750][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:51][1626422728][15000002901b5][ERR][FrontDo_70_1 HIT 4 OUTSTANDING_NOPINS.][ISCSI][need_a_nop,3804]
[2013-06-03 18:58:51][Thread:Iscsi_Control, Chap_UpdateInitiatorLinkUp:114]:Chap_UpdateInitiatorLinkUp Update initiator LINK_DOWN

Handling Process

Restart host for recovery. 

Root Cause

Because of the other hosts and storage were using the same port, and the connections between storage and all the others hosts were OK, so this problem was caused by the abnormal condition of host, thus can’t ping through, usually, if the ISCSI link status of host was unstable or abnormal, then the initiator will turn to be inactive.

While the initiator of host was inactive, host will not try to reconnect, even though logon manually, still can’t connect. We’ve confirmed it’s the Microsoft issue after contacting with them. But there’s no official KB for more details from Microsoft.