Community maintenance is complete. Thank you for your patience!

ONTAP Discussions

iSCSI Path Discovery




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?





Hello @swordfish ,

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




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

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner