VMware Cloud Community
halr9000
Commander
Commander
Jump to solution

bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?

(this was already reported privately to c_shanklin, posting here for others' benefit)

For some reason the serial #'s are not being populated below.

PS > Get-VMHost | Get-VMHostStorage | select -ExpandProperty ScsiLun | select Vendor, Model, SerialNumber

Vendor                         Model                          SerialNumber
------                         -----                          ------------
OPNFILER                       VIRTUAL-DISK                   unavailable
FUJITSU                        MAP3735NP                      unavailable
FUJITSU                        MAP3735NP                      unavailable
SEAGATE                        ST336607LW                     unavailable
OPNFILER                       VIRTUAL-DISK                   unavailable
SEAGATE                        ST336607LW                     unavailable

Author of the upcoming book: Managing VMware Infrastructure with PowerShell

Co-Host, PowerScripting Podcast (http://powerscripting.net)

My signature used to be pretty, but then the forum software broked it. vExpert. Microsoft MVP (Windows PowerShell). Author, Podcaster, Speaker. I'm @halr9000
Tags (1)
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

I'm not sure this is a VITK bug.

In the ScsiLun object the serialNumber property also returns "unavailable" for my iSCSI LUNs.

In the SDK reference it says "The serial number of the SCSI device. For a device that is SCSI-3 compliant, this property is derived from page 80h of the Vital Product Data (VPD), as defined by the SCSI-3 Primary Commands (SPC-3) spec. Not all SCSI-3 compliant devices provide this information. For devices that are not SCSI-3 compliant, this property is not defined."


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
4 Replies
LucD
Leadership
Leadership
Jump to solution

I'm not sure this is a VITK bug.

In the ScsiLun object the serialNumber property also returns "unavailable" for my iSCSI LUNs.

In the SDK reference it says "The serial number of the SCSI device. For a device that is SCSI-3 compliant, this property is derived from page 80h of the Vital Product Data (VPD), as defined by the SCSI-3 Primary Commands (SPC-3) spec. Not all SCSI-3 compliant devices provide this information. For devices that are not SCSI-3 compliant, this property is not defined."


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
halr9000
Commander
Commander
Jump to solution

That makes a lot of sense. I would ask VMware to consider having the VITK return $null instead of "undefined", as that is consistent with other powershell conventions. But otherwise, now that I know what to expect I can safely document it thusly in my book.

I would appreciate if anybody has some fancy SCSI-3 drives try this out and paste the output.

Author of the upcoming book: Managing VMware Infrastructure with PowerShell

Co-Host, PowerScripting Podcast (http://powerscripting.net)

My signature used to be pretty, but then the forum software broked it. vExpert. Microsoft MVP (Windows PowerShell). Author, Podcaster, Speaker. I'm @halr9000
0 Kudos
halr9000
Commander
Commander
Jump to solution

Just checked my very fancy IBM Bladecenter--still says unavailable.

Author of the upcoming book: Managing VMware Infrastructure with PowerShell

Co-Host, PowerScripting Podcast (http://powerscripting.net)

My signature used to be pretty, but then the forum software broked it. vExpert. Microsoft MVP (Windows PowerShell). Author, Podcaster, Speaker. I'm @halr9000
0 Kudos
yonish
Contributor
Contributor
Jump to solution

Hello,

I have the smae beahivor.

Esxi 5.5 fc lun ( netapp,infinidat,xiv)

Best regards,

Yoni Shperling

0 Kudos