Server 2008 R2 iSCSI Hang

We are trying to connect Windows Server 2008 R2 to a DSS V6 Lite volume using the built-in Microsoft iSCSI initiator. We can get the Windows iSCSI to discover the target and connect, but the blank disk will either not show up, or show up but will freeze the MMC console when trying to initialize the disk. Also, trying to disconnect the iSCSI target will cause the iSCSI manager to freeze and sometimes even cause Windows to completely get frozen.

As a test, we connected another iSCSI target with a different storage appliance (Nexenta) and have a currently working EqualLogic target on the host. Are there any settings that need to be adjusted on the DSS console that don't work with the defaults? Thanks in advance.

The iSCSI Target does not cause this effect. Does this happen with all MS initiators? Also try to delete the iSCSI Volume and re-create it again using Block IO.

We haven't noticed it happening with other initiators. We have also tried re-creating the volume and have been using Block I/O. If the information is helpful, our DSS server has two NICs in the same subnet. We did see the instructions for static routing, but assumed that doesn't need to be configured for our setup. We plan on using MPIO with this configuration.

Where could we look for logging information for iSCSI in DSS? If this doesn't sound like a problem with DSS, we'll concentrate on troubleshooting Windows.

Quote:

---

Originally Posted by Mike C

We haven't noticed it happening with other initiators. We have also tried re-creating the volume and have been using Block I/O. If the information is helpful, our DSS server has two NICs in the same subnet. We did see the instructions for static routing, but assumed that doesn't need to be configured for our setup. We plan on using MPIO with this configuration.

Where could we look for logging information for iSCSI in DSS? If this doesn't sound like a problem with DSS, we'll concentrate on troubleshooting Windows.

---

This sounds more like the settings onthe windows side isnt working with DSS.
Has anything been changed? what about frame sizes?
It is also advisable for only one MS initiator to connect to a target. Multiples can cause problems.

Quote:

---

Originally Posted by Gr-R

This sounds more like the settings onthe windows side isnt working with DSS.
Has anything been changed? what about frame sizes?
It is also advisable for only one MS initiator to connect to a target. Multiples can cause problems.

---

We have changed the frame sizes to jumbo frames (9000). We have configured all of our switches and NICs on Windows for jumbo frames, as we have the same Windows servers connected to a Dell EqualLogic SAN. We are trying to use the DSS server for our Hyper-V cluster. Will multiple MS initiators cause problems? We have a small lab setup with VMware vSphere (2 clustered ESX hosts) and DSS that works fine.

Quote:

---

Originally Posted by Mike C

We have changed the frame sizes to jumbo frames (9000). We have configured all of our switches and NICs on Windows for jumbo frames, as we have the same Windows servers connected to a Dell EqualLogic SAN. We are trying to use the DSS server for our Hyper-V cluster. Will multiple MS initiators cause problems? We have a small lab setup with VMware vSphere (2 clustered ESX hosts) and DSS that works fine.

---

Make sure to also set jumbo frames on DSS (CNTRL+ALT+W at the console)
Multiple initiators to multiple targets is not a problem. Its when you try to connect multiple initaitors to the same target, the MS will complain.

Try to see this KB:
http://kb.open-e.com/Jumbo-Frames_121.html

We changed the frame size jumbo frames (9000). We set all the switches and network cards in Windows jumbo frames, because we have the same Windows-based servers connected to the SAN Dell EqualLogic. We are trying to use the DSS server to our Hyper-V cluster. Will initiate a number of factors cause MS? We are a small lab setup with VMware vSphere (2 ESX hosts in the cluster) and the DSS that works well.