<?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>article Script: Get-ScsiLunInfo in VMware PowerCLI Documents</title>
    <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Script-Get-ScsiLunInfo/ta-p/2793921</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's a quick helper script I wrote that helps generate a report of specific properties of SCSI LUNs attached to a VMHost.&amp;nbsp; Script supports 2 parameters, one for the VMHost and another for the HBA type you wish to target.&amp;nbsp; Lots of room for improvement (e.g. parameter to target an HBA by name.)&amp;nbsp; Main goal was to produce a report that ties together the LUN ID, Canonical Name and Console Device Name on a per-host basis.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Script makes 2 assumptions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. PowerShell already has the PowerCLI Snap-in loaded.&lt;/P&gt;&lt;P&gt;2. You're already connected to a VI-Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this adds some value to the community!&amp;nbsp; Enjoy!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 22 Feb 2014 03:18:38 GMT</pubDate>
    <dc:creator>aaronwsmith</dc:creator>
    <dc:date>2014-02-22T03:18:38Z</dc:date>
    <item>
      <title>Script: Get-ScsiLunInfo</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Script-Get-ScsiLunInfo/ta-p/2793921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's a quick helper script I wrote that helps generate a report of specific properties of SCSI LUNs attached to a VMHost.&amp;nbsp; Script supports 2 parameters, one for the VMHost and another for the HBA type you wish to target.&amp;nbsp; Lots of room for improvement (e.g. parameter to target an HBA by name.)&amp;nbsp; Main goal was to produce a report that ties together the LUN ID, Canonical Name and Console Device Name on a per-host basis.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Script makes 2 assumptions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. PowerShell already has the PowerCLI Snap-in loaded.&lt;/P&gt;&lt;P&gt;2. You're already connected to a VI-Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this adds some value to the community!&amp;nbsp; Enjoy!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Feb 2014 03:18:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Script-Get-ScsiLunInfo/ta-p/2793921</guid>
      <dc:creator>aaronwsmith</dc:creator>
      <dc:date>2014-02-22T03:18:38Z</dc:date>
    </item>
  </channel>
</rss>

