Can Hyper-V VM Connect to iSCSI Targets on Its Host?

ridhuan.amri · Wed Apr 04, 2012 9:40 am

Hi guys,

I am testing to make a high available SQL Failover Cluster between the virtual machines in my Hyper-V nodes. Currently, using Microsoft iSCSI Initiator, I want to connect the virtual machines to Starwind iSCSI targets which reside in the hosts. However, I keep on receiving "Service Unavailable" error. I tried to use QuickConnect to do it, and the error is "Unable to login to target". May I know what caused this and how I can troubleshoot it?

Regards,
Ridhuan

Wed Apr 04, 2012 9:54 am

This configuration should work. Check your firewall settings. Do you have anything in StarWind log?

ridhuan.amri wrote:Hi guys,

I am testing to make a high available SQL Failover Cluster between the virtual machines in my Hyper-V nodes. Currently, using Microsoft iSCSI Initiator, I want to connect the virtual machines to Starwind iSCSI targets which reside in the hosts. However, I keep on receiving "Service Unavailable" error. I tried to use QuickConnect to do it, and the error is "Unable to login to target". May I know what caused this and how I can troubleshoot it?

Regards,
Ridhuan

ridhuan.amri · Wed Apr 04, 2012 10:21 am

Hi Anton,

Thanks for the reply. Yes, by right it should work. I have checked my Windows firewall settings on both hosts and VM, but none is showing any blockade as I have already allowed all of rules. Inside the Starwind log I cannot see any error message, but please let me know what expression should I search inside the log for the connection attempt by the VM. Referring to the "Unable to login to target" message, does this mean the authentication is not valid or no communication been established at all?

Regards,
Ridhuan

Wed Apr 04, 2012 10:23 am

Just try to connect and capture and send back complete StarWind log.

ridhuan.amri wrote:Hi Anton,

Thanks for the reply. Yes, by right it should work. I have checked my Windows firewall settings on both hosts and VM, but none is showing any blockade as I have already allowed all of rules. Inside the Starwind log I cannot see any error message, but please let me know what expression should I search inside the log for the connection attempt by the VM. Referring to the "Unable to login to target" message, does this mean the authentication is not valid or no communication been established at all?

Regards,
Ridhuan

ridhuan.amri · Wed Apr 04, 2012 10:49 am

Hi Anton,

I got the error message already. It seems to say about the device is local. Please refer to the error below:

4/4 18:49:05.084 264 Tgt: *ERROR* 'iqn.2008-08.com.starwindsoftware:192.168.1.200-vm3partner' can't register session. The device 'HAImage5' may be owned by a local process!
4/4 18:49:05.084 264 T[374,1]: *ERROR* Login request: device open failed.
4/4 18:49:05.084 afc C[374], IN_LOGIN: Event - LOGIN_REJECT.
4/4 18:49:05.084 afc C[374], FREE: T7.
4/4 18:49:05.084 264 C[374], FREE: recvData returned 10058

How can I configure the device to be accessible by the VM?

Regards,
Ridhuan

ridhuan.amri · Thu Apr 05, 2012 7:10 am

Hello,

May I know how can I solve this issue? Please let me know what is wrong in my setup. I have turned off the firewall for both servers and clients, but still no connection. And I tried to change the management interface port from 3261 to 3260, still failed. I can telnet to both servers at port 3260 (blank screen) and port 3261 (displays Starwind message). What else should I check? Any feedback will be highly appreciated! Thank you.

Regards,
Ridhuan

Thu Apr 05, 2012 8:14 am

Can you tell me if you're using the latest version? We're currently offering 5.8 and the log fragment you've sent looks like 5.6
If that's true I'd first ask you to update, I'm sure that the problem will be solved then.

ridhuan.amri · Thu Apr 05, 2012 8:38 am

Hi Max,

I am using version 5.8. Please refer to the version I obtained from the log:

4/4 20:14:21.336 1194 Srv: StarWind Native SAN for Hyper-V v5.8.0 (Build 20120314, [SwHV], Win64)
4/4 20:14:21.336 1194 Srv: Built Mar 14 2012 19:46:03

May I know what login that is mentioned inside the log? That will help me to search for the authentication error.

Thu Apr 05, 2012 10:41 am

Well, that explains a lot - due to licensing policy only Physical Hosts where the StarWind Native SAN installed can connect to HA, and connection from any other machine will be rejected.
If you want to accomplish your plan you need to use iSCSI SAN edition, not Native SAN.

ridhuan.amri · Thu Apr 05, 2012 6:23 pm

Hi Anatoly,

Noted that. Will take a look at it. Thanks!

Regards,
Ridhuan

Thu Apr 05, 2012 8:17 pm

This seems to be a stupid limitation of Hyper-V native version we're really not aware of. For now please use basic product and we'll "flex" this limitation out pretty soon. Sorry for inconvenience!

ridhuan.amri wrote:Hi Anatoly,

Noted that. Will take a look at it. Thanks!

Regards,
Ridhuan

ridhuan.amri · Fri Apr 06, 2012 6:36 am

Hi Anton,

By right, do you mean the Starwind Native SAN for Hyper-V should support the connection from the Guest VM? What is the difference between this Starwind Native SAN for Hyper-V and Starwind iSCSI SAN, besides from the connection wise?

Regards,
Ridhuan

Sun Apr 08, 2012 11:05 pm

They are completely different products sharing the same codebase. Codepaths for loopback processing (when running inside Hyper-V parent partition) and generic network processing are completely different (performance and deadlock fight reasons).

ridhuan.amri wrote:Hi Anton,

By right, do you mean the Starwind Native SAN for Hyper-V should support the connection from the Guest VM? What is the difference between this Starwind Native SAN for Hyper-V and Starwind iSCSI SAN, besides from the connection wise?

Regards,
Ridhuan

joenoonz · Thu Jun 05, 2014 3:24 pm

I know this is an old thread but unfortunately I'm having the same/similar issue as described by the OP.

I am running Windows 2008 R2 and Starwind v 5.8.1975

I had previously set up several drives in iSCSI initiator that were working fine. I came in this morning and the quorum showed as the connection was down (HOST IP: 3260). I attempted via the iSCSI initiator to disconnect the quorum and reconnect. I am now being hit with a prompt that says "Service Unavailable."

I am new to this role but apparently the previous Sys Admin had the same problem intermittently. In this case he just reimaged both servers in the failover cluster. That is not a tenable way forward as this is apparently the third or fourth time this has happened.

Please assist if possible. I'm also going to create a new post about my issues in the main forum.

Thanks

Fri Jun 06, 2014 5:44 pm

You need to upgrade to V8 as 5.8 is dramatically old. It's out support for 2+ years. Please upgrade and tons of things has been changed in 5.xx -> 6.xx -> 8.xx, tons of bugs fixed (including lost of connectivity because of an operational timeout).