Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Careers | About Us | Contact Us|

 

Hyper-V VM turn off because it lost connection to iSCSI SAN
Event ID 1, 7, 20, 39, 49 and 129: iSCSIprt issues

Situation: The client created Exchange 2010 Failover Clustering based on this design: Exchange 2010 Design. The remote site VM were turn off with these Event IDs in the physical server.

Log Name: System
Source: iScsiPrt
Event ID: 1
Task Category: None
Level: Error
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.

Log Name: System
Source: iScsiPrt
Event ID: 7
Level: Error
Description:
The initiator could not send an iSCSI PDU. Error status is given in the dump data.

Log Name: System
Source: iScsiPrt
Event ID: 20
Level: Error
Description:
Connection to the target was lost. The initiator will attempt to retry the connection.

Log Name: System
Source: iScsiPrt
Event ID: 39
Level: Error
Description:
Initiator sent a task management command to reset the target. The target name is given in the dump data.

Log Name: System
Source: iScsiPrt
Event ID: 49
Level: Error
Description:
Target failed to respond in time to a Task Management request.

Log Name: System
Source: iScsiPrt
Event ID: 129
Task Category: None
Level: Warning
Description:
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\RaidPort7

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

Possible causes: 1. There is a network issue that the physical server can't access to the SAN.

2. The physical can't reach the iSCSI drive because the SAN is down.

3. There is the incorrect configuration on the NIC or switch so that the server can't access the iSCSI drive.

4. The iSCSI has a configuration issue.

 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

 

  This web is provided "AS IS" with no warranties.
Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.