topic Re: Clustering Problem in Operating System - HP-UX

Clustering Problem

Mousa55 — Mon, 04 Jan 2010 07:40:29 GMT

Dear All,

I facing problem with make a new cluster on two node (rp8420, 11.11 for both) As described below.
===============
# cmquerycl -v -C cmclconfig.ascii -n ruxerp01 -n ruxdb02

Begin checking the nodes...
Error: Permission denied to 10.8.1.51
Warning: Unable to determine local domain name for ruxerp01
Looking for other clusters ... Done
Error: Node ruxdb02 is refusing Serviceguard communication.
Please make sure that the proper security access is configured on node
ruxdb02 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 ruxdb02 resolves the IP address correctly.
Failed to gather configuration information.
===============
I configured all required files As described in attached file. and i exporting and importing the vg01.map successfully and the VG is active in one node (primary)

How I can solving this problem.

Thanks and best regards

Re: Clustering Problem

johnsonpk — Mon, 04 Jan 2010 08:42:01 GMT

Are you able to rlogin from node 1 to node2 without password and vice versa ?

And also one entry per server in cmclnodelist would be enough

Rgds!
Johnson

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 08:43:43 GMT

Hi All,

i have 11.16 Serviceguard version and this all patch installed on both node

swlist -l product | grep -i guard
ATS-CORE A.11.16.00 Serviceguard Advanced Tape Services
PHKL_27532 1.0 ; ServiceGuard/vsar incompatibility removed
PHKL_28114 1.0 timeout; ServiceGuard TOC
PHSS_32731 1.0 Serviceguard A.11.16.00
SG-Apache-Tool B.02.20 Serviceguard Apache Script Templates
SG-Informix-Tool B.02.20 Serviceguard Informix Script Templates
SG-NFS-Tool A.11.11.05 Serviceguard NFS Script Templates
SG-Oracle-Tool B.02.20 Serviceguard Oracle Script Templates
SG-Progress-Tool B.02.20 Serviceguard Progress Script Templates
SG-Samba-Tool B.02.20 Serviceguard Samba Script Templates
SG-Sybase-Tool B.02.20 Serviceguard Sybase Script Templates
SG-Tomcat-Tool B.02.20 Serviceguard Tomcat Script Templates
ServiceGuard A.11.16.00 ServiceGuard

thanks

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 08:45:16 GMT

Hi,

yes i can rlogin without password in 2 node

thanks

Re: Clustering Problem

R.K. # — Mon, 04 Jan 2010 08:51:29 GMT

Hi Nejad,

You need to check following files and their format on both nodes:

/etc/cmcluster/cmclnodelist - must exist on both nodes and entries of both nodes should be present.
/etc/nsswitch.conf - files dns

What is :
# grep ident /etc/services
# grep ident /etc/inetd.conf

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 09:02:59 GMT

Hi All,

The /etc/cmcluster/cmclnodelist it is exist on both node.
but the /etc/nsswitch.conf it is availble on second node only and this file included
# more /etc/nsswitch.conf
#
# /etc/nsswitch.files:
#
# @(#)B.11.11_LR
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any name services.
#
passwd: files
group: files
hosts: files
services: files
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files

What is :
# grep ident /etc/inetd.conf
this will allow service to ignore the identd

thanks

Re: Clustering Problem

R.K. # — Mon, 04 Jan 2010 09:18:59 GMT

Hi Nejad,

Actually I wanted the output of following commands:

# grep ident /etc/services
# grep ident /etc/inetd.conf

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 09:29:18 GMT

Hi All,

on Node 1:

# grep ident /etc/services
ident 113/tcp authentication # RFC1413
# grep ident /etc/inetd.conf
auth stream tcp wait root /usr/lbin/identd identd

Node 2:

# grep ident /etc/services
ident 113/tcp authentication # RFC1413
# grep ident /etc/inetd.conf
auth stream tcp wait root /usr/lbin/identd identd

thanks

Re: Clustering Problem

R.K. # — Mon, 04 Jan 2010 09:43:23 GMT

Hi Nejad,

My server has following entries:

/etc/services:
ident 113/tcp auth tap # RFC 1413

/etc/inetd.conf:
ident stream tcp wait bin /usr/lbin/identd identd

Why not try changing auth --> ident....in inetd.conf.

then..
# inetd -c

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 09:54:02 GMT

Hi All,

the problem is still.

Begin checking the nodes...
Error: Permission denied to 10.8.1.51
Warning: Unable to determine local domain name for ruxerp01
Looking for other clusters ... Done
Error: Node ruxdb02 is refusing Serviceguard communication.
Please make sure that the proper security access is configured on node
ruxdb02 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 ruxdb02 resolves the IP address correctly.
Failed to gather configuration information.

# grep ident /etc/inetd.conf
ident stream tcp wait bin /usr/lbin/identd identd

thanks

Re: Clustering Problem

R.K. # — Mon, 04 Jan 2010 10:08:14 GMT

Hi Nejad,

Check following link....may be you can find something useful.

http://bizsupport1.austin.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3203314&prodTypeId=18964&objectID=c01680756

