StarWind Software

Hi gents,

I am using vsan free edition on 2 Win2019 hyper-V.
scripts are very helpful and devices are online and synced.

I am configuring the iscsi initiator as per the documentation provided by StarWind.
1. discovery portal - loopback using microsoft iscsi initiator
1. discovery portal - partner ip - iscsi initiator - local IP (same subnet)

targets are then showing as normal.

I am connecting all targets except the partner witness.

My question is - how should the targets show up in Win Disk Mgmt. I see all the disks, local/partner
What should be like? I must be doing something wrong.

In the documentation it is showing up only 2 disks in diskpart, I get all the disks in standalone mode as far as I can see.

I am an iscsi noob, so I apologize in advance.

If you have 1 disk per server (an HA pair), in the iSCSI initiator you will see 2 targets. If you have two pairs of disks, you will see 4 targets.
In Disk Management, you will see the number of disks available on the current server. But this is true only for cases when Multipath IO support is enabled for iSCSI devices. If this is not done, you will the the double number of disks in Disk Management.

Hi Boris,

thanks for the reply.

I am following this : https://www.starwindsoftware.com/resour ... erver-2016

Indeed I have the following:

MultiPath enabled
2 servers
2 disks per server
I have created 3 targets per server - CSV1, CSV2 and QUORUM
Indeed I see 6 targets in the iScsi Initiator

I connect all iscsi targets except the loopback witness(quorum) so I have 5 connected targets per server
In disk management I see all 5 disks available

Problem is - what to map? in the scenario described in the link your colleague in diskpart are shown 2 disks, 1 witness and share whereas in my case I get 5 drives instead of 3

Many thanks in advance,

Andrei

Most likely you missed the following command:
that enables multipath support for iSCSI devices.
If you have 3 targets per server, you will see three disks connected with the above command applied.

Boris, you rock!

the command solves the additional disks shown in Disk Mgmt

Thank you!

Glad it solved your issue.