only if you installed the latest APARs which are released recently for hacmp 5.2 in aix 5.3 env.

i have been told that is a bug for hacmp 5.2 in aix 5.3 OS when installed the latest apars if hdiskhb is being used as heartbeat device.
user could just ignor this messages and go on.

what a shame!

thanks,

Frank

As this concerns diskhb networking, there are a number of things to check.

First of all, simply try removing the diskhb net as a non-IP network and see if the verify runs, except that it may complain about a missing nonIP network.

For the nonIP network to work you need to be sure you have the latest rsct filesets installed. Further, you need to verify that the volume groups are extended concurrent capable.

If the above is true you should be able to do lsvg on both nodes. One node will be active and read/write, the other will be varyon but in passive (read-only of the VGDA, LVCB, etc.). If this is not happening (only varyon on one node, or no longer showing up as concurrent enabled, the diskhb will not work.

I"ll try to get some more research done - but others probably have suggestions too (I have a couple of days off so I may just not be commenting for a few days).

In short: two tests) HACMP without diskhb network (if it works then, and doesnt after setting it on again then at least we know where to look. If HACMP is still acting weird, then at least diskhb can no mask the real problem.)

hi all



we have tow nodes hacmp 5.2 cluster which was working well before i migrated OS from aix 5.2 to aix 5.3. i tested the failover/takeover last night and it did not work anymore. in the mean time, i found that IBM just released the newest apars for hacmp 5.2 recently and installed them into those clustered nodes. after reboot and synching the ha, more errors came out. it complianed that the heartbeatline device ( a disk device) was reserved and could not gain any shared vg info from both nodes. i did try to read and write the heartbeatline device through commands - A: dhb_read -p hdisk4 -r B: dhb_read -p hdisk4 -t. it works fine. what else should i check?




the error message as the following.



Verification to be performed on the following:
    Cluster Topology
    Cluster Resources

Verification will automatically correct verification errors.


Retrieving data from available cluster nodes.  This could take a few minutes.......

Verifying Cluster Topology...

WARNING: ONHNAP: Read on disk /dev/hdisk4 failed.
  Check cables and connections.
  A reserve may be set on that disk by another node.

WARNING: ONHNAT: Read on disk /dev/hdisk4 failed.
  Check cables and connections.
  A reserve may be set on that disk by another node.

WARNING: The mode of volume group mqmvg cannot be determined on node ONHNAP
WARNING: The mode of volume group mqmvg cannot be determined on node ONHNAT
WARNING: The mode of volume group cernervg cannot be determined on node ONHNAP
WARNING: The mode of volume group cernervg cannot be determined on node ONHNAT
WARNING: The mode of volume group oravg cannot be determined on node ONHNAP
WARNING: The mode of volume group oravg cannot be determined on node ONHNAT
WARNING: The mode of volume group prod2vg cannot be determined on node ONHNAP
WARNING: The mode of volume group prod2vg cannot be determined on node ONHNAT

Verifying Cluster Resources...

processing RG: ONHNAP_rg

Remember to redo automatic error notification if configuration has changed.
Updating ODM errnotify on node ONHNAP.
Updating ODM errnotify on node ONHNAT.

Verification has completed normally.