Installing HP 3PAR InForm Command Line Interface (CLI)
HP 3PAR Cluster Extension communicates with the HP 3PAR storage system using the HP 3PAR InForm Command Line Interface (CLI). Ensure that you install the supported version of HP 3PAR Command Line Interface (CLI) on a host where clx3PARrun can be used.
Creating and configuring the user configuration file
The CLI expects as an argument the name configured as the APPLICATION tag value.
The following is an example of a customized user configuration file when using clx3PARrun:
#
COMMON
#LogLevel info # errorinfo default: error (optional)
#The APPLICATION part defines failover information for the application
#specified as value of the APPLICATION tag.
#For example, the command - clx3PARrun CLXTEST1 — will use the below
#settings to check and allow access to the disk set specified as volume
#Group CLX_VGTEST1. Example includes similar kind of settings for another
#cluster group CLXTEST2.
#Necessary object when clx3PARrun is used are:
#APPLICATION, DC_A_InServStorage_SerNum, DC_B_InServStorage_SerNum,
#RCVolumeGroupA, RCVolumeGroupB, DC_A_Hosts and DC_B_Hosts
#APPLICATION CLXTEST1 | # package/service/cluster group test_application | |
#DC_A_InServStorage_SerNum | 1302871 # 1302871 is the data | center A HP 3PAR |
array serial number |
|
|
#DC_B_InServStorage_SerNum | 1302835 # 1302835 is the data | center B HP 3PAR |
array serial number |
|
|
#RCVolumeGroupA | CLX_VGTEST1 # CLX_VGTEST1 is the | data center A |
HP 3PAR Remote Copy volume group name |
| |
#RCVolumeGroupB | CLX_VGTEST1.r2835 # CLX_VGTEST1.r2835 is the data | |
center B HP 3PAR Remote Copy volume group name |
| |
#DC_A_Hosts clx_node1 clx_node2 # clx_node1, clx_node2 are data | centre A cluster | |
nodes |
|
|
#DC_B_Hosts clx_node3 clx_node4 # clx_node3, clx_node4 are data | centre B cluster | |
nodes
#ApplicationStartup fastfailback # values: fastfailback resyncwait
#UseNonCurrentDataOk yes # values: yes no #Default value is yes which causes the failover operation to succeed at the destination site when the data at the destination site might not be current. On setting the value to No the resource will not come online at the destination site since the data might not be current.
#APPLICATION CLXTEST2 | # package/service/cluster group test_application | ||
#DC_A_InServStorage_SerNum | 1302871 | # 1302871 | is the data center A HP 3PAR |
array serial number |
|
|
|
#DC_B_InServStorage_SerNum | 1302835 | # 1302835 | is the data center B HP 3PAR |
array serial number |
|
|
|
#RCVolumeGroupA | CLX_VGTEST2 # CLX_VGTEST2 is the data center A | ||
HP 3PAR Remote Copy volume group name |
|
| |
#RCVolumeGroupB | CLX_VGTEST2.r2835 # CLX_VGTEST2.r2835 is the data | ||
center B HP 3PAR Remote Copy volume group name
#DC_A_Hosts clx_node1 clx_node2 # clx_node1, clx_node2 are data centre A cluster nodes
#DC_B_Hosts clx_node3 clx_node4 # clx_node3, clx_node4 are data centre B cluster nodes
#ApplicationStartup resyncwait # values: fastfailback resyncwait
#UseNonCurrentDataOk yes # values: yes no #Default value is yes which causes the failover operation to succeed at the destination site when the data at the destination site might not be current. On setting the value to No the resource will not come online at the destination site since the data might not be current.
Timing considerations
HP 3PAR Cluster Extension gives priority to storage system operations over cluster software operations. If HP 3PAR Cluster Extension is invoked at the point when virtual volumes of Remote Copy volume group are in resynchronization or full synchronization operation or is gathering information about the remote storage system, it waits until the requested status information is reported. This ensures the priority of data integrity over cluster software failover behavior. Because the failover timing depends on the configuration of your Remote Copy environment, load on the
Configuring the CLI 57