cmcld: DLPI error!

[fuchs_2]

wenn i start the command cmviewcl, the cluster answers with the following message:
----------------------------------------------
cmviewcl : Cannot view the cluster configuration. Either this node is not configured in a cluster, or else there is some obstacle to viewing the configuration. Check the syslog file for more information. For a list of possible causes, see the ServiceGuard manual for cmviewcl.
----------------------------------------------

the syslog gives me the following information:
----------------------------------------------
Dec 25 19:01:08 PHVNP12 cmcld: DLPI error! dl_errno: 1, dl_unix_errno: 0
Dec 25 19:01:09 PHVNP12 cmcld: Failed to send to 0x00306e25195aaa080009167e on net_id 3
Dec 25 19:01:10 PHVNP12 cmcld: Failed to send to 0x00306e251952aa080009167e on net_id 4
Dec 25 19:01:10 PHVNP12 cmcld: DLPI error! dl_errno: 1, dl_unix_errno: 0
-----------------------------------------------

the sap-instance is reachable, but i don´t think that this is a good start for the week. any suggestions?

[T G Manikandan]

There is a fix for this.

What version are you running for serviceGuard

[T G Manikandan]

11.09 PHSS_26338
11.13 PHSS_26674
11.14 PHSS_26056,

This is fixed in A11.15

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3935-90063/B3935-90063_top.html&con=/hpux/onlinedocs/B3935-90063/00/00/9-con.html&toc=/hpux/onlinedocs/B3935-90063/00/00/9-toc.html&searchterms=dl_unix_errno&queryid=20031219-010923

[melvyn burnard]

yoiu appear to have a networking problem.
I would suggest you run the cmscancl command and read through the output file, to check whether all your networks can talk to each other as you expect.
You may also want to patch your version of SG, depending on which version you are running.
do:
what /usr/lbin/cmcld to find out what version, and what patch level, you are running.

[fuchs_2]

hallo!

we use the following version of mc/sg: A.11.13

and there ist noone of the patches installed, which you have listed.

[melvyn burnard]

One question to ask, is hte cluster up and running?
Did you get a node TOC'ing when you got the mesages?
If not, this has nothing to do with the fix mentioned in the patches or newer rlease of SG, as that issue would cause a TOC.
I suspect you have some networking connectivity issue. check you can linkloop between the various network cards, run cmscancl to do htis automatically, and review hte resultant log file.

[T G Manikandan]

here is the latest patch

http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHSS_28849&context=hpux:800:11:11


http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHSS_26674&context=hpux:800:11:11

[fuchs_2]

well the tip with the cmscancl returned the following result:

[root@PHVNP12][/root_home]# cmscancl
cmviewconf: Binary file does not exist.

cmscancl: Unable to obtain node names from [root@PHVNP12][/root_home]# cmviewconf
cmviewconf: Binary file does not exist.



which file does the machine miss? /etc/cmcluster/cmclconfig and all necessary file in the package-dir are available?

[fuchs_2]

One question to ask, is hte cluster up and running?

--> the cluster is up and running! the output of the second node (which is the dialog-instance at the moment) is as usual:

[root@BHVNP15][/etc/cmcluster]# cmviewcl -v -p PO9

PACKAGE STATUS STATE AUTO_RUN NODE
PO9 up running enabled PHVNP12

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled PHVNP12 (current)
Alternate up enabled BHVNP15

PHVNP12 is the node with the problems.
the answer of cmviewcl appears after 20 sec (whihc is to long, but not so long as if the second clusternode will be down)


Did you get a node TOC'ing when you got the mesages?

---> no - there was no TOC.

If not, this has nothing to do with the fix mentioned in the patches or newer rlease of SG, as that issue would cause a TOC.
I suspect you have some networking connectivity issue. check you can linkloop between the various network cards, run cmscancl to do htis automatically, and review hte resultant log file.

---> cmscancl will not work, but i try the linkloop.

[fuchs_2]

a hanging cmclconfd was the problem. this process occupied the file /etc/cmcluster und don´t gave it free. so the cmviewcl and the other command failed.

thats what i can say at the first momen