6.Run the package on a node in the Serviceguard cluster.

#cmrunpkg -n <node_name> <package_name>

7.Enable global switching for the package.

#cmmodpkg -e <package_name>

Checking the Metrocluster Package Configuration

Starting from HP Serviceguard version A.11.20, the cmcheckconf -vcommand validates the cluster and the package configuration. Starting from the April 2011 patch release, Metrolcuster uses this functionality to ensure the sanity of Metrocluster and the Site Controller package configuration. HP recommends you to set up a cron job to run the cmcheckconf command regularly. For more information about setting the cron job, see Setting up Periodic Cluster Verification section in the latest version of the Managing Serviceguard manual available at http://www.hp.com/ go/hpux-serviceguard-docs —> HP Serviceguard.

“Validating Metrocluster Package” (page 242) lists the checks made on a Metrocluster Package when the Metrocluster module is integrated with a Site Controller package.

Table 20 Validating Metrocluster Package

Validations/Checks

Command

Remark

 

 

 

Check whether the Array Management

cmcheckconf [–v]

For Metrocluster with Continuous Access

Software is available.

cmapplyconf

EVA, it checks whether the HP

 

Command View EVA server is

 

 

 

cmcheckconf [-P/-p]

accessible from the nodes.

 

 

 

Check whether the contents in the

cmcheckconf [-v]

 

environment file matches with the

 

 

contents in the package present in the

 

 

CDB.

 

 

 

 

 

Check all attributes in the Metrocluster

cmcheckconf [–v]

Checks the package configuration file

module.

cmapplyconf

that is passed as an argument for the

 

cmcheckconf [-P/-p] command.

 

cmcheckconf [-P/-p]

 

For cmcheckconf, it checks the

 

 

Metrocluster environment file that is

 

 

available in the Metrocluster package

 

 

directory.

 

 

 

Verify if the disks belonging to a

cmcheckconf [–v]

Warns you if the disks belonging to a

volume group or a disk group are

cmapplyconf

volume group or a diskgroup are not

being replicated. **

being replicated. It reports and error if

 

 

cmcheckconf [-P/-p]

the disks belong to a different

 

 

replication group than what is

 

 

mentioned in the environment file or the

 

 

package configuration file.

 

 

When Metrocluster is integrated with

 

 

Site Controller, this check is done only

 

 

when the cmcheckconf [-v]

 

 

command is executed. During

 

 

validation, it creates a list of volume

 

 

groups and diskgroups for all the

 

 

packages controlled by Site Controller

 

 

and does the above check.

 

 

Restrictions

 

 

Cannot confirm if the disks are being

 

 

replicated in case they are being used

 

 

as raw disks or in case they belong to

 

 

an Oracle ASM diskgroup.

 

 

Skips this check on VxVM diskgroups

 

 

if the naming convention used by VxVM

 

 

is legacy and if the controller ID is

 

 

 

242 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA