HP-UX双机下使用cmquerycl遇到的问题和解决方法

在配置双机时，先进行双机环境检查：

 

# 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 should 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 should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
.....
Gathering Network Configuration ....... Done
Note: Disks were discovered which are not in use by either LVM or VxVM.
      Use pvcreate(1M) to initialize a disk for LVM or,
      use vxdiskadm(1M) to initialize a disk for VxVM.
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 should not be activated on more than one node.
Use vgchange to de-activate a volume group on a node.
Failed to gather configuration information.

至此双机检查没有通过，无法继续配置。

 

Google的结果，网上帖子 如下：

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

 

摘 录一下原因：

When a volume group is created, it is given a unique VGID - a merger of the
servers' machine ID (uname -i) and the timestamp of the VG creation date. To
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 of
vg00 LVM structures (such as adding a disk) are interpretted by cmquerycl as
unresolvable LVM differences between servers - terminating the command.

 

大概的意思是 双机以VGID和PVID来确定vg是否是共享盘；在双机的vg00所在硬盘克隆的情况下，由于PVID一致，就会出现问题。

 

解决方法如 下：

0. 执行lvlnboot -v /dev/vg00，保存执行结果

1. 启动到LVM维护模式
   #shutdown -ry 0
   ISL>hpux -lm

2. export vg00,并保存配置
   vgexport -v -m vg00.map /dev/vg00

3. 修改vgid，如果已经作了镜像，两块盘要同时指定
   vgchgid -f /dev/rdsk/c2t0d0 /dev/rdsk/c2t1d0
   输入‘y'

4. 重新import vg
   mkdir /dev/vg00
   mknod /dev/vg00/group c 64 0x000000
   vgimport -v -m vg00.map /dev/vg00 /dev/rdsk/c2t0d0 /dev/rdsk/c2t1d0

5. 修改LVM boot区
   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
   执行lvlnboot -v /dev/vg00，与第0步执行结果比较，应该相同

6. 修改LVM缺省的boot命令
   mount /usr
   lifcp /dev/rdsk/c2t0d0:AUTO -
   lifcp /dev/rdsk/c2t0d0:AUTO -
   上面两条命令的输出结果如果不是“hpux”，则执行下面的命令修改
   mkboot -a "hpux" /dev/rdsk/c2tYd0

7. 重启
   shutdown -ry 0