iSCSI error.

[Marco]

Hi,
I have a cluster with 3 nodes Windows 2008 Enterprise Core Version and
the SAN is HP MSA 2012i. When I backup the VM using DPM in each node
receiving the following errors:

Event ID: 39
Source: iScsiPrt
General:
Initiator sent a task management command to reset the target. The target
name is given in the dump data.

- and -

Eventi ID: 9
Source: iScsiPrt
General:
Target did not respond in time for a SCSI request. The CDB is given in the
dump data.

Also I get the following warning:

Event ID: 139
Source: iScsiPrt
General:
The description for Event ID 129 from source iScsiPrt cannot be found.
Either the component that raises this event is not installed on your local
computer or the installation is corrupted. You can install or repair the
component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
\Device\RaidPort1
the message resource is present but the message is not found in the
string/message table

I tried adding the registry key "TimeOutValue" in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk and I set it to
60, but the problem is the same.
Regards.

[Jonesy]

How are the iSCSI targets zoned? Does more than one host share the same
target?

Post by Marco
Hi,
I have a cluster with 3 nodes Windows 2008 Enterprise Core Version and
the SAN is HP MSA 2012i. When I backup the VM using DPM in each node
Event ID: 39
Source: iScsiPrt
Initiator sent a task management command to reset the target. The target
name is given in the dump data.
- and -
Eventi ID: 9
Source: iScsiPrt
Target did not respond in time for a SCSI request. The CDB is given in the
dump data.
Event ID: 139
Source: iScsiPrt
The description for Event ID 129 from source iScsiPrt cannot be found.
Either the component that raises this event is not installed on your local
computer or the installation is corrupted. You can install or repair the
component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
\Device\RaidPort1
the message resource is present but the message is not found in the
string/message table
I tried adding the registry key "TimeOutValue" in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk and I set it to
60, but the problem is the same.
Regards.

[Marco]

Hi,
I have enabled MPIO on iSCSI connections and each node of the cluster is
connected to the iSCSI SAN using two network cards.

Post by Jonesy
How are the iSCSI targets zoned? Does more than one host share the same
target?

Post by Marco
Hi,
I have a cluster with 3 nodes Windows 2008 Enterprise Core Version and
the SAN is HP MSA 2012i. When I backup the VM using DPM in each node
Event ID: 39
Source: iScsiPrt
Initiator sent a task management command to reset the target. The target
name is given in the dump data.
- and -
Eventi ID: 9
Source: iScsiPrt
Target did not respond in time for a SCSI request. The CDB is given in the
dump data.
Event ID: 139
Source: iScsiPrt
The description for Event ID 129 from source iScsiPrt cannot be found.
Either the component that raises this event is not installed on your local
computer or the installation is corrupted. You can install or repair the
component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
\Device\RaidPort1
the message resource is present but the message is not found in the
string/message table
I tried adding the registry key "TimeOutValue" in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk and I set it to
60, but the problem is the same.
Regards.

[JGGiant]

I too am having this same issue on nearly all my Windows 2008 machines
connected to an iSCSI storage. More so on machines with higher I/O. I am
running Windows 2008 standard 64 bit on these machines.

MPIO is not in use in this portion of my environment. 1 1GB NIC is
dedicated to the iSCSI storage on each machine. On the Equallogic side,
traffic is being loadbalanced across 2-4 NICs. This seems like a server side
issue as I cannot correlate this issue on all servers at the same time.

I manage an Exchange environment, OCS, as well as a few machines running SQL
(connected to Equallogic iSCSI storage). All being backed up by DPM. I was
able to resolve this issue on the machines with lower I/O working with
Equallogic support. Basically we went through every portion of the
configuration from the network side, server side, etc. Updating the NIC
driver and configuring it as an iSCSI device resolved the issue on our
Exchange HUB/CAS servers (machines processing much lower I/O). I implemented
this fix on our mailbox (high I/O) servers, and although I now see the errors
less frequently, I do still see them often enough to be an issue.