Hyper-V Failover Cluster MPIO Issue

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

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

Ivan (staff)
Staff
Posts: 172
Joined: Thu Mar 09, 2017 6:30 pm

Fri Mar 31, 2017 7:15 pm

Hello Kayakero,
Actually, one thing what you can try. I assume the reason of this "issue" is that iSCSI Initiator connecting to the partner targets earlier than the local ones will be available after StarWind synchronization. That is why you can see some targets, which synchronized later, connected to through partner iSCSI connections. It can be resolved by delayed iSCSI services start on your host. Follow this simple steps:
1)Open Services;
2)Find the Microsoft iSCSI Initiator Service;
3)Change the Startup type from Automatic to Manual;
4)Create the delayiSCSI.txt file on C:\ drive then open it and type next strings:

Code: Select all

timeout 60
net start MSiSCSI
Save this file as delayiSCSI.cmd. Note, the time can be changed depending on StarWind fast synchronization time.
5)Open the Task schedule and create new basic task
6)In Trigger tab choose "When the computer starts"
7) In Action tab choose "Start a program"
8 ) In program/script field browse path to the delayiSCSI.cmd
9) In the General tab check "Run whether user is logged on or not" and "Run with highest privileges"
10) In iSCSI Initiator change status of loopback connection to active
11) Restart the host one more time to confirm that issue resolved
Please let us know if it helps.
Post Reply