HP P6000 Cluster Extension Software Administrator Guide (5697-0986, June 2011)

• If you see the customized P6000 Cluster Extension Parameters tab when you try to configure a
P6000 Cluster Extension resource from a remote management station using the MMC, you must
unregister clxevamscsex.dll from the cluster node. Use the command cluster /UNREGAD-
MINEXT:clxevamscsex.dll to unregister the DLL. Unregistering the DLL allows you to configure
the resource using the standard Microsoft Properties tab. This situation might occur if you have a
cluster with both Server Core or Hyper-V Server and Windows Server 2008/2008 R2 cluster
nodes.
• When you configure P6000 Cluster Extension resource properties from a remote management
station through the MMC, which uses the standard Microsoft Properties tab, the properties you
enter are not validated, so you must enter the property values accurately, and verify them against
the P6000 Cluster Extension documentation.
System resources
Monitor the system resources on a regular basis as part of Windows administration. If any system
resource usage by the cluster service is reaching maximum levels, stop and then restart the cluster
service. This action automatically fails over the resources and resets system resources. See the MSCS
documentation for information about how to stop a cluster service.
An alternate method is to manually move all resources to another node in the cluster before stopping
the cluster service. After all resources are successfully moved to another node, stop and then restart
the cluster service; then, manually move back all resources.
Logs
If the P6000 Cluster Extension log files need to be cleared and reset (for example, to reduce disk
space usage), you can delete the files. P6000 Cluster Extension automatically creates new log files.
TIP:
Archive the log files before deleting them.
Hyper-V Live Migration log entries
In the P6000 Cluster Extension log file (clxevamscs.log), live migration messages include the
prefix CLX_LM to help you differentiate live migration issues from P6000 Cluster Extension log
messages.
For example:
[10/12/09 20:13:02][2136][CLX_LM: CLXVMDISK04-App01][INFO] CLX detected
that Live Migration for VM "Virtual Machine VM04" has begun.
[10/12/09 20:13:02][2136][CLX_LM: CLXVMDISK04-App01][INFO] CLX started
gathering VM "Virtual Machine VM04" specific storage information.
Configuring P6000 Cluster Extension for Windows54