HP StorageWorks XP Cluster Extension Software Administrator Guide (T1656-96035, April 2010)

4. Define the previously defined Custom Cluster Event release_vg_fs_pre as a pre-event of
release_vg_fs.
Timing considerations
XP Cluster Extension is designed to prefer XP disk array operations over cluster software operations.
If XP Cluster Extension invokes disk pair resynchronization operations or gathers information about
the remote XP disk array, XP Cluster Extension will wait until the requested status information is reported.
This assumption has been made to clearly prioritize data integrity over the cluster software's failover
behavior.
In some cases, however, this behavior could lead to an HACMP error event (config_too_long).
The default timeout value is 6 minutes. Use the chssys command to increase the timeout. For example:
#chssys -s clstrmgr -a "-u 60000"
NOTE:
You must stop the cluster to run the chssys command.
The described timeouts can occur in the following situations:
• XP Cluster Extension uses XP RAID Manager instances to communicate with the remote XP disk
array. Depending on the settings of the XP RAID Manager instance timeout parameter and the
number of remote instances, the online operation could time out. This can happen if the local XP
RAID Manager instance cannot reach the remote XP RAID Manager instance. See “Setting up XP
RAID Manager” on page 20 for more details.
• XP Cluster Extension tries to resynchronize disk pairs and waits until the XP RAID Manager device
group is in PAIR state if the ApplicationStartup attribute is set to RESYNCWAIT. Depending on the
XP RAID Manager version and the XP firmware version, this could be a full resynchronization,
which can take much longer than the online timeout interval. Even if the XP RAID Manager version
and the XP firmware version allow a delta resynchronization, the delta between the primary and
the secondary could be big enough for the copy process to exceed the online timeout value.
Configuring XP Cluster Extension for AIX34