none
The initiator could not send an iSCSI PDU. Error status is given in the dump data. after installing Cluster Service

    Question

  • I have a 3 node hyper-V cluster:

    HW = 3 HP DL380 G7 servers

             -8 NICs, dual 4 port (2 NICS teamed=LAN-01, 2 NICS teamed = DMZ-01, Nic 5 = mgmt, Nic 6 = Cluster communication, 2 NICS teamed = LAN-02)

             -4 onboard iscsi enhanced ports

    SW = Server Core R2 Ent.

            -Roles: Hyper-V

            - Features: Failover Clustering, Multipath IO, WOW64 Support

    2 of the Servers work awsome, no complaints. However the third "identical" server is giving me issues. I get it all setup and everything is working, iSCSI is good to go. When connecting to iscsicpl I can connect and disconnect at will. Once I install the FailoverCluster-Core The iSCSI goes not responding and throws the following errors:

     

    Log Name:   System
    Source:    iScsiPrt
    Date:     8/25/2011 4:50:10 PM
    Event ID:   49
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   Server-02.bdn.ca
    Description:
    Target failed to respond in time to a Task Management request.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
     <System>
      <Provider Name="iScsiPrt" />
      <EventID Qualifiers="49152">49</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" />
      <EventRecordID>3644</EventRecordID>
      <Channel>System</Channel>
      <Computer>Server-02.bdn.ca</Computer>
      <Security />
     </System>
     <EventData>
      <Data>\Device\RaidPort1</Data>
      <Binary>000001000100000000000000310000C000000000000000000000000000000000000000000000000007</Binary>
     </EventData>
    </Event>
    Log Name:   System
    Source:    iScsiPrt
    Date:     8/25/2011 4:50:10 PM
    Event ID:   7
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   Server-02.bdn.ca
    Description:
    The initiator could not send an iSCSI PDU. Error status is given in the dump data.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
     <System>
      <Provider Name="iScsiPrt" />
      <EventID Qualifiers="49152">7</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" />
      <EventRecordID>3643</EventRecordID>
      <Channel>System</Channel>
      <Computer>Server-02.bdn.ca</Computer>
      <Security />
     </System>
     <EventData>
      <Data>\Device\RaidPort1</Data>
      <Binary>000080000100000000000000070000C00000000000000000000000000000000000000000000000000D0200C0690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary>
     </EventData>
    </Event>
    Log Name:   System
    Source:    iScsiPrt
    Date:     8/25/2011 4:50:10 PM
    Event ID:   20
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   Server-02.bdn.ca
    Description:
    Connection to the target was lost. The initiator will attempt to retry the connection.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
     <System>
      <Provider Name="iScsiPrt" />
      <EventID Qualifiers="49152">20</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" />
      <EventRecordID>3642</EventRecordID>
      <Channel>System</Channel>
      <Computer>Server-02.bdn.ca</Computer>
      <Security />
     </System>
     <EventData>
      <Data>\Device\RaidPort1</Data>
      <Binary>00007C000100000000000000140000C0000000000000000000000000000000000000000000000000690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary>
     </EventData>
    </Event>
    Log Name:   System
    Source:    iScsiPrt
    Date:     8/25/2011 4:50:10 PM
    Event ID:   39
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   Server-02.bdn.ca
    Description:
    Initiator sent a task management command to reset the target. The target name is given in the dump data.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
     <System>
      <Provider Name="iScsiPrt" />
      <EventID Qualifiers="49152">39</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-08-25T21:50:10.700497800Z" />
      <EventRecordID>3641</EventRecordID>
      <Channel>System</Channel>
      <Computer>Server-02.bdn.ca</Computer>
      <Security />
     </System>
     <EventData>
      <Data>\Device\RaidPort1</Data>
      <Binary>00007C000100000000000000270000C0000000000000000000000000000000000000000000000000690071006E002E0032003000300033002D00310030002E0063006F006D002E006C00650066007400680061006E0064006E006500740077006F0072006B0073003A0063006F0062002D006D0067006D0074002D00300031003A00370037003A006C006F006E0064006F006E0063006C007500730074002D0030003200</Binary>
     </EventData>
    </Event>

    Things I've tried:

    using only one port and cable (Testing all the physical connections)

    HP actually replaced the Motherboard thinking it might bad Hardware. (Like I said I have two other identical servers that work.)

    I've reloaded this unit about 5 times trying to install components in different orders.

    The second FailoverCluster-Core is uninstalled the iSCSI comes back to life!

    If I use the the non-onboard NICS it actaully works. Looking for any suggetions on this one.



     

     

    Thursday, August 25, 2011 10:02 PM

All replies

  • Have you reviwed this KB - 981482?
    Chuck Timon Senior, Support Escalation Engineer (SEE) Windows Beta Engineer Microsoft Corporation
    Friday, August 26, 2011 12:54 AM
    Moderator
  • I have read the the article. It just doesnt make sense that it only stops working once the cluster feature is installed? I have had this server online previously as well. I will try increasing the receiving buffer just to see.
    Friday, August 26, 2011 4:39 AM
  • Ok, I've tried everything in that document. with no success. We also pulled all the HW out of the server, just enough RAM to boot and only onboard NICs. I'm feeling like we've tried everything. Anyone got some suggestions?
    Tuesday, August 30, 2011 2:13 PM
  • I was able to resolve this error.  Not sure though if the cause is the same.  I opened up the "Microsoft iSCSI Initiator" and on the "Targets" tab the Status was not "Connected".  This gave me the clue to go check the Targets by using the StarWind. After uploading the key from http://www.starwindsoftware.com/starwind-free-license-key-generated everything start working normally 
    Friday, September 30, 2011 4:19 PM