HP P6000 Cluster Extension Software Administrator Guide (5697-2274, November 2012)

customized P6000 Cluster Extension Parameters tab. For more information about the Properties
tab, see “Setting P6000 Cluster Extension resource properties using the MMC” (page 32).
• When you install P6000 Cluster Extension into a Windows Server 2008/2008 R2/2012
environment, the resource extension DLL is registered by default, which prevents you from
configuring a P6000 Cluster Extension resource from a remote management station. If you
need to remotely configure a P6000 Cluster Extension resource in a Windows Server
2008/2008 R2/2012-based cluster, unregister clxevamscsex.dll from the cluster node,
which allows you to configure the P6000 Cluster Extension resource using the standard
Microsoft Properties tab. Use the command cluster
/UNREGADMINEXT:clxevamscsex.dll to unregister the DLL.
Powershell cmdlets can also be used instead of cluster.exe to unregister
clxevamscsex.dll. For more information, see Microsoft documentation.
CAUTION: Configuring P6000 Cluster Extension resources using the MMC from a remote
management station is supported using only the standard Microsoft Properties tab. Do not try
to use the customized P6000 Cluster Extension Parameters tab for this purpose.
• 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
/UNREGADMINEXT: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/2012 cluster nodes.
Powershell cmdlets can also be used instead of cluster.exe to unregister
clxevamscsex.dll. For more information, see Microsoft documentation.
• 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.
40 Configuring P6000 Cluster Extension