
Checking the Metrocluster Configuration
Starting from HP Serviceguard version A.11.20, the cmcheckconf
“Validating Metrocluster Package” (page 189) lists the checks made on a Metrocluster Package.
Table 17 Validating Metrocluster Package
Validations/Checks | Command | Remark | |
|
|
| |
Check whether the Array Management | cmcheckconf | For Metrocluster with Continuous Access | |
Software is available. | cmapplyconf | for P9000 and XP, It checks whether | |
| the Raid Manager is installed. | ||
| cmcheckconf | ||
|
| ||
|
|
| |
Check whether the contents in the | cmcheckconf |
| |
environment file matches with the |
|
| |
contents in the package present in the |
|
| |
CDB. |
|
| |
|
|
| |
Check all attributes in the Metrocluster | cmcheckconf | Checks the package configuration file | |
module. | cmapplyconf | that is passed as an argument for the | |
| cmcheckconf | ||
| cmcheckconf | ||
| For cmcheckconf, it checks the | ||
|
| Metrocluster environment file that is | |
|
| available in the Metrocluster package | |
|
| directory. | |
|
|
| |
Verify if the disks belonging to a | cmcheckconf | 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 | 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 | |
|
| 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 | |
|
| greater than 512 (This happens when | |
|
| VxVM uses an internal format to | |
|
| recognize devices that do not support | |
|
| legacy dsf format). Also skips the check | |
|
| if the naming convention is enclosure | |
|
| based. In such cases, it is | |
|
| recommended that you change the | |
|
| naming scheme using the vxddladm | |
|
| command so that VxVM output shows | |
|
|
|
Configuring Modular Packages 189