Operating System - HP-UX
1837097 Members
2168 Online
110112 Solutions
New Discussion

cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

 
boomerang
Frequent Advisor

cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

Hi Admins,

I am getting below error message while i am trying join the node "SP01" to cluster .Please advice


root@SP01:/>cmrunnode -v SP01

cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

cmrunnode: In order to use cmrunnode, the cluster must already be running on a subset of reachable nodes or else all cluster nodes must be reachable.

cmrunnode: Issuing cmrunnode again may succeed.
7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

Shalom,

cmviewcl -v

Lets see if the cluster is running at all.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
boomerang
Frequent Advisor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

This cluster is with 2 nodes SP01 and SP02 .I am not able to ping to HEARTBEAT_IP: 10.11.7.146(of SP01) from node SP02.But can ping the HEARTBEAT_IP:10.11.4.139(of SP01) from node SP02.

Please see the below configuration and advice ,what can be the possible reasons because of which i cannot ping the heart beat IP.



NODE_NAME SP01
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.11.7.146
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.11.4.139
NETWORK_INTERFACE lan3
FIRST_CLUSTER_LOCK_PV /dev/dsk/c10t3d4
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE /dev/tty0p0

# Possible standby Network Interfaces for lan0: lan1.
# Possible standby Network Interfaces for lan2: lan3.

NODE_NAME SP02
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.11.7.147
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.11.4.140
NETWORK_INTERFACE lan3
FIRST_CLUSTER_LOCK_PV /dev/dsk/c10t3d4
boomerang
Frequent Advisor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

root@SP01:/tmp>cmviewcl

CLUSTER STATUS
CMSCLUSTER unknown

NODE STATUS STATE
SP01 down unknown
SP02 unknown unknown

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 unknown unknown enabled unowned

root@SP02:/tmp>cmviewcl

CLUSTER STATUS
CMSCLUSTER up

NODE STATUS STATE
SP01 down halted
SP02 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running disabled SP02


Amitav
Frequent Advisor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

Did u add the entry of the new node on the cluster config file and complied it....??
Rita C Workman
Honored Contributor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

The node SP01 is down as far as the cluster was concerned...it shows that the pkg1 is now running on SP02. So it looks like maybe you had a failover.

Now you appear to be on SP01, so the box is not truly down. But, again, as far as the cluster is concerned - it is.

Possibly, your heartbeat connection went out, so the cluster complained. You may need to address SP01 heartbeat. Might be a bad cable or a lose cable.

Rgrds,
Rita




Horia Chirculescu
Honored Contributor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

What do you get on SP01 when issuing:

cmruncl -n SP01 -v

How about syslog.conf?

Horia.
Best regards from Romania,
Horia.
boomerang
Frequent Advisor

Re: cmrunnode: Unable to communicate with a running cluster or with all nodes in the cluster.

Hi All,

Issue resolved,Actually our network guy by mistake disabled the port on switch to which our HP box was connected.After enabling the same I was able to add the node to cluster.

Thanks for your time and suggestions.