Re: Clustering Problem

Horia Chirculescu — Mon, 04 Jan 2010 11:37:45 GMT

Hello,

You should check also syslog.log on both nodes.

There should be some informations that you can use.

Best regards,
Horia.

Re: Clustering Problem

Mousa55 — Mon, 04 Jan 2010 11:48:39 GMT

Hi All,

No any important information in syslog.log file.
only this
"cmclconfd running with weak security (identd disabled)"

# grep ident /etc/inetd.conf
ident stream tcp wait bin /usr/lbin/identd identd

thanks

Re: Clustering Problem

Rita C Workman — Mon, 04 Jan 2010 14:30:46 GMT

What does your /etc/resolv.conf show?

Do reserve lookups (nslookup) on both boxes; One for the IP and one for the hostname. Report what comes up.

Move your heartbeat addresses to the bottom of your /etc/hosts files.

A thought - hostfile entries generally look like:
IP

Thanks,
Rita

Re: Clustering Problem

Rita C Workman — Mon, 04 Jan 2010 14:34:29 GMT

Forgot to add...

You don't have DNS running on "any" platform?

/rcw

Re: Clustering Problem

Michael Steele_2 — Mon, 04 Jan 2010 16:25:17 GMT

Hi

You have problems with your FQDN's.

"...Serviceguard recognizes only the hostname (the first element) in a fully
qualified domain name (a name with four elements separated by periods, like those in the example above). This means, for example, that gryf.uksr.hp.com and gryf.cup.hp.com cannot be nodes in the same cluster, as Serviceguard would see them as the same host gryf..."

A MCSB node is the same thing as a hostname or a FQDN.

Also, you need to be using a DNS lookup first before a /etc/hosts file lookup or none of your package floating ip's will ever fail over correctly.

Re: Clustering Problem

Michael Steele_2 — Mon, 04 Jan 2010 16:28:26 GMT

Check the file "/etc/cmcluster/cmclnodelist"

Host1 root
Host2 root

Re: Clustering Problem

Rita C Workman — Mon, 04 Jan 2010 18:23:36 GMT

I think Michael saw what I saw (maybe).

What I didn't care for was that your heartbeat name is too close to your node name. It could maybe do a lookup and stop at the heartbeat and miss going to the actual line (below) for your server. Try changing the name on your heartbeat name to be more unique, like HB-ruxp01 or just HB01.

You can resolve to the hostfile then DNS in your resolv.conf. But both had better be working in harmony. So if you run reverse nslookup's do it for all potential lookup boxes (UNIX hostfile & all DNS servers). That way you ensure resolution is same on all. > Fix accordingly as needed.

For /etc/lvmrc (each to his own), but I generally just set it to Activate=1.
Remember for clustered volume groups you set them to vgchange -c y to give the cluster control.

/rcw

Re: Clustering Problem

Emil Velez — Tue, 05 Jan 2010 00:07:43 GMT

I assume cmclnodelist is on both nodes.

make sure it is in /etc/cmcluster

Re: Clustering Problem

Mousa55 — Tue, 05 Jan 2010 05:21:55 GMT

Hi All,

i don't have the /etc/resolv.conf file in any node.
and i Move it the heartbeat addresses to the bottom in /etc/hosts and the problem is still. and i don't have DNS running on "any" platform.

Node1:
/etc/hosts

127.0.0.1 localhost loopback
10.8.33.251 itprt
10.15.9.92 rhom rhom.sp.local # HP OpenView Operations Mgt
10.8.1.56 ruxpost
10.8.1.60 ruxdevdb
10.8.1.50 ruxdb01
10.8.1.69 ruxerp01
10.8.1.69 ruxerp01.sp.local
10.8.1.51 ruxdb02
10.8.1.51 ruxdb02.sp.local
10.15.1.26 rhhubcas02 hubcas02
10.8.1.2 DNS01 sp.local
10.8.1.3 DNS02 sp.local
192.168.1.40 ruxerp01-heartbeat
192.168.1.30 ruxdb02-heartbeat
==
# more /etc/cmcluster/cmclnodelist
ruxerp01 root
ruxdb02 root
127.0.0.1 root
==
# more /.rhosts
+
ruxerp01 root
ruxdb02 root
==================
Node2:
/etc/hosts
10.8.1.50 ruxdb01
10.8.1.69 ruxerp01
10.8.1.69 ruxerp01.sp.local
10.8.1.51 ruxdb02
10.8.1.51 ruxdb02.sp.local
127.0.0.1 localhost loopback
10.15.1.26 rhhubcas02 hubcas02
10.8.1.2 DNS01 sp.local
10.8.1.3 DNS02 sp.local
10.8.1.56 ruxpost
10.8.1.60 ruxdevdb
#192.168.1.20 ruxdb01-heartbeat
192.168.1.40 ruxerp01-heartbeat
192.168.1.30 ruxdb02-heartbeat
===
# more /etc/cmcluster/cmclnodelist
ruxerp01 root
ruxdb02 root
127.0.0.1 root
==
# more /.rhosts
+
ruxerp01 root
ruxdb02 root
===============

thanks for all replay