Recconecting every minute to iSCSI target

[theark]

I'm just updated to 5.7 from 5.6 and am receiving 2 messages every minute in my logs:

iScsiPrt
Error Event ID 20
Connection to the target was lost. The initiator will attempt to retry the connection

iScsiPrt
Error Event ID 34
A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.

This happens every minute on the client machine.

The server is a Windows Server 2008 server (running natively) sharing an iSCSI image the client is a Windows SBS 2003 server (running on VMWare ESXi 4) using the Microsoft iSCSI Initiator.

Any ideas?

I've noticed a post with someone have the same issue on a HyperV machine.

[anton (staff)]

Do you run two node cross-linked configuration or do you run StarWind inside VMs?

[theark]

Do you run two node cross-linked configuration or do you run StarWind inside VMs?

Starwind runs on a native Windows 2008 server, the iSCSI client runs on SBS2003 on a virtual server

[anton (staff)]

Good. Anything changed except 5.6 -> 5.7 upgrade? Can you run Performance Monitor to see is there any spikes in network load?

Do you run two node cross-linked configuration or do you run StarWind inside VMs?

Starwind runs on a native Windows 2008 server, the iSCSI client runs on SBS2003 on a virtual server

[theark]

The only change seems to be that these messages are appearing. There seems to be a write spike every few minutes. There's barely any activity on it. Its just used to store Windows Server Update data so there's no activity until updates are released.

[gstephenson]

I'm just updated to 5.7 from 5.6 and am receiving 2 messages every minute in my logs:

iScsiPrt
Error Event ID 20
Connection to the target was lost. The initiator will attempt to retry the connection

iScsiPrt
Error Event ID 34
A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.

This happens every minute on the client machine.

The server is a Windows Server 2008 server (running natively) sharing an iSCSI image the client is a Windows SBS 2003 server (running on VMWare ESXi 4) using the Microsoft iSCSI Initiator.

Any ideas?

I've noticed a post with someone have the same issue on a HyperV machine.

Yes, the solution in my case was to change iscsiPingPeriod value to 20 in Starwind.cfg on the first server, restart Starwind, let sync finish, then do the same on the second Starwind server.

[theark]

Yes, the solution in my case was to change iscsiPingPeriod value to 20 in Starwind.cfg on the first server, restart Starwind, let sync finish, then do the same on the second Starwind server.

I am only running one StarWind server?

[gstephenson]

Yes, the solution in my case was to change iscsiPingPeriod value to 20 in Starwind.cfg on the first server, restart Starwind, let sync finish, then do the same on the second Starwind server.

I am only running one StarWind server?

I would try the same thing on your one server then, but I'm not really an expert. Also make sure you have the latest build. I am running 5.7.1727.

[Anatoly (staff)]

Agree.

We have just updated build on the site (5.7.1733). You can download it using this link.

[theark]

Just installed the latest build from today (I was already on 5.7.1733) and so far it seems to have stopped the issue!

[anton (staff)]

That was a plan. Thank you very much for keeping us updated.