ISCSI initiator of host turned to be inactive, thus the host can’t visit the storage LUN.
[2013-06-03 18:58:42][WARN][FrontDo_70_1 No reply for 1 NopIns, delta=754][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:45][WARN][FrontDo_70_1 No reply for 2 NopIns, delta=755][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:48][WARN][FrontDo_70_1 No reply for 3 NopIns, delta=750][ISCSI][need_a_nop,3813]
[2013-06-03 18:58:51][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 iqn.1991-05.com.microsoft:gpgded-ant01.gpfinance.gpg.gov.za LINK_DOWN
Restart host for recovery.
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.