Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.
UseSkyline Advisorto avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.
UseSkyline Health Diagnosticsto root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.
If you require additional help from technical support, please useSkyline Advisorto initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.
Purpose
When performing troubleshooting with ESXi storage, use command line tools which require you to identify a specific disk or LUN connected to ESXi. This article provides information on different ways to identify these disks.
Resolution
ESXi 6.x/7.x
Run these commands to collect disk and LUN information from ESXi:
You see an output similar to: fc.5001438005685fb5:5001438005685fb4-fc.50060160c46036df:50060167446036df-naa.6006016094602800e07ff528b73ae011 UID: fc.5001438005685fb5:5001438005685fb4-fc.50060160c46036df:50060167446036df-naa.6006016094602800e07ff528b73ae011 Runtime Name:vmhba0:C0:T0:L23 Device:naa.6006016094602800e07ff528b73ae011 Device Display Name: DGC Fibre Channel Disk (naa.6006016094602800e07ff528b73ae011) Adapter: vmhba0 Channel: 0 Target: 0 LUN: 23 Plugin: NMP State: active Transport: fc Adapter Identifier: fc.5001438005685fb5:5001438005685fb4 Target Identifier: fc.50060160c46036df:50060167446036df Adapter Transport Details: WWNN: 50:01:43:80:05:68:5f:b5 WWPN: 50:01:43:80:05:68:5f:b4 Target Transport Details: WWNN: 50:06:01:60:c4:60:36:df WWPN: 50:06:01:67:44:60:36:df fc.5001438005685fb5:5001438005685fb4-fc.50060160c46036df:5006016f446036df-naa.6006016094602800e07ff528b73ae011 UID: fc.5001438005685fb5:5001438005685fb4-fc.50060160c46036df:5006016f446036df-naa.6006016094602800e07ff528b73ae011 Runtime Name:vmhba0:C0:T1:L23 Device:naa.6006016094602800e07ff528b73ae011 Device Display Name: DGC Fibre Channel Disk (naa.6006016094602800e07ff528b73ae011) Adapter: vmhba0 Channel: 0 Target: 1 LUN: 23 Plugin: NMP State: active Transport: fc Adapter Identifier: fc.5001438005685fb5:5001438005685fb4 Target Identifier: fc.50060160c46036df:5006016f446036df Adapter Transport Details: WWNN: 50:01:43:80:05:68:5f:b5 WWPN: 50:01:43:80:05:68:5f:b4 Target Transport Details: WWNN: 50:06:01:60:c4:60:36:df WWPN: 50:06:01:6f:44:60:36:df
Note: For the detail path information of a specific device(Device:<device>), run theesxcli storage core path list -d <device>command .
Alternatively, you could use the "esxcfg-mpath -b"command to list out all the working paths for the devices detected.
You see an output similar to: naa.60002ac000000000000000060001e77e: 3PARdata Fibre Channel Disk (naa.60002ac000000000000000060001e77e) vmhba1:C0:T0:L3LUN:3 state:active fc Adapter: WWNN: 50:06:0b:00:00:c2:72:0b WWPN: 50:06:0b:00:00:c2:72:0a Target: WWNN: 2f:f7:00:02:ac:01:e7:7e WWPN: 20:22:00:02:ac:01:e7:7e vmhba1:C0:T1:L3LUN:3 state:active fc Adapter: WWNN: 50:06:0b:00:00:c2:72:0b WWPN: 50:06:0b:00:00:c2:72:0a Target: WWNN: 2f:f7:00:02:ac:01:e7:7e WWPN: 21:22:00:02:ac:01:e7:7e vmhba0:C0:T0:L3LUN:3 state:active fc Adapter: WWNN: 50:06:0b:00:00:c2:72:09 WWPN: 50:06:0b:00:00:c2:72:08 Target: WWNN: 2f:f7:00:02:ac:01:e7:7e WWPN: 22:21:00:02:ac:01:e7:7e vmhba0:C0:T1:L3LUN:3 state:active fc Adapter: WWNN: 50:06:0b:00:00:c2:72:09 WWPN: 50:06:0b:00:00:c2:72:08 Target: WWNN: 2f:f7:00:02:ac:01:e7:7e WWPN: 23:21:00:02:ac:01:e7:7e
eui.00e04c2020202000: Local USB Direct-Access (eui.00e04c2020202000) vmhba32:C0:T0:L0LUN:0 state:active Local HBA vmhba32 channel 0 target 0
Run theesxcli storage core device listcommand to generate a list of LUNs currently connected to the ESXi host.
You see an output similar to: mpx.vmhba0:C0:T0:L0 Display Name: Local VMware Disk (mpx.vmhba2:C0:T0:L0) Has Settable Display Name: false Size: 286070 Device Type: Direct-Access Multipath Plugin: NMP Devfs Path: /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0 Vendor: VMware Model: Block device Revision: 1.0 SCSI Level: 2 Is Pseudo: false Status: on Is RDM Capable: false Is Local: true Is Removable: false Is SSD: false Is Offline: false Is Perennially Reserved: false Thin Provisioning Status: unknown Attached Filters: VAAI Status: unsupported Other UIDs:vml.0000000000766d686261323a303a30
Alternatively you could usethe "esxcfg-scsidevs -c" to list out all the devices being detected by the ESXi host.
You see an output similar to:
Run theesxcli storage vmfs extent listcommand to generate a list of extents for each volume and mapping from device name to UUID.
You see an output similar to: Volume Name VMFS UUID Extent Number Device Name Partition ------------ ----------------------------------- ------------- ------------------------------------ --------- esxi-local4e0d86e1-0db6f826-6991-d8d3855ff8d60mpx.vmhba2:C0:T0:L03 datastore14d4ac840-c1386fa0-9f6d-0050569300a70naa.6006016094602800364ce22e3825e0111 vmfs54dad8f16-911648ca-d660-d8d38563e6580naa.600601609460280052eb8621b73ae0111
Alternatively, you could execute the "esxcfg-scsidevs -m" command to list out all the VMFS backed datastores that are currently active/mounted on the host along with their UUID information.
The output should look similar to:
Run theesxcli storage filesystem listcommand to generate a compact list of the LUNs currently connected to the ESXi host, including VMFS version.
You see an output similar to: Mount Point Volume Name UUID Mounted Type Size Free ------------------------------------------------- ------------ ----------------------------------- ------- ------ ------------- ------------ /vmfs/volumes/f98fbd51-d2efb396 ISOs f98fbd51-d2efb396 true NFS 581284225024 181569196032 /vmfs/volumes/4d4ac840-c1386fa0-9f6d-0050569300a7datastore14d4ac840-c1386fa0-9f6d-0050569300a7true VMFS-3 9395240960 746586112 /vmfs/volumes/4e0d86e1-0db6f826-6991-d8d3855ff8d6esxi-local4e0d86e1-0db6f826-6991-d8d3855ff8d6true VMFS-5 294473695232 293884395520 /vmfs/volumes/4dad8f16-911648ca-d660-d8d38563e658vmfs54dad8f16-911648ca-d660-d8d38563e658true VMFS-5 1879048192 220200960 /vmfs/volumes/4e303229-94dedb01-508c-d8d3855ff8d64e303229-94dedb01-508c-d8d3855ff8d6true vfat 4293591040 4290248704 /vmfs/volumes/f9618575-313f4ef5-943d-d5308d29e876Hypervisor1f9618575-313f4ef5-943d-d5308d29e876true vfat 261853184 128241664 /vmfs/volumes/12e6c575-9a49251d-634c-1c34f28a0238Hypervisor212e6c575-9a49251d-634c-1c34f28a0238true vfat 261853184 163708928 /vmfs/volumes/2da668ef-40e5d96b-90bf-855ddb9c5547Hypervisor32da668ef-40e5d96b-90bf-855ddb9c5547true vfat 299778048 114704384
Run thels -alh /vmfs/devices/diskscommand to list the possible targets for certain storage operations.
These are the definitions for some of identifiers and their conventions:
naa.<NAA>:<Partition>oreui.<EUI>:<Partition>
NAA stands for Network Addressing Authority identifier. EUI stands for Extended Unique Identifier. The number is guaranteed to be unique to that LUN. The NAA or EUI identifier is the preferred method of identifying LUNs and the number is generated by the storage device. Since the NAA or EUI is unique to the LUN, if the LUN is presented the same way across all ESXi hosts, the NAA or EUI identifier remains the same. For more information on these standards, see the SPC-3 documentation from theInternational Committee for Information Technology Standards (T10).
The<Partition>represents the partition number on the LUN or Disk. If the<Partition>is specified as 0, it identifies the entire disk instead of only one partition. This identifier is generally used for operations with utilities such asvmkfstools.
Example:naa.6090a038f0cd4e5bdaa8248e6856d4fe:3= Partition 3 of LUNnaa.6090a038f0cd4e5bdaa8248e6856d4fe.
Some devices do not provide the NAA number described above. In these circumstances, an MPX Identifier is generated by ESXi to represent the LUN or disk. The identifier takes the form similar to that of the canonical name of previous versions of ESXi with the mpx. prefix. This identifier can be used in the exact same way as the NAA Identifier(NaaID) described above.
vml.<VML>orvml.<VML>:<Partition>
The VML Identifier can be used interchangeably with the NAA Identifier and the MPX Identifier. Appending:<Partition>works in the same way described above. This identifier is generally used for operations with utilities such asvmkfstools.
To find out the vml ID run the command:
vmkfstools -q <vm-disk>.vmdk
vmhba<Adapter>:C<Channel>:T<Target>:L<LUN>
This identifier is now used exclusively to identify a path to the LUN. When ESXi detects that paths associated to one LUN, each path is assigned this Path Identifier. The LUN also inherits the same name as the first path, but it is now used an a Runtime Name, and not used as readily as the above mentioned identifiers as it may be different depending on the host you are using. This identifier is generally used for operations with utilities such asvmkfstools.
Example:vmhba1:C0:T0:L0= Adapter 1, Channel 0, Target 0, and LUN 0.
Note: Generally, multi-port fiber channel adapters are equipped with dedicated controllers for each connection, and therefore each controller is represented by differentvmhba#. If the adapter supports multiple connections to thesamecontroller, it is represented by a different channel number. This representation is directly dependent on the capability of the adapter.
<UUID>
The<UUID>is a unique number assigned to a VMFS volume upon the creation of the volume. It may be included in syntax where you need to specify the full path of specific files on a datastore.
Related Information
There are additionalesxcli storagecommands available in ESXi 6.0 to identify mounted Virtual Volumes or NFS v4.1 volumes. For more information, see:
