Subscribe

iSCSI on Windows Server 2016

I have three node  HyperV Windows Server 2016 Cluster that are usng iSCSI to a FAS 8040. I have the initiator group setup and the iSCSI initiator in Windows is configured to see the two luns. One lun is for the quroum and the other lun is for data. During a reboot, the storage appears to be connected but in reality it is not which results in the clsuter crashing. The only way to get the cluster to come back online is to have the luns owned by host 1. I have looked that logs on both sides but not seeing any errors. Is there another log file i should be looking at or a setting that needs to be applied.

 

Thanks,

 

Janet

Re: iSCSI on Windows Server 2016

Which Data ONTAP version is in use?

When you say "during reboot" did you mean reboot of the windows host or the storage controller?

Does your igroup have entries for all three windows initiators or only one?

How did you figure out that "the storage appears to be connected but in reality it is not" ? Any command outputs ?

Please post more info which you think is relevant and would be helpful in troubleshooting.

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.