DO you need the WWID for the luns?  If so the script gets the
following info.  I have not yet done one that correlated the datastore
vmware name to the wwid.  I need to do that for our own convenience in
dealing with our storage team and validating information, but take a
look and let me know if that is what you need.

http://www.blkmtn.org/VMware_get-lunpathsetting.ps1


VMhost  Lunpath State   Preferred       SanID
server01.company.com    
fc.20000000c9889bd9:10000000c9889bd9-fc.50060e8005bc8e51:50060e8005bc8e51-naa.60060e8005bc8e000000bc8e000000c0
  Active  FALSE   101:102:117:104:101:133:125:102
server01.company.com    
fc.20000000c9889bd8:10000000c9889bd8-fc.50060e8005bc8e41:50060e8005bc8e41-naa.60060e8005bc8e000000bc8e00000221
  Active  FALSE   101:102:117:104:101:133:125:101
server01.company.com    
fc.20000000c9889bd9:10000000c9889bd9-fc.50060e8005bc8e51:50060e8005bc8e51-naa.60060e8005bc8e000000bc8e00000221
  Active  FALSE   101:102:117:104:101:133:125:102


On Fri, Feb 26, 2010 at 6:55 AM, Kim Longenbaugh
<[email protected]> wrote:
> I’m no guru, but I thing you can get the info you need from the VIC (V3.5)
> or the vCenter (v4) by:
>
> Selecting the ESX host in the left pane,
>
> Selecting the “Configuration” tab in the right,
>
> Selecting “Storage Adapters”
>
> Highlight the Storage Adapter providing the storage
>
> Looking at the “path” or “canonical path” info for a volume.  If it’s iSCSI,
> then the iSCSI name is also provided.
>
>
>
> That’s the only way I know, but I’m sure there’s a way to find it with the
> CLI as well.
>
>
>
> ________________________________
>
> From: Jeff Bunting [mailto:[email protected]]
> Sent: Friday, February 26, 2010 8:44 AM
> To: NT System Admin Issues
> Subject: ESX LUN ids
>
>
>
> Any of you ESX gurus know of a command (or maybe a log to look at) that will
> show what the LUN ids are on an ESX host?  I've been googling about, but
> haven't found anything yet.  We've been migrating a cluster to a new SAN and
> one of the hosts is having a problem with some of the new LUNs because the
> disk signatures are different.  Someone else configured the LUNs on the SAN;
> I'm trying to determine if the problem is there or on the host.
>
> Thanks,
> Jeff
>
>
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to