cmviewcl displays incorrect status for package before TOC'ed

[Tomoko Onishi]

Hi all,

I'm running SG 11.15 on HPUX 11i and I have a 1 package 2 node cluster.

After I have killed cmcld deamon on a standby node,
I happened to notice that the status of package of cmviewcl was 'down' before TOC'ed,
though the package on a primary node was always up normally.

------------------------------------------
host001:root> cmviewcl

CLUSTER STATUS
cls0001 up

NODE STATUS STATE
host001 up reforming
host002 down unknown

UNOWNED_PACKAGES

PACKAGE | STATUS | STATE | AUTO_RUN | NODE
pal_pkg01| down | | |unowned
-----------------------------------------

Is this incorrect status?

# After TOC'ed, the status of package became "up".

Regards,

[Karthik S S]

Hi,

Did you run cmviewcl on the node where you killed cmcld? If yes you may not get proper results as expected.

-Karthik S S

[Tomoko Onishi]

No. I killed cmcld on host002, and run cmviewcl on the other node(host001).

Tomoko

[Karthik S S]

Sounds like a patch issue. Have you installed the latest patches for SG11.15? Also make sure the patch revisions are same across the nodes.

One such cmviewcl behaviour is solved by the following patch,
http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.pdb|patch.breadcrumb.search|&patchid=PHSS_29067&context=hpux:800:11:23

Upload your system information in the following site using cpm_collect.sh and search for serviceguard as the keyword. Select relevant patches to you environment and install them on both the nodes

http://www1.itrc.hp.com/service/patch/searchBySystem.do?BC=patch.breadcrumb.main|patch.breadcrumb.pdb|

-Karthik S S

[melvyn burnard]

This is correct, as you can see that the cluster is reforming after the TOC. Also, as the primary node has TOC'ed, the package state is unowned, until the cluster reforms and the package manager restarts the package on the surviving node.

[Tomoko Onishi]

I also doubted the patch, but PHSS_30087(for 11.11) has installed on both node.
I think this sympton differs from this patch description, because SERVICE_NAME and SERVICE_FAIL_FAST_ENABLED are not cofigured for this package.

[Tomoko Onishi]

Hi melvyn,

It's true the package state is unowned, but I thought the package STATUS should be "unknown" or "up" is correct.