Identifying boot LUNs for Boot From SAN Configurations

Products

• VMware vSphere ESXi

Issue/Introduction

This article provides steps to identify boot LUNs for Boot from SAN configurations.

Environment

7.x
8.x

Resolution

To identify boot LUNs for ESXi Boot from SAN configurations, first find what LUNs are being used by the bootbank and the altbootbank. By definition, these LUNs will be the boot LUNs:

1. SSH to the ESXi host via root
2. Obtain the bootbank and altbootbank UUIDs:

ls -l /

Example:

lrwxrwxrwx 1 root root 49 Oct 27 17:55 altbootbank -> /vmfs/volumes/########-########-####-############
drwxr-xr-x 1 root root 512 Sep 17 01:11 bin
lrwxrwxrwx 1 root root 49 Oct 27 17:55 bootbank -> /vmfs/volumes/########-########-####-############

3. Obtain the disk ID:

vmkfstools -P <path>

Example:

vmkfstools -P /vmfs/volumes/########-########-####-############
 

vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 261853184 (63929 file blocks * 4096), 114647040 (27990 blocks) avail
UUID: ########-########-####-############
Partitions spanned (on "disks"):
naa.xxxxxxxxxxxxxxxxxxxxxxx:6

4. Check the device properties:

esxcli storage nmp device list -d <naaID>
esxcli storage core device list -d <naaID>

Example

esxcli storage nmp device list -d naa.################################

naa.################################
Device Display Name: NETAPP Fibre Channel Disk (naa.################################)
Storage Array Type: VMW_SATP_DEFAULT_AA
Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba0:C0:T6:L0;current=vmhba0:C0:T6:L0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba0:C0:T6:L0

 

Example

esxcli storage core device list -d naa.################################

 

naa.################################
Display Name: NETAPP Fibre Channel Disk (naa.################################)
Has Settable Display Name: true
Size: 30720
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/naa.################################
Vendor: NETAPP
Model: LUN
Revision: 0.2
SCSI Level: 4
Is Pseudo: false
Status: on
Is RDM Capable: true
Is Local: false
Is Removable: false
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unknown
Other UIDs: vml.######################################################

 

To find the "friendly names" of these LUNs as seen in the vCenter/ESXi host client views, use the "esxcli storage filesystem list" command, and searching for the naa number(s) for the boot LUN(s):

/vmfs/devices/disks/naa.################################    spr-lun3    ########-########-####-############    true    VMFS-5    805037932544    400613703680

Using the above example, "spr-lun3" is the friendly name of the boot LUN because its naa number ################################ matches what the previous outputs.

Note: Locally-attached disk LUNs may not have "friendly names" set at all.