Rshexec: cannot connect to node NODE1

rshexec cannot connect to node NODE1

rshexec: cannot connect to node NODE1

* Normally this kind of error we are facing at the time of HACMP Cluster synchronize.

* If suppose we are not resolving this issue, cluster resource groups will be going to error mode.

* We will not able to solve the error resource groups.

Error Message:

NODE1:# smitty hacmp 
           -> Extended Configuration 
	      -> Extended Verification and Synchronization

rshexec: cannot connect to node NODE1
Could not run clfilecollection -u on node NODE1.
rshexec: cannot connect to node NODE2
Could not run clfilecollection -u on node NODE2.

Verification has completed normally.
rshexec: cannot connect to node NODE1
ERROR: Cannot refresh clcomdES subsystem on node NODE1rshexec: cannot connect to node NODE2
ERROR: Cannot refresh clcomdES subsystem on node NODE2

Problem Identification:

* Actually Problem is related to Cluster nodes intercommunication.

* At the time of Cluster nodes Creation we did mistake over there.

* For example if you are having two node HACMP cluster.

* Manually configuring /etc/hosts file on cluster individual nodes

NODE1+NODE2:# cat /etc/hosts
192.168.1.1 NODE1
192.168.1.2 NODE2
10.10.10.1 NODE1BOOT
10.10.10.2 NODE2BOOT
192.168.1.100 NODESVC

* Manually configuring /usr/es/sbin/cluster/etc/rhosts file on cluster individual nodes

NODE1+NODE2:# cat /usr/es/sbin/cluster/etc/rhosts
192.168.1.1
192.168.1.2
10.10.10.1 
10.10.10.2
192.168.1.100

* We have to mention our persistent hostname is our cluster node name. and choose nodes communication path is your persistent IP Address for each nodes.

* But by default we are choosing nodes boot IP Address for cluster nodes communication interface.

* Actually this is wrong. but our cluster will work why because boot IP address pinging to each other.

* Problem is We will not able to perform HACMP cluster topology Verification and synchronization.

* We are getting “rshexec: cannot connect to node NODE1” Error at the moment of cluster Verification.

Solution for the Problem:

* At the time of HACMP cluster nodes configuration mention system persistent host name is your cluster node name and communication path is your persistent IP address.

For HACMP Cluster NODE1 configuration:

NODE1# smitty hacmp 
-> Extended Configuration 
  -> Extended Topology Configuration 
     -> Configure HACMP Nodes
	 Node Name                   : NODE1 ----> NODE1 Persistent system hostname
	 Communication Path to Node  : 192.168.1.1[NODE1]----> NODE1 Persistent system IP Address

For HACMP Cluster NODE2 Configuration:

NODE1# smitty hacmp 
-> Extended Configuration 
  -> Extended Topology Configuration 
     -> Configure HACMP Nodes
	 Node Name                   : NODE2 ---> NODE2 Persistent system hostname
	 Communication Path to Node  : 192.168.1.2[NODE2] ---> NODE2 Persistent system IP Address

* Again verify and synchronize the cluster from primary node, problem will be resolved.

NODE1:# smitty hacmp 
           -> Extended Configuration 
	      -> Extended Verification and Synchronization

Result:

* rshexec: cannot connect to node NODE1 prebloem has been resolved as per our instruction.

 

Related posts

2 Thoughts to “Rshexec: cannot connect to node NODE1”

  1. Marek

    hello,
    you must have made a typo – both nodes have same IP

    192.168.1.1 NODE1
    192.168.1.1 NODE2

    1. Hi

      Some typing mistake. error corrected.

      192.168.1.1 NODE1
      192.168.1.2 NODE2

Leave a Comment