Identify ONTAP LUN on Windows host

[schmitz_peter]

Hi all,

I give up, I'll never be a Windows guy.

Please enlighten me: With no SnapDrive on board, how is it possible to identify the name of an iSCSI LUN on an ONTAP 9 filer?

I tried to match any sort of number from the outputs of

::> lun mapping show

::> lun show

and

::> iscsi session show

with the outputs of

PS C:\Users\admin> iscsicli

and

PS C:\Users\admin> Get-IscsiConnection

to no avail.

All I want is to find the name of the LUN/volume on Windows to find the corresponding object on the filer to modify.

Any clues?

Thanks and best regards

Peter

[mjdalton1]

Have you tried the MicroSoft iSCSI initiator utility in Windows. This should give you the LUN ID 

https://www.techrepublic.com/blog/how-do-i/how-do-i-install-configure-and-use-microsofts-iscsi-initiator/

Hope this helps

[schmitz_peter]

---

@mjdalton1 wrote:

Have you tried the MicroSoft iSCSI initiator utility in Windows. This should give you the LUN ID 

https://www.techrepublic.com/blog/how-do-i/how-do-i-install-configure-and-use-microsofts-iscsi-initiator/

Hope this helps

---

I have, yes. Unfortunately LUN ID reported by Windows doesn't match the LUN ID on the NetApp side.

But thanks for the info.

Peter

[dkon · Accepted solution]

Using native MPIO you can find the serial number with something like `mplcaim -v mpio.txt`.  Pop open mpio.txt to find the SN, and you should be able to match that up with the output of `lun show -fields serial-hex` on the filer.  Match up the MPIO disks to system disks with `mpclaim -s -d`.

[schmitz_peter]

---

@dkon wrote:

Using native MPIO you can find the serial number with something like `mplcaim -v mpio.txt`.  Pop open mpio.txt to find the SN, and you should be able to match that up with the output of `lun show -fields serial-hex` on the filer.  Match up the MPIO disks to system disks with `mpclaim -s -d`.

---

Yeah, that's it! Cheers.

Peter

[RJC]

The mpclaim approach did not work for me.

The powershell command in the following NetApp KB worked perfectly 🙂

https://kb.netapp.com/onprem/ontap/da/SAN/How_to_find_the_serial_number_of_a_LUN_in_Windows_using_PowerShell

This provides the value you can find in ONTAP for the "serial", not the "serial-hex".