ISCSI Connections Get Lost Frequently

[akwete]

iSCSI connections from my two windows server 2008 R2 initiators to iSCSI targets on my ReadyNAS 3200 get lost frequently. I've got both servers connected to each target (two LUNs total.)

[TeknoJnky]

I didn't think that readynas iscsi supports multiple connections to the same target at the same time, at least yet.

[chirpa]

More details..

What firmware on the NAS?
Using Teaming/Bonding, or separate NICs?
Are the two machines connecting to the same targets, or different ones on the same NAS?

[akwete]

I didn't think that readynas iscsi supports multiple connections to the same target at the same time, at least yet.

If that's true then I just purchased an overpriced file-based network server:(

[akwete]

More details..

What firmware on the NAS?
Using Teaming/Bonding, or separate NICs?
Are the two machines connecting to the same targets, or different ones on the same NAS?

Firmware version 4.2.9. No Teaming/Bonding. Both Machines are connecting to the same targets on the same NAS.

[mdgm]

If that's true then I just purchased an overpriced file-based network server:(

What? You mount the iSCSI target on a server and share the files from there with the rest of your network?

If multiple connections to the one target is possible with iSCSI perhaps it'll be added as a feature in a future firmware release?

[akwete]

If that's true then I just purchased an overpriced file-based network server:(

What? You mount the iSCSI target on a server and share the files from there with the rest of your network?

If multiple connections to the one target is possible with iSCSI perhaps it'll be added as a feature in a future firmware release?

I need multiple connections per iSCSI target to setup a Hyper-V failover cluster. Strangely enough my setup passes the cluster validation wizard. However it fails when setting up the VMs for high availability (errors about missing volumes.)

[mdgm]

Not sure if this is helpful, but I found this in another thread:

iSCSI MPIO/MCS/Teaming Network Configuration

Our next firmware release (4.2.10) will have support both MCS and MPIO. But note that having support for it, and being Logo'd by Microsoft for official support issues is two separate items.

[aqkevin]

I need multiple connections per iSCSI target to setup a Hyper-V failover cluster. Strangely enough my setup passes the cluster validation wizard. However it fails when setting up the VMs for high availability (errors about missing volumes.)

I've just set up Hyper-V failover clustering successfully with the Readynas 3200. Each node must connect to the iscsi target (which you've done). After validation passes, you need to convert the iscsi storage into a Cluster Shared Volume (CSV) in the failover management tool. In order for CSV to work on the 3200, you need to enable "Access Control" for the iscsi target and list every node in the failover cluster in the access list.

I have done all this and actually "live migrated" VMs successfully.

Good luck.

Kevin

[rvanider]

I have had similar experiences with dropped iSCSI connections as well on the Pro as well. Everything is passing the cluster tests (4.2.9 & 4.2.10T51) and the live migrations are working well. The T51 beta seems to be significantly more stable but not quite there yet. For the purposes of testing I have setup up three hosts (2008 R2) with seven LUN all on CSV. I will generally see one or more of the hosts losing a connection to different targets. If I manually reconnect them it appears to be ok. Booting the NAS seems give it a better workout and make the problem more evident.

I am starting to wonder if it is a memory constraint. There are a ton of iscsi_trx/iscsi_ttx processes running.

[akwete]

My failover cluster with CSV via iSCSI is somewhat stable now, except for iSCSI connections not being restored occassionally when the NAS is rebooted.

[rvanider]

I have been getting quite a few dropped connections (the initiator stuck on reconnecting...). It has been quite a battle but I am just testing out some tweaks on the cluster hosts now that look promising. If this round of testing goes well I will be giving the cold boot (nas included) a whirl this weekend.

[mdgm]

Please give RAIDiator x86 4.2.11 Beta a try:

RAIDiator 4.2.11 is a minor update to the RAIDiator 4.0 series for the ReadyNAS NVX, Pro, 2100, and 3200. For those who have been following the 4.2.10 beta release, the decision was made to release that firmware version internally for our upcoming 3100 and 4200 products, but proceed with 4.2.11 as a unified firmware for all x86 ReadyNAS.