HP XP Cluster Extension Software Administrator Guide
MSFC provides two parameters to adjust state change recognition/resolution:
• IsAlive
• LookAlive
XP Cluster Extension automatically calls the IsAlive function whenever the cluster service calls the
LookAlive function. Therefore, both functions must be set to the same value.
Bouncing service or application
XP Cluster Extension will alternate (start and fail) between local nodes if the ApplicationStartup
property has been set to FASTFAILBACK and no remote system is available until the service or
application restart limit has been reached. For more information, see “ApplicationStartup” (page 51).
The FastFailbackEnabled property is not used by the XP Cluster Extension integration with MSFC.
Administration
XP Cluster Extension administration includes remote management of resources and monitoring of
system resources and logs.
Remote management of XP Cluster Extension resources in a cluster (Windows Server
2008/2008 R2/2012)
You can use the MMC with Failover Cluster Management to manage clusters and configure XP
Cluster Extension resources. Note the following when configuring XP Cluster Extension resources
by using the MMC from a remote management station:
• When you use the MMC to remotely configure XP Cluster Extension resource properties in a
Server Core or Hyper-V Server cluster node, the Failover Cluster Management GUI on the
remote management station displays the standard Microsoft Properties tab instead of the
customized XP Cluster Extension Parameters tab. For more information about the Properties
tab, see “Setting XP Cluster Extension resource properties using the MMC” (page 28).
• When you install XP Cluster Extension into a Windows Server 2008/2008 R2/2012
environment, the resource extension DLL is registered by default, which prevents you from
configuring XP Cluster Extension resource from a remote management station. If you need to
remotely configure XP Cluster Extension resource in a Windows Server 2008/2008 R2/
2012-based cluster, unregister clxmscsex.dll from the cluster node, which allows you to
configure the XP Cluster Extension resource using the standard Microsoft Properties tab. Use
the command cluster /UNREGADMINEXT:clxmscsex.dll to unregister the DLL.
Powershell cmdlets can also be used instead of cluster.exe to unregister clxmscsex.dll.
For more information, see Microsoft documentation.
CAUTION: Configuring XP 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 XP Cluster Extension Parameters tab for this purpose.
• If you see the customized XP Cluster Extension Parameters tab when you try to configure XP
Cluster Extension resource from a remote management station using the MMC, you must
unregister clxmscsex.dll from the cluster node. Use the command cluster
/UNREGADMINEXT:clxmscsex.dll to unregister the DLL. Unregistering the DLL allows you
to configure the resource using the standard Microsoft Properties tab. This situation might
Bouncing service or application 37