The Problem and Solution of cmquerycl under the dual-machine HP-UX

When configuring dual-host, perform the dual-host environment check first:

 

# Cmquerycl-N hlrdb1-N hlrdb2-v-C
/Etc/cmcluster/clhlrdb. ASCII

 

Begin checking the nodes...
Warning:
Unable to determine local domain name for hlrdb1
Looking for other
Clusters... Done
Gathering configuration information ..
Gathering
Storage information ..
Found 10 devices on node hlrdb1
Found 16
Devices on node hlrdb2
Analysis of 26 devices shocould take
Approximately 4 seconds
0% ---- 10% ---- 20% ---- 30% ---- 40% ---- 50% ---- 60% ---- 70% ---- 80% ---- 90% ---- 100% ----
Found
3 Volume groups on node hlrdb1
Found 3 Volume groups on node hlrdb2
Analysis
Of 6 volume groups shocould take approximately 1 seconds
0% ---- 10% ---- 20% ---- 30% ---- 40% ---- 50% ---- 60% ---- 70% ---- 80% ---- 90% ---- 100% ----
.....
Gathering
Network Configuration...
Note: disks were discovered which
Are not in use by either LVM or ESX.
Use pvcreate (1 m)
Initialize a disk for LVM or,
Use vxdiskadm (1 m) to initialize
Disk for ESX.
Warning: volume group/dev/vg00 is configured
Differently on node hlrdb1 than on
Node hlrdb2
Error: volume
Group/dev/vg00 on node hlrdb2 does not appear to have a physical
Volume
Corresponding to/dev/DSK/c2t1d0 on node hlrdb1 (24142709971117077841 ).
Warning:
Volume group/dev/vg00 is configured differently on node hlrdb2 than on
Node
Hlrdb1
Error: volume group/dev/vg00 on node hlrdb1 does not appear
To have a physical
Volume corresponding to/dev/DSK/c2t1d0 on Node
Hlrdb2 (24142709991117033934 ).
Warning: The volume group/dev/vg00 is
Activated on more than one node:
Hlrdb1
Hlrdb2
Warning: volume
Groups shoshould not be activated on more than one node.
Use vgchange
To de-activate a volume group on a node.
Failed to gather
Configuration information.

The dual-machine check fails and the configuration cannot be continued.

 

Google results, online posts
As follows:

Http://forums1.itrc.hp.com/service/foru...threadId=657218

 

Abstract
Reason:

When a volume group is created, it is given a unique vgid-
A merger of
Servers 'machine ID (uname-I) and the timestamp
The VG creation date.
Save time, administrators may have used dd
Or copyutil to clone
Vg00 onto another servers 'disks. Unfortunately,
This also copies the same
Vgid to the new server.

MC/serviceguard
Utilizes LVM structures such as volume group ID (vgid) and
Physical
Volume ID (PVID) to determine which vgs are shared (common to both
Servers ).
If each servers 'vg00s' PVID and vgid are the same, cmquerycl
(Serviceguard)
Considers them to be the same VG. subsequent alterations
Vg00 LVM
Structures (such as adding a disk) are interpretted by cmquerycl
Unresolvable
LVM differences between servers-terminating the command.

 

Which probably means
The dual-host uses the vgid and PVID to determine whether the VG is a shared disk. When the dual-host vg00 is located on a cloned hard disk, a problem occurs because the PVID is consistent.

 

Solution:
Below:

0. Run lvlnboot-V/dev/vg00 to save the execution result.

1. Start to LVM maintenance mode
# Shutdown
-Ry 0
Isl> HPUX-LM

2. Export vg00 and save the configuration
Vgexport-V
-M vg00.map/dev/vg00

3. Modify the vgid. If the image has been created, specify
Vgchgid-F
/Dev/rdsk/c2t0d0/dev/rdsk/c2t1d0
Enter 'y'

4. re-import VG

Mkdir/dev/vg00
Mknod/dev/vg00/group C 64 0 0x000000
Vgimport
-V-M vg00.map/dev/vg00/dev/rdsk/c2t0d0/dev/rdsk/c2t1d0

5. Modify LVM
Boot Zone
Vgchange-A y vg00
Lvlnboot-B/dev/vg00/lvol1

Lvlnboot-r/dev/vg00/lvol3
Lvlnboot-S/dev/vg00/lvol2

Lvlnboot-D/dev/vg00/lvol2
Lvlnboot-r/dev/vg00
Run lvlnboot
-V/dev/vg00, which is the same as the execution result in step 1.

6. Modify the default LVM boot command
Mount/usr

Lifcp/dev/rdsk/c2t0d0: auto-
Lifcp/dev/rdsk/c2t0d0: auto-

If the output result of the above two commands is not "HPUX", execute the following command to modify
Mkboot-a "HPUX"
/Dev/rdsk/c2tyd0

7. Restart
Shutdown-ry 0