Target Not Available

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
jduehmig
Posts: 5
Joined: Tue Feb 05, 2008 4:18 pm

Wed Jul 17, 2013 1:44 pm

I have the Starwind iSCSI target running and configured on a Windodws 2012 server (physical machine.) I have the Microsoft iSCSI initiator running on a separate Windows 2012 server (Hyper-V VM on a different physical server.) Last week I successfully connected to the target and ran a backup to the iSCSI target. When I returned this week the connection to the target has been lost and I can't get it back. Last week I did setup a connection between the two servers using a dedicated backup VLAN, but I can ping both servers using the VLAN network. I can also see the portal from the initiator but no targets are available. I've removed all CHAP information to make sure it is not an authentication issue but that hasn't changed anything. I'm getting the following errors on the initiator side:

Log Name: System
Source: MSiSCSI
Date: 7/17/2013 7:22:43 AM
Event ID: 113
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: DPMVM.internal.com
Description:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *172.24.18.2 0003260 ROOT\ISCSIPRT\0000_0 .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSiSCSI" />
<EventID Qualifiers="0">113</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-17T12:22:43.000000000Z" />
<EventRecordID>6709</EventRecordID>
<Channel>System</Channel>
<Computer>DPMVM.internal.com</Computer>
<Security />
</System>
<EventData>
<Data>0xefff0003</Data>
<Data>*172.24.18.2 0003260 ROOT\ISCSIPRT\0000_0 </Data>
</EventData>
</Event>

Log Name: System
Source: iScsiPrt
Date: 7/17/2013 7:22:43 AM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DPMVM.internal.com
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="iScsiPrt" />
<EventID Qualifiers="49152">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-17T12:22:43.934935900Z" />
<EventRecordID>6710</EventRecordID>
<Channel>System</Channel>
<Computer>DPMVM.internal.com</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort1</Data>
<Binary>000006000100000000000000010000C0000000000000000000000000000000000000000000000000BC0CAC181202</Binary>
</EventData>
</Event>


Log Name: System
Source: iScsiPrt
Date: 7/17/2013 7:22:43 AM
Event ID: 70
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DPMVM.internal.com
Description:
Error occurred when processing iSCSI logon request. The request was not retried. 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">70</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-17T12:22:43.934935900Z" />
<EventRecordID>6711</EventRecordID>
<Channel>System</Channel>
<Computer>DPMVM.internal.com</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort1</Data>
<Binary>000004000100000000000000460000C0000000000000000000000000000000000000000000000000360200C0</Binary>
</EventData>
</Event>


Any help would be appreciated.
Thanks,
Joe
jduehmig
Posts: 5
Joined: Tue Feb 05, 2008 4:18 pm

Thu Jul 18, 2013 2:52 pm

I was able to resolve this myself. I had installed the Microsoft iSCSI target components first as a test. I removed those components and the StarWind targets began working again.
Joe
User avatar
anton (staff)
Site Admin
Posts: 4021
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Thu Jul 18, 2013 7:18 pm

Love self-supporting customers!

BTW, it's possible to bind StarWind to the other port (non-3260) so it will co-exist with any iSCSI software using 3260 port by default.
jduehmig wrote:I was able to resolve this myself. I had installed the Microsoft iSCSI target components first as a test. I removed those components and the StarWind targets began working again.
Joe
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply