Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 25, 2016 9:00 PM
I have two servers(Windows Server 2012 R2) in a fail over cluster that hosts file servers and VMs. They are connected to a Synology RS815RP for iSCSI storage. I have 6 Targets that I connect to in Microsoft iSCSI initiator. Whenever I reboot any of the servers not all of the targets reconnect. I went through all the targets and made sure to check: ADD TO Favorites list
Contacted Synology support and there recommendation is to increase the timeout value because its a issue with windows.
All replies (9)
Wednesday, August 31, 2016 3:54 PM âś…Answered
Hi Blugs,
Check event viewer to see if there are any related events. iSCSI related events are under the following path: Windows log\Application.
I have seen some similar issues solved by updating DSM version.
How about the network connection between nodes and storage, is it stable?
>>Whenever I reboot any of the servers not all of the targets reconnect.
Are there any differences between different targets?
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi again Leo,
I decided to re investigate the network connections to iSCSI storage. When I was setting up the test configuration of the Synology NAS and the two servers, I used NIC teaming. I removed the two NICs from the team and used only one NIC to connect to the Synology NAS. The server rebooted and I got all the connections working automatically. I found this article and apparently it is not supported https://technet.microsoft.com/en-us/magazine/ff679916.aspx
Friday, August 26, 2016 5:12 AM
Hi Blugs,
Check event viewer to see if there are any related events. iSCSI related events are under the following path: Windows log\Application.
I have seen some similar issues solved by updating DSM version.
How about the network connection between nodes and storage, is it stable?
>>Whenever I reboot any of the servers not all of the targets reconnect.
Are there any differences between different targets?
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Friday, August 26, 2016 1:08 PM
The network connection is good between the Synology and both servers.The last time it happened it was the Cluster Shared Volume but I don't think its consistently that target. I will do it this weekend and follow up to see if its a specific target. Under the Application logs I don't see any for iscsi but I have a lot of errors for Perflib ID: 1008 & usbperf ID: 2001
Monday, August 29, 2016 9:18 AM
Hi Blugs,
>>I will do it this weekend and follow up to see if its a specific target
Any updates on it?
It seems the two events are not related to the cause of the issue.
Have you tried to increase the timeout value?
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Monday, August 29, 2016 3:00 PM
Hi Blugs,
if you finish with all your iSCSI, MPIO and CSV settings, go to "Volume and Device" Tab on iSCSI Initiator again, and press "Auto Configure". ;-)
Best Regards,
Boris
Wednesday, August 31, 2016 1:28 PM
Hi Blugs,
if you finish with all your iSCSI, MPIO and CSV settings, go to "Volume and Device" Tab on iSCSI Initiator again, and press "Auto Configure". ;-)
Best Regards,
Boris
If I select Auto Configure from here will it use any IP address to connect. Reason is because when I connected each target I went to advanced then select Microsoft iscsi initiator and the adapter I want it to use and the ip it should connect to
Wednesday, August 31, 2016 1:30 PM
Hi Blugs,
>>I will do it this weekend and follow up to see if its a specific target
Any updates on it?
It seems the two events are not related to the cause of the issue.
Have you tried to increase the timeout value?
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Where do I go to increase the timeout value?
Wednesday, August 31, 2016 2:10 PM
Hi Blugs,
>>I will do it this weekend and follow up to see if its a specific target
Any updates on it?
It seems the two events are not related to the cause of the issue.
Have you tried to increase the timeout value?
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
It happened to all targets. They are stuck at reconnecting... In the event logs under Windows\System\ there is a bunch of iScsiPrt Event ID 5.
Thursday, September 1, 2016 7:42 AM
Hi Blugs,
Thanks for sharing the information.
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].