<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber? in VMware PowerCLI Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022733#M66280</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would appreciate if anybody has some fancy SCSI-3 drives try this out and paste the output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Author of the upcoming book: &lt;A href="http://sapienpress.com/vmware.asp"&gt;Managing VMware Infrastructure with PowerShell&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Co-Host, PowerScripting Podcast (http://powerscripting.net)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Aug 2008 17:57:39 GMT</pubDate>
    <dc:creator>halr9000</dc:creator>
    <dc:date>2008-08-05T17:57:39Z</dc:date>
    <item>
      <title>bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022731#M66278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;(this was already reported privately to c_shanklin, posting here for others' benefit)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For some reason the serial #'s are not being populated below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="noformat"&gt;PS &amp;gt; 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&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Author of the upcoming book: &lt;A href="http://sapienpress.com/vmware.asp"&gt;Managing VMware Infrastructure with PowerShell&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Co-Host, PowerScripting Podcast (http://powerscripting.net)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 13:38:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022731#M66278</guid>
      <dc:creator>halr9000</dc:creator>
      <dc:date>2008-08-05T13:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022732#M66279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure this is a VITK bug.&lt;/P&gt;&lt;P&gt;In the &lt;A href="http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.host.ScsiLun.html"&gt;ScsiLun&lt;/A&gt; object the &lt;STRONG&gt;serialNumber&lt;/STRONG&gt; property also returns "unavailable" for my iSCSI LUNs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the SDK reference it says "&lt;EM&gt;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.&lt;/EM&gt;"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 17:17:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022732#M66279</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2008-08-05T17:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022733#M66280</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would appreciate if anybody has some fancy SCSI-3 drives try this out and paste the output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Author of the upcoming book: &lt;A href="http://sapienpress.com/vmware.asp"&gt;Managing VMware Infrastructure with PowerShell&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Co-Host, PowerScripting Podcast (http://powerscripting.net)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 17:57:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022733#M66280</guid>
      <dc:creator>halr9000</dc:creator>
      <dc:date>2008-08-05T17:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022734#M66281</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just checked my very fancy IBM Bladecenter--still says unavailable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Author of the upcoming book: &lt;A href="http://sapienpress.com/vmware.asp"&gt;Managing VMware Infrastructure with PowerShell&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Co-Host, PowerScripting Podcast (http://powerscripting.net)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 18:01:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022734#M66281</guid>
      <dc:creator>halr9000</dc:creator>
      <dc:date>2008-08-05T18:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: bug in VMHostStorageInfoImpl.ScsiLun.SerialNumber?</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022735#M66282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the smae beahivor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Esxi 5.5 fc lun ( netapp,infinidat,xiv) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Yoni Shperling&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 May 2014 10:38:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/bug-in-VMHostStorageInfoImpl-ScsiLun-SerialNumber/m-p/2022735#M66282</guid>
      <dc:creator>yonish</dc:creator>
      <dc:date>2014-05-29T10:38:06Z</dc:date>
    </item>
  </channel>
</rss>

