Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Identifying disks when working with VMware ESXi (1014953)

Last Updated: 9/28/2023Categories: InformationalTotal Views: 171921Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

77 like this article

Subscribe to get an email
newsletter with new updates

77 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to 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.

Use Skyline Health Diagnostics to 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 use Skyline Advisor to 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

Run these commands to collect disk and LUN information from ESXi:

Run the esxcli storage core path list or esxcfg-scsidevs -l command to generate a list of all LUN paths currently connected to the ESXi host.

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: <WWNN> WWPN: <WWPN>
Target Transport Details: WWNN: <WWNN> WWPN: <WWPN>
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: <WWNN> WWPN: <WWPN>
Target Transport Details: WWNN: <WWNN> WWPN: <WWPN>

Note: For the detail path information of a specific device ( Device: <device>), run the esxcli 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:L3 LUN:3 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba1:C0:T1:L3 LUN:3 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba0:C0:T0:L3 LUN:3 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba0:C0:T1:L3 LUN:3 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>

naa.60002ac0000000000000000a0001e77e : 3PARdata Fibre Channel Disk (naa.60002ac0000000000000000a0001e77e)
vmhba1:C0:T0:L7 LUN:7 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba1:C0:T1:L7 LUN:7 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba0:C0:T0:L7 LUN:7 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>
vmhba0:C0:T1:L7 LUN:7 state:active fc Adapter: WWNN: <WWNN> WWPN: <WWPN>  Target: WWNN: <WWNN> WWPN: <WWPN>

eui.00e04c2020202000 : Local USB Direct-Access (eui.00e04c2020202000)
vmhba32:C0:T0:L0 LUN:0 state:active Local HBA vmhba32 channel 0 target 0

Run the esxcli storage core device list command 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 the esxcli storage vmfs extent list command 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-local 4e0d86e1-0db6f826-6991-d8d3855ff8d6 0 mpx.vmhba2:C0:T0:L0 3
datastore1 4d4ac840-c1386fa0-9f6d-0050569300a7 0 naa.6006016094602800364ce22e3825e011 1
vmfs5 4dad8f16-911648ca-d660-d8d38563e658 0 naa.600601609460280052eb8621b73ae011 1

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 the esxcli storage filesystem list command 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-0050569300a7 datastore1 4d4ac840-c1386fa0-9f6d-0050569300a7 true VMFS-3 9395240960 746586112
/vmfs/volumes/ 4e0d86e1-0db6f826-6991-d8d3855ff8d6 esxi-local 4e0d86e1-0db6f826-6991-d8d3855ff8d6 true VMFS-5 294473695232 293884395520
/vmfs/volumes/ 4dad8f16-911648ca-d660-d8d38563e658 vmfs5 4dad8f16-911648ca-d660-d8d38563e658 true VMFS-5 1879048192 220200960
/vmfs/volumes/ 4e303229-94dedb01-508c-d8d3855ff8d6 4e303229-94dedb01-508c-d8d3855ff8d6 true vfat 4293591040 4290248704
/vmfs/volumes/ f9618575-313f4ef5-943d-d5308d29e876 Hypervisor1 f9618575-313f4ef5-943d-d5308d29e876 true vfat 261853184 128241664
/vmfs/volumes/ 12e6c575-9a49251d-634c-1c34f28a0238 Hypervisor2 12e6c575-9a49251d-634c-1c34f28a0238 true vfat 261853184 163708928
/vmfs/volumes/ 2da668ef-40e5d96b-90bf-855ddb9c5547 Hypervisor3 2da668ef-40e5d96b-90bf-855ddb9c5547 true vfat 299778048 114704384

Run the ls -alh /vmfs/devices/disks command to list the possible targets for certain storage operations.

You see an output similar to:
lrwxrwxrwx 1 root root 19 Jul 27 16:40 vml.0000000000766d686261323a303a30 -> mpx.vmhba2:C0:T0:L0
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:1 -> mpx.vmhba2:C0:T0:L0:1
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:2 -> mpx.vmhba2:C0:T0:L0:2
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:3 -> mpx.vmhba2:C0:T0:L0:3
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:4 -> mpx.vmhba2:C0:T0:L0:4
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:5 -> mpx.vmhba2:C0:T0:L0:5
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:6 -> mpx.vmhba2:C0:T0:L0:6
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:7 -> mpx.vmhba2:C0:T0:L0:7
lrwxrwxrwx 1 root root 21 Jul 27 16:40 vml.0000000000766d686261323a303a30:8 -> mpx.vmhba2:C0:T0:L0:8
lrwxrwxrwx 1 root root 36 Jul 27 16:40 vml.02000600006006016094602800364ce22e3825e011524149442030 -> naa.6006016094602800364ce22e3825e011
lrwxrwxrwx 1 root root 38 Jul 27 16:40 vml.02000600006006016094602800364ce22e3825e011524149442030:1 -> naa.6006016094602800364ce22e3825e011:1
lrwxrwxrwx 1 root root 36 Jul 27 16:40 vml.02000e0000600601609460280052eb8621b73ae011524149442030 -> naa.600601609460280052eb8621b73ae011
lrwxrwxrwx 1 root root 38 Jul 27 16:40 vml.02000e0000600601609460280052eb8621b73ae011524149442030:1 -> naa.600601609460280052eb8621b73ae011:1

These are the definitions for some of identifiers and their conventions:

naa.<NAA>:<Partition> or eui.<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 the International 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 as vmkfstools.

Example: naa.6090a038f0cd4e5bdaa8248e6856d4fe:3 = Partition 3 of LUN naa.6090a038f0cd4e5bdaa8248e6856d4fe.

mpx.vmhba<Adapter>:C<Channel>:T<Target>:L<LUN> or mpx.vmhba<Adapter>:C<Channel>:T<Target>:L<LUN>:<Partition>

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> or vml.<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 as vmkfstools.

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 as vmkfstools.

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 different vmhba#. If the adapter supports multiple connections to the same controller, 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 additional esxcli storage commands available in ESXi 6.0 to identify mounted Virtual Volumes or NFS v4.1 volumes. For more information, see:

The esxcli storage Commands section in the vSphere 6.0 Command-Line Interface Documentation

The Virtual Volumes and esxcli Commands section in the vSphere 6.0 Troubleshooting guide

The Working with Virtual Volumes section in the vSphere 6.0 Storage guide

The Create an NFS Datastore section in the vSphere 6.0 Storage guide

Identificando discos ao trabalhar com o VMware ESXi/ESX
使用 VMware ESXi/ESX 时识别磁盘
Windows と ESXi/ESX ホスト間でファイルをやりとりするために、USB フラッシュドライブを使用する方法
VMware ESXi/ESX を操作するときのディスクの識別
Identificar discos al trabajar con VMware ESXi/ESX
Identifizieren der Festplatten bei der Arbeit mit VMware ESXi/ESX
How to detach a LUN device from ESXi hosts
Identifying Raw Device Mappings (RDMs) using the vSphere Client

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere

VMware ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 8.0.x

VMware vSphere ESXi 7.0.x

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere 7.0.x

Take Our Survey

Support Assistant