Peter> Windows command "wmic diskdrive get serialnumber,deviceid" Peter> lists serial number of each device. It just happens to display the Peter> S/N in the same ASCII format as "lun show -v" (7-mode) and "lun show Peter> -vserver <svm> -path <path>".
This is really useful. Now I just did this on my system and I get a bunch of disks without serial numbers shown. Is this because I need to install the Netapp PowerShell extensions first? I've been distracted by other issues all day today, and just now got a chance to try this out.
Peter> C:\Users\administrator.VGIBU>wmic diskdrive get serialnumber,deviceid Peter> DeviceID SerialNumber Peter> \.\PHYSICALDRIVE2 2Ff5c]ALEUCc Peter> \.\PHYSICALDRIVE1 2Ff5c]ALEUCe Peter> \.\PHYSICALDRIVE0 6000c29019552f108aa8b158a2eb040d
f35> lun show -v Peter> /vol/luntest/l1 10.0g (10742215680) (r/w, online, mapped) Peter> Serial#: 2Ff5c]ALEUCc Peter> Multiprotocol Type: windows_2008 Peter> Maps: winluntest=1 Peter> /vol/luntest/l2 10.0g (10742215680) (r/w, online, mapped) Peter> Serial#: 2Ff5c]ALEUCe Peter> Multiprotocol Type: windows_2008 Peter> Maps: winluntest=2
Peter> (Yes, I snipped some)
Peter> You won't get the NetApp volume/LUN/host name from tools native Peter> to a host/guest operating system, since that is not presented Peter> in standard SCSI code pages (a.k.a. VPD - Vital Product Data). Peter> NetApp management IP addresses are buried in proprietary pages, Peter> which is how SANLUN, VSC and other tools discover the NetApp Peter> controller or cluster hosting the LUN. From there the tools Peter> match S/N or NAA ID (which contains the S/N), like we just did Peter> above.
This is a shame, since it looks like it wouldn't be all that hard for the info to be pulled out and presented easily enough. Oh well... getting even this much info will be a big help.
John