iscsiprt error event id 20

[Aaron_Denton]

We're seeing this about once per day on one of our clustered Windows Server 2008 R2 Hyper-V servers.

Is there something I can look for in Starwind configuration or logs that might help give me some clues?

[anton (staff)]

This is "connection to the target was lost". Now we need to take a look at StarWind own log to see corresponding message from there. Could you please provide one? Zip and send full log with your remarks to support@starwindsoftware.com (assuming there are errors reported in Windows log @ that time). Then we could say for sure as there are tons of reasons why it can happen. Thank you!

[Aaron_Denton]

Got a really quick response from the log I emailed to support.

We're going to get new network cards instead of using onboard Broadcom.

Here's the info I received from Joe about iSCSIprt error event id 20.


Hi Aaron,

This is a fairly generic error, and it is either related to your NIC or the MS iSCSI Initiator, and it is not generated by StarWind. Typically, this can be due to an outdated driver or something of that nature. However, if you were having issues your event logs would be flooded with iSCSI errors (multiple per second). So, I wouldn’t worry about this at all if you’re only receiving 1 per day. If the server is heavily loaded, then this certainly can be due to a time-out, but again, if you’re not having any issues I wouldn’t worry about it. Another thing to look at would be if you have dedicated NICs for iSCSI storage. You should dedicated NICs and switches (or at least VLANs) for iSCSI communication, and you should not be integrating your LAN and iSCSI traffic. That could certainly cause these types of issues.

Regards,

Joe

[anton (staff)]

Honestly any component broken between target and initiator can produce a delay and thus connection lost issue. Let's shoot possible points of failure one-by-one.