I know many of you may have the same feeling. It was
difficult for me to find the device for a new LUN allocated, as it
had some partition and I had to remove it before I can format as
VMFS. I found some KB articles, but not as easy as the good old
esxcfg-mpath. I will post some detail here later. 1. SSH and type
the esxcfg-mpath command as below to find the naa, where 90 is the
LUN#
[root@abcd]# esxcfg-mpath -b | grep 90
-B 5
naa.60060e80056e350000006e35
: HITACHI Fibre Channel Disk
(naa.60060e80056e350000006e35)
vmhba1:C0:T0:L90 LUN:90 state:active fc Adapter: WWNN:
20:00:00:00:c9:89:55:e0 WWPN: 10:00:00:00:c9:89:55:e0 Target: WWNN:
50:06:0e:80:05:6e:35:0d WWPN:
50:06:0e:80:05:6e:35:0d
vmhba2:C0:T0:L90 LUN:90 state:active fc Adapter: WWNN:
20:00:00:00:c9:89:56:da WWPN: 10:00:00:00:c9:89:56:da Target: WWNN:
50:06:0e:80:05:6e:35:1b WWPN:
50:06:0e:80:05:6e:35:1b
2. Once you
have the naa, use the following command to find the console
device.
[root@abcd]# esxcfg-scsidevs -l | grep
naa.60060e80056e350000006e -A
8
naa.60060e80056e
Device Type: Direct-Access
Size: 61441
MB
Display Name: HITACHI Fibre
Channel Disk
(naa.60060e80056e)
Plugin:
NMP
Console Device:
/dev/sdcf
Devfs Path:
/vmfs/devices/disks/naa.60060e80056e
Vendor: HITACHI Model: OPEN-V*6 Revis: 5001
SCSI
Level: 2 Is Pseudo: false Status: on
Is RDM
Capable: true Is Removable: false
Is Local:
false
Other
Names:
vml.02005a000060060e80056e35
naa.60060e80056e35
3. run
fdisk against the device and create the
partition.
[root@abcd]# fdisk
/dev/sdcf
Select option o to create a DOS partition and then w
to write the changes. And you are set.
4. Go to VC and define the VMFS volume
