HP P6000 Cluster Extension Software Administrator Guide (5697-0986, June 2011)

Example 2 This example assumes you have defined an APPLICATION tag named my-
exchange in the UCF.cfg file and have specified all necessary objects,
including the DeviceGroup object, to map the DR group to the application
service my-exchange. P6000 Cluster Extension will check the vdisk set
mapped to the application service my-exchange, and run the necessary
failover procedure to enable read/write access to the vdisks.
# clxevarun -forceflag my-exchange
Related information clxevarun expects only the app_name parameter, which uniquely
identifies an application service in the APPLICATION section of the user
configuration file.
•
• To force a DR group failover, use the –forceflag option. When using
clxevarun, the –forceflag option is used instead of
app_name.forceflag, which is only used with the non-CLI version of
P6000 Cluster Extension.
CAUTION:
The forceflag option is an emergency switch used to
manually activate your vdisk. If the forceflag option has
been specified, P6000 Cluster Extension will not check any
consistency or concurrency rules before activating the vdisk in
the associated DR group.
Return codes clxevarun exits with one of the following return codes:
OK Application service can be started.
0
ERROR_GLOBAL Application service could not start on any node in either
site on either P6000/EVA storage system.
1
ERROR_DC Application service could not start on any node in the local site
on the local P6000/EVA storage system.
2
ERROR_LOCAL Application service could not start on this node.
3
Configuring the CLI
The following configuration steps are required before using the P6000 Cluster Extension CLI:
1. Creating the Continuous Access EVA environment, page 89
2. Installing and configuring HP SMI-S EVA server, page 89
3. Configuring the HP EVA storage system, page 89
4. Creating and configuring the user configuration file, page 89
CLI commands and utilities88