problem while adding new node in cluster

[Fenny_1]

Hi All,
we are facing this error, while adding new node in an existing cluster. Name resolution is working fine on all nodes. but still we are facing this error.
# cmcheckconf -v -k -C staging.ascii

Checking cluster file: staging.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Warning: Unable to get configuration for cluster staging.
Error: Node tppora50 is refusing Serviceguard communication.
Please make sure that the proper security access is configured on node
tppora50 through either file-based access (pre-A.11.16 version) or role-based
access (version A.11.16 or higher) and/or that the host name lookup
on node tppora50 resolves the IP address correctly.
cmcheckconf : Failed to gather configuration information

[Duncan Edmonstone · Accepted solution]

Hi,

I would advise you to carefully read and understand these 2 white papers:

http://docs.hp.com/en/6283/SGsecurityfiles.pdf

http://docs.hp.com/en/5874/securingserviceguard_nov2005.pdf

HTH

Duncan

[Fenny_1]

Hi,

I've already gone through those documents. I've checked security settings and host connectivity multiple times. but im still getting this error.

[skt_skt]

are the servers are in the same patch levels?

check this too first or its equivalent.

PHSS_34759 1.0 Serviceguard A.11.16.00
PHSS_32732 1.0 COM B.03.00.00

[Stephen Doud]

Several causes exist.

1) If this is a new cluster creation (version A.11.16 or later), insure
/etc/cmcluster/cmclnodelist has been created on every node in the cluster.
The file format is akin to .rhosts. Example:

tic root
toc root

or use IP-based handles to expedite the authentication function. Eg:

16.113.32.42 root
16.113.32.43 root

NOTE: EVERY node must be listed in every cmclnodelist!

--------------------------------------------------------------------------------
2) The error occured because an old cluster binary file existed on the other
node and there was no cluster binary on the node where the configuration
command was executed. Removing the invalid cluster binary file permitted
the cmapplyconf to operate.

--------------------------------------------------------------------------------
3) In another case, the identd service was not enabled in /etc/inetd.conf.
# grep ident /etc/inetd.conf
#auth stream tcp6 wait bin /usr/lbin/identd identd

Removing the "#" comment and running 'inetd -c' cleared the condition.

[Fenny_1]

Hi All,
Problem is resolved, Thanks for everyone's help