iSCSI Path Discovery

[swordfish]

Hello

We are setting up Hyper-V on Windows Server 2019. We earlier used to setup SAN on Windows 2016 using FC and we never had to add manual sessions. When we added all the target IP addresses in the target list, it only shows 1 path to the LUN, unlike ESXi  which discovers all the paths as soon as you add targets. Then we added a second session (using the alias IP as the destination) and now it shows 2 paths to the LUN.  Are we missing something obvious or is it configured this way only. Another question that arises, what will happen when there will be a takeover or a server reboot. ? Do we have to add these paths manually every time?

Thanks

[GidonMarcus]

Hi,

Have a look at the iSCSI express guide. You can jump into page 14 which answers most of your concerns:

https://docs.netapp.com/ontap-9/topic/com.netapp.doc.exp-iscsi-cpg/iSCSI%20express%20configuration%20for%20Windows.pdf

[tahmad]

Hello @swordfish ,

were you able to find the answers in the document provided previously?