topic Re: one node serviceguard cluster in Operating System - HP-UX

one node serviceguard cluster

CGEYROTH — Thu, 29 Jan 2004 12:36:27 GMT

Can this be done? (I know that the idea of a cluster indicates more than one),are there any gotcha's or documents indicating how to do it?

Re: one node serviceguard cluster

Dave Hutton — Thu, 29 Jan 2004 12:40:22 GMT

You can do it. We used to do it to basically make our test/dev environments look and feel like our prod ones.

I don't recall any gotchas, I believe you can just set them up like any other cluster. It's been a long time since I've messed with it.

Dave

Re: one node serviceguard cluster

melvyn burnard — Thu, 29 Jan 2004 12:45:27 GMT

Yes yo can do this, and it is supported.
Many people use a single nopde to do basic testimng, or use the LAN failover facility.
Setting it up is the same as any other cluster, just no need to repeat the work on the other nodes ;-]

Re: one node serviceguard cluster

Sridhar Bhaskarla — Thu, 29 Jan 2004 12:50:38 GMT

Hi,

Yes. YOu can do it. I basically setup my workstation as a single node cluster to test my package scripts involving package dependencies.

The main advantage is for local lan failover and easy convertibility to multi-node cluster.

-Sri

Re: one node serviceguard cluster

CGEYROTH — Thu, 29 Jan 2004 12:57:48 GMT

I've created a cmclnodelist file that contains the following:-

nodename root

when I run the command

# cmquerycl -n nodename -C conf.ascii

I get:

Permission denied to nodename
cmquerycl : Unable to find an unused cluster name: No such device or address.

what have I done wrong?

Re: one node serviceguard cluster

melvyn burnard — Thu, 29 Jan 2004 13:05:40 GMT

first thing to check is doing:#
nslookup hostname
does this come back with the right ip address?
then do nslookup ip_address
does this come back with the right hostname?
If these do not work, then you need fix that first.
If they do work correctly, then change the /etc/cmcluster/cmclnodelist file to jusy have a + in it, and try again
If that does not help, try removing the cmclnodelist file and having a .rhosts file for root.

The correct syntax should be
cmquerycl [-v] -C -n node1

Re: one node serviceguard cluster

Kevin Wright — Thu, 29 Jan 2004 18:05:10 GMT

Is your cluster running?

what does cmviewcl -v show?

Re: one node serviceguard cluster

Sridhar Bhaskarla — Thu, 29 Jan 2004 18:07:13 GMT

Hi,

If rlogin is successful then cmclnodelist will work.

Keep an .rhosts entry for 'node root' and see if you can rlogin with 'rlogin node -l root'.

It may most likely an nslookup issue.

-Sri

Re: one node serviceguard cluster

CGEYROTH — Fri, 30 Jan 2004 08:16:18 GMT

The problem was a .rhost issue which is now resolved.

One final issue, when I ran the cmquerycl command to build the cluster configuration file, it made the following statement, will this cause me problems later as I attempt to configure my one node cluster? :-

Warning: Failed to find a configuration that satisfies the minimum network configuration requirements.
Minimum network configuration requirements are:
- 2 or more heartbeat networks OR
- 1 heartbeat network with local switch OR
- 1 heartbeat network with serial line.

Re: one node serviceguard cluster

melvyn burnard — Fri, 30 Jan 2004 08:38:29 GMT

No, this is just alerting you that you do not have the recommended minimum for HA compliance in your network config.

Re: one node serviceguard cluster

jjh_1 — Tue, 31 Jan 2006 23:14:19 GMT

minimum configuration

step 1 : need not Lock Disk
step 2 : need not relocatable IP (if you need, you can use)
step 3 : need not standby lan card (if you need, you can use)
step 4 : cd /etc/cmcluster
setp 5 : cmquerycl -C onenodetest.ascii -n onlyserver
setp 6 : modify onenodetest.ascii (vi onenodetest.ascii)
setp 7 : mkdir /etc/cmcluster/pkg1 (if you need, you make more package)
step 8 : cd /etc/cmcluster/pkg1
step 9 : cmmakepkg -p pkg1.conf (modify)
step 10: cmmakepkg -s pkg1.cntl (modify)
step 11: cd /etc/cmcluster
step 12: cmcheckconf -C $PWD/onenodetest.ascii -P $PWD/pkg1/pkg1.conf
if no error
step 13: cmapplyconf -C $PWD/onenodetest.ascii -P $PWD/pkg1/pkg1.conf
if successful
step 14: cmruncl
step 15: cmvicl
CLUSTER STATUS
onenodetest up

NODE STATUS STATE
onlyserver up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled onlyserver ewcl