 | ||
| Mapping DMP meta-devices | ||
|---|---|---|
| Prev | Configuring Storage Foundation as backend storage for virtual machines | Next |
| ||
| Mapping DMP meta-devices | ||
|---|---|---|
| Prev | Configuring Storage Foundation as backend storage for virtual machines | Next |
Consistent mapping can be achieved from the host to the guest by using the Persistent Naming feature of DMP.
Running DMP in the host has other practical benefits:
Multi-path device can be exported as a single device. This makes managing mapping easier, and helps alleviate the 32 device limit, imposed by the VirtIO driver.
Path failover can be managed efficiently in the host, taking full advantage of the Event Source daemon to proactively monitor paths.
When Veritas InfoScale Solutions products are installed in the guest, the 'Persistent Naming' feature provides consistent naming of supported devices from the guest through the host to the array. The User Defined Names feature, or UDN, allows DMP virtual devices to have custom assigned names.
To map a DMP meta-device to a guest
# # /opt/VRTSrhevm/bin/vxrhevadm -p RHEV-M Admin Password -n guest_1 -d /dev/vx/dmp/xiv0_8614 attach
Where RHEV-M Admin Password is the administrator password on RHEV Manager.
As DMP devices are attached through virtio-scsi interface, the SCSI commands are directly passed to the device which makes SCSI inquiry possible in the guest resulting into correct device identification. For volume and file devices, guest to host device mapping is not possible.