Hey you iSCSI wizards,

We are just getting into iSCSI for winders and have the following scenario happen today:

We had a failover on a cluster member that host test/infrastructure systems today, due to a faulty ESH2 (that was triggered by a background FW update, but that is a different discussion).

This filer also has an iSCSI volume on a test window server.

During a failover, it reported errors, but the iSCSI reconnected. However, during a giveback (after NetApp replaced the faulty ESH2), the iSCSI connection gave errors and lost the connection altogether. We had to reboot that test windows box to recover the iSCSI volume.

We are working with NetApp to learn more about this. But just from browsing on the NOW site about iSCSI, there are recommendations about increasing the timeout values from the default 10 sec to at least 60 sec, and other registry tunings for iSCSI to make it more robust.

http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs16249 http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs17115

Anybody been there and done this or other tunings with success ?

TIA

-Rob