Most existing local controllers do not meet the hardware requirements for correct addressing and communication with RDM disks. By default, they are candidates for potential RDM on ESXi/ESX hosts, the local storage device feature is disabled.
To configure a local device as an RDM disk, perform the following operations:
Open the SSH service with the ESXi/ESX host
Obtain the hard disk identifier in the vSphere Client:
Log on to ESXI through SSH and configure RDM. Run the following command:
1 2 3 |
# Vmkfstools-z/vmfs/devices/disks//Vmfs/volumes///. Vmdk For example: # Vmkfstools-z/vmfs/devices/disks/t10.ATA _____ volumes/vmfs/volumes/PLEXTOR128G/RDMSTORE/WD320GRDM. vmdk |
Let's take a look at the truth of this file:
Note:: The size of the newly created RDM pointer file is the same as that of the bare device mapped to. It is a virtual file and does not occupy any storage space.In the above exampleIs the hard disk identifier,Is an existing disk drive letter formatted as VMFS, such as an SSD/HDD disk drive letter that stores Virtual Machine files. By default, ESXI does not allow creating folders. You can create folders in the resource browser of the client. Do not place the RDM pointer file on the disk to be mapped, which may cause the "file locked" error.
If you have created an RDM pointer file, use the vSphere Client to connect RDM to the VM:
Right-click the virtual machine to add the RDM disk.
ClickEdit Settings.
ClickAdd...
Select the hard disk.
Select to use an existing virtual disk.
Browse to the directory where the RDM pointer is saved in step 5, select the RDM pointer file, and then clickNext Step.
Select the virtual SCSI controller to connect the disk to, and then clickNext Step.
ClickComplete.
If the disk is online or mounted after you log on to the system:
Now, the new hard disk in the virtual machine list should be displayed as the mapped bare LUN.Note:: VMotion cannot be used because the VM has been migrated to a local disk.