This post is more than 5 years old
5 Posts
0
18794
May 28th, 2019 05:00
iSCSI connection failures after KB4499177
Heads up on KB4499177
We encountered an odd issue on some of our Win Server 2016 nodes, that connect to a PS4210 array, started this morning at about 3am.
Trying to connect to some volumes (but not necessarily /all/) on the array was reporting a "Target error", and found elsewhere reports about it being an authentication failure... Takes a while to try until it hits a timeout threshold.
Firmware is up to date on the array, and drivers/firmware on the hosts are also up to date.
Plentiful host reboots, nothing resolved it until...
Now uninstalled KB4499177 (2019-05 Cumulative Update) - rebooted - and wham, instant connectivity again. Have repeated the incident on a 2nd node in the Failover Cluster - same issue, same resolution.
So, possibly Dell related, but most presumedly MS led issue on this one.
Couldn't see anything relevant to this as a known issue in the KB.
Other error messages reported from Windows Event Viewer:
Cluster Shared Volume 'XYZ' ('XYZ') is no longer accessible from this cluster node because of error '(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
Event 1: Unexpected failure. Error code: 48F@01000003
Event 43: Target failed to respond in time for a login request.
and from Group Manager:
iSCSI session to target 'XYZ from initiator 'XYZ' was closed. iSCSI initator connection failure. No response on connection for 6 seconds.
iSCSI login to target 'XYZ' from initiator 'XYZ' failed for the following reason:
Requested target not found.
0 events found
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
June 25th, 2019 21:00
Hello,
Excellent!! Please let us know how that goes.
From what I understand the problem to be it's during the connection phase on a required iSCSI feature that's not handled properly that used to be. A feature Dell PS Series requires.
Thanks for the update.
Regards,
Don
Shamshoom
3 Posts
0
June 25th, 2019 21:00
Hi Guys,
We spoke to Microsoft and it appears that they will be releasing a fix in July. We are about to be Guinea Pigs for the solution hopefully tomorrow. Will update as soon as possible...
Thanks.
Shamshoom
3 Posts
0
June 27th, 2019 19:00
Not as good as I hoped, but, MS just release a fix:
https://support.microsoft.com/en-us/help/4509475/windows-10-update-kb4509475
I am testing as we speak.
Thanks.
ChadCorkrum
1 Rookie
•
24 Posts
0
June 27th, 2019 20:00
It looks to have resolved the issue, I've installed it on the secondary nodes of a file and sql cluster and everything connected fine.
Not available on WSUS yet so those looking to only download it once will have to wait a bit.
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
June 27th, 2019 21:00
Hello,
Thank you for the update!
Very much appreciated!
Regards,
Don
fzb
1 Rookie
•
21 Posts
0
July 3rd, 2019 03:00
While not a supported scenario (no supported HIT for Win2019, running 5.1), the patch (in W2019 its KB4509479) didn't solve the issue completely for us. While the machine manages to connect the target again after some time with the patch applied, when it is used we regulary see iScsiPrt Event 49 (Target failed to respond in time to a Task Management request), 20 (Connection to the target was lost. The initiator will attemp to retry the connection), 39 (Initiator sent a task management command to reset the target.), 48 (Target failed to respond in time to a NOP request.) followed by the information that the target lost the connection but successfully reconnected.
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
July 3rd, 2019 11:00
Hello,
That issue is not likely related to the fix these patches provide. Since the problem is a failure to ever connect.
Your servers are connecting but timing out. Sometimes this indicates a network side problem.
I would suggest you open a support case so they can review the SAN diagnostics.
I would also not use HIT/ME with 2019.
Regards,
Don
komputerguy
7 Posts
0
July 6th, 2019 16:00
Thank you! What a horrible week I had with our exchange server bouncing databases!!! Removed the update and everything looks good!
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
July 7th, 2019 09:00
Hello,
That's great! Glad this forum helped. MS has released updated patches to resolve this issue and provide the original fixes too.
Regards,
Don
komputerguy
7 Posts
0
July 7th, 2019 19:00
Can you post the official patch release?
dwilliam62
6 Operator
•
1.5K Posts
•
6.4K Points
0
July 7th, 2019 20:00
Hello,
Sure.
Microsoft has released updated KB patches for both WIndows 2016 and Windows 2019
Windows Server 2016: https://support.microsoft.com/en-us/help/4509475
Windows Server 2019: https://support.microsoft.com/en-us/help/4509479
Regards,
Don