Dropping iSCSI Connections
Posted: Tue Oct 19, 2010 11:37 am
We are using Starwind as a iSCSI solution. We have multiple servers accessing this server through iSCSI targets. All our servers are running MS Server 2008 R2 and we have several Hyper-V virtual servers running on the host that have the actual VHD stored on the Starwind server. Our iSCSI connections drop almost once per day and it seems to be from the Starwind side as this affects all the servers accessing a iSCSI target. Most of the time it requires a Starwind service restart. We are now to a point of fighting with server/data corruption on an almost daily occurence.
We do have a dedicated 4 port Intel NIC that is setup as a teamed NIC. I have read that MS does not recommend this when doing clusters, but we currently have no servers in a cluster. Is it okay to use Starwind with teamed NIC's?
Does anyone have any ideas on this?
Thanks,
Chris
We do have a dedicated 4 port Intel NIC that is setup as a teamed NIC. I have read that MS does not recommend this when doing clusters, but we currently have no servers in a cluster. Is it okay to use Starwind with teamed NIC's?
Does anyone have any ideas on this?
Thanks,
Chris