HP 3PAR Cluster Extension Software Administrator Guide for Windows (5697-1821, April 2012)

• The value of the HP3PARCLICommandTimeout property must be less than the configured
resource PendingTimeout value.
• The value of HP3PARRCPeriodicLinkDownTimeout property should be set between 200 and
300 seconds based on the time taken by the remote copy to make the VG status to go to the
stopped state after the RC link is brought down.
In general, because the failover environment is dispersed into two (or more) data centers, the
failover time cannot be expected to be the same as that in a single data center with a single shared
disk device. Therefore, the following values of the HP 3PAR Cluster Extension resource and the
service or application using that resource, must be adjusted, based on failover tests performed to
verify the proper configuration setup: FailoverPeriod, RestartPeriod, PendingTimeout, LookAlive,
and IsAlive.
In addition, FailoverPeriod value of the service or application must be higher than the RestartPeriod
value of the resource and both must be higher than the resource's PendingTimeout value. Microsoft
Cluster provides two properties to adjust state change recognition or resolution:
• IsAlive
• LookAlive
NOTE: For Windows Server 2008/2008 R2, the IsAlive and LookAlive properties are replaced
by the Thorough Resource Health Check Interval and Basic Resource Health Check Interval
properties.
Bouncing service or application
HP 3PAR 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.
Creating array password file
HP 3PAR Cluster Extension uses HP 3PAR CLI commands to manage the HP 3PAR storage system
objects. HP 3PAR CLI can be installed on the client machine to manage the HP 3PAR storage
systems remotely. Each CLI session requires a user name and an encrypted password for successful
command execution. Alternatively, a onetime password file can be generated for subsequent use.
Generated password file is specific to the HP 3PAR storage system. However, it can be copied to
other systems for use. HP 3PAR Cluster extension requires this password file for its operations. For
each array managed by HP 3PAR Cluster Extension, appropriate password files must be generated
and configured during the HP 3PAR Cluster Extension configuration.
After you log into the HP 3PAR command shell (using the valid username and password credentials),
use following command to generate the password file:
setpassword -u <user name> -saveonly -file <file name>
The generated password file is stored in the directory from where the command shell is launched.
For example, if you use %HP 3PAR CLI PATH% to login to the command shell, the generated
password file location will be <HP 3PAR CLI PATH>\bin.
IMPORTANT: If there is any change in the configured IP address of the array or password file
location and content, Cluster Extension will fail to communicate with the array and will not perform
the required actions. At any point of time, you can launch the HP 3PAR Configuration tool and
use the Connection Test option to verify connectivity and array credentials, and take necessary
action.
Bouncing service or application 45