PowerVault™ MD32X0, MD32X0i, and MD36X0i Series of Storage Arrays: Implementing Hyper-V
Page 27
Figure 15.
Summary of VM Using Live Migration
Troubleshooting
It is important that your storage status is at Optimal status. If an issue occurs, you can correct
problems by clicking on the Recovery Guru.
•
If you cannot access a virtual disk on the MD32X0, MD32X0i, or MD36X0i storage array,
make sure that the Host-to-Virtual Disk mapping is correct. On the iSCSI initiator, make
sure that you have access to all of the targets of the MD3200i storage array. Check any
network problems.
•
Run the
dsmUtil
command to make sure that all paths are available. This utility
comes with the MDSM MPIO, and it is located in the following directory (on x64
servers):
C:\Program Files (x86)\DSMDrivers\md3dsm>
•
Use the
–g
option, and enter the target ID of your MD3200 or 3000i storage array. The
storage arrays should be numbered sequentially.
C:\Program Files (x86)\DSMDrivers\md3dsm>dsmutil –g0
The paths appear in the output extract.
Lun #0 - WWN: 600a0b800036e4cd00000f9a47affbca
----------------
LunObject: 0x0