iSCSI Initiator Dropping

We have an new HP server with 6 GB of memory and quad core 64-bit processor running Microsoft Hyper-V on windows 2008.  We have one Guest OS, which is a Windows 2008 OS running the file server role of server core.  In the Guest OS we are running Backup Exec12 agent to backup our data.  The data is connected to a HP MSA 2012i SAN via iSCSI.  The connection to the SAN is via two nics that are teamed and on a separate VLAN dedicated to the SAN.  All switching is gigabit.  

The backup server happens to be the host Hyper-V server.  The host and the guest each have a dedicated nic that is connected to a server vlan.  The host server is running Backup Exec and backs up the guest via the agent.  

When the backup runs, we are seeing relatively slow speed and after a period of time the iSCSI Initiator reports that it has lost connection to the disk.  A moment later it returns.  This behavior seems to repeat itself throughout the backup and often the backup will just fail.

We are hoping someone might be able to clue us into why the iSCSI initiator might be dropping out.  We are not seeing any errors on the HP MSA SAN nor on the switching devices.  It seems to be a problem within the Hyper-V guest OS.  

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Can you confirm on the OS side that you have a gigabit connection to the SAN?
 I've seen this sort of error occur on a server using a low-grade NIC that was starting to fail and could not maintain gigabit connectivity. It was replaced with a higher-grade server adapter and the problem disappeared.
jjeldridgeAuthor Commented:
The server and NIC's are brand new (1 month).  All are gigabit.  2 NIC's are built-in HP nics and 2 are an external Intel Card.  The Intel NIC are teamed and go to the SAN.  The NIC's are presented as 10GB adapters in the GUEST and are running at 1 GB full duplex on the Host.

The iSCSI initiator dropping only seems to happen during a backup operation.  We are using Backup exec 12.5 with a remote agent software on the Guest OS.  It also seems like the the iSCSI might be dropping when the backup is struggling to grab a file (not sure on this one but we are trying to confirm).  

jjeldridgeAuthor Commented:
The issue has something to do with the NIC team.  We removed the NIC Team on the nic's running to the iSCSI SAN and we no longer see the issue.  The issue only seemed to arise after prolonged data transfer.  So a 1GB file transfered fine but trying to backup several hundred GB of data caused the drops.  

We are still reviewing this for a more permanent resolution

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I have the same problem with win2008server and hp 2012i. I'll try to unteam the NICs later today.

When copying data from the iscsi to another network device we get errors like:

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:


the message resource is present but the message is not found in the string/message table


Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.


Connection to the target was lost. The initiator will attempt to retry the connection.
So has the perminent solution ever been found in terms of several hundered GB transfered and this occurs?
initiator could not find a match for the initiator task tag in the received PDU.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.