HP StorageWorks SAN Virtualization Services Platform administrator guide (5697-8056, March 2009)

Corrective actionProblem
Check the VSM monitor status tab to see if the VSM
is running with local setup.
• Local setup means that the virtual disks containing
the setup database were not located on startup
and that the system started with a local (blank)
database.
• Verify zoning and LUN masking.
• Verify that the VSM is connected to the Fibre
Channel switch, and there are link lights on the
HBA or switch port.
• Check the VSM Monitor Recovery tab to identify
if any recovery steps are needed. Use VSM safe
mode to:
• Recover startup data from backup.
• Recover from a corrupted setup database.
The VSM is active but does not see pools, virtual disks,
and so on.
Configuration problems
Table 11 Configuration problems
Corrective actionProblem
Minimize the VSM client window and then maximize
the window. The GUI should appear. This may also
occur if the display resolution does not match that of
the server.
After rebooting the VSM server, a dull grey-green
screen appears, but nothing else happens.
• Verify that a VSM license is installed. License keys
are tied to the IP address of the VSM. If the VSM
IP address changes, uninstall the licenses and rein-
stall from the original license files.
• Verify that the license capacity has not been ex-
ceeded.
Storage pool cannot be created.
• Verify that there is adequate free space in the pool.
• Verify that the pool is in a normal status. Missing
EVA or MSA virtual disks can cause a volume
creation failure.
• Verify the presented capacity is available.
• Verify that the license capacity has not been ex-
ceeded.
• Check the Disabled Operations tab on the pool
for a potential cause.
Cannot create a new virtual disk.
Check the disabled operations tab on the virtual disk.
This lists what operations are disabled and why.
Cannot delete a virtual disk.
• Check the VSM event log for failover messages to
determine which server requested the failover.
• Review the server event logs for I/O failures that
would cause a virtual disk failover.
The virtual disk is running on the secondary DPM.
Basic troubleshooting90