HP MPIO Full Featured DSM for SAN Virtualization Services Platform 4.01.00 installation and reference guide (5697-0237, January 2010)

Solution: Run the following commands from the command prompt pointed to the folder "C:\Program
Files\Common Files\Hewlett-Packard\HP MPIO DSM\COMMON FILES\mof" and register the
following mof files:
• mofcomp hpwmi.mof
• mofcomp HPDSMHighPerfProvider.mof
• mofcomp -N:root\wmi LBPolicy.mof
• mofcomp -N:root\wmi mpdisk.mof
• mofcomp -N:root\wmi mpio.mof
• mofcomp -N:root\wmi pdo.mof
Problem: HPDSM CLI or HP MPIO DSM Manager does not display the output.
Solution: Run the following commands from the command prompt pointed to the folder "C:\Program
Files\Common Files\Hewlett-Packard\HP MPIO DSM\COMMON FILES\mof" and register the
following mof files:
• mofcomp hpwmi.mof
• mofcomp HPDSMHighPerfProvider.mof
• mofcomp -N:root\wmi LBPolicy.mof
• mofcomp -N:root\wmi mpdisk.mof
• mofcomp -N:root\wmi mpio.mof
• mofcomp -N:root\wmi pdo.mof
Problem: In a clustered system, the devices display with an yellow-bang in the Device Manager screen.
Solution: Do the following:
1. Ensure that the system sees the paths from both the SVSP Data Path Modules.
2. Reboot the system.
Problem: Host does not display devices when you change the configurations of a LUN and/or HBA
from the management application. The configuration changes include adding or removing LUN(s) to
or from the host, or changing the HBA relation.
Solution: Re-scan the host by completing the following steps:
1. Go to Device Manager > Disk drives.
2. Right-click and select Scan for hardware changes.
Problem: In an SVSP environment the host does not list the MPIO devices in Device Manager when
the backend LUN is unpresented and then presented back to the host after a long time interval. (The
backend LUNs could have been unpresented either for maintenance or if the backend LUN is removed)
Solution: After the backend LUN is presented back to the system, do one of the following:
• Reboot the system.
• Disable all the HBA ports and enable them back.
Problem: On changing the existing LUN number from the Virtualization Services Manager (VSM), the
new LUN number is not reflected in the disk management.
Solution: The change in LUN number not reflecting for the device does not have any functional impact.
To get the updated LUN number, do one of the following:
• Reboot the system
• Disable all the HBA ports and enable them back.
— Troubleshooting44