1837086 Members
2382 Online
110112 Solutions
New Discussion

Re: cluster issue

 
Lakshmikanth Baddam
Frequent Advisor

cluster issue

after i gave the below cmquerycl command i got this warning and even ascii file was not ceated
please help me on this


# cmquerycl -C chld.ascii -n host1 -n host2
Warning: Unable to determine local domain name for childps1
Note: Disks were discovered which are not in use by either LVM or VxVM.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.

Node Names: host1
host2

Bridged networks (local node information only - full probing was not performed):

1 lan0 (host1)

2 lan1 (chost1)

5 lan0 (host2)

6 lan1 (host2)

IP subnets:

IPv4:

3.164.120.0 lan0 (host1)
lan0 (host2)

192.168.1.0 lan1 (host1)
lan1 (host2)

IPv6:

Possible Heartbeat IPs:

3.164.120.0 3.164.120.83 (host1)
3.164.120.84 (host2)

192.168.1.0 192.168.1.122 (host1)
192.168.1.123 (host2)

Possible Cluster Lock Devices:

LVM volume groups:

/dev/vg00 host1

/dev/vgora host1

/dev/oradata host1

/dev/vg00 host2

/dev/finvol host2
6 REPLIES 6
IT_2007
Honored Contributor

Re: cluster issue

You better plan before attempt to create cluster ascii file since if you don't know what you are doing then it would be difficult manage it.

If you followed Service Guard installation manual then you might have seen cheat sheet which gives you idea about information like host name, IP address, heartbeat, volume groups, cluster lock, package name, package IP address etc.. Fill out on the paper and then follow it out.

Once you have above information then you know how to connect nodes and heartbeat.
melvyn burnard
Honored Contributor

Re: cluster issue

You seem to have an issue with your network connectivity as the output you supply indicates no connection between the two:
Bridged networks (local node information only - full probing was not performed):

1 lan0 (host1)

2 lan1 (chost1)

5 lan0 (host2)

6 lan1 (host2)

IP subnets:

IPv4:

3.164.120.0 lan0 (host1)
lan0 (host2)

192.168.1.0 lan1 (host1)
lan1 (host2)

IPv6:

Possible Heartbeat IPs:

3.164.120.0 3.164.120.83 (host1)
3.164.120.84 (host2)

192.168.1.0 192.168.1.122 (host1)
192.168.1.123 (host2)

fix this before you progress
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Prashanth.D.S
Honored Contributor

Re: cluster issue

Hi Lakshmikanth,

Can you check if there are any firewall's which are preventing the connection...

Best Regards,
Prashanth
srinimar
Frequent Advisor

Re: cluster issue

Hi

I have configured to heartbeat IP's.
192.168.1.122 and 123. for each nodes. and placed them in /etc/hosts and /netconf files.

I have two servers A - DataBase server and B- Applâ n server.

File systems in A


/dev/vg00 -----/a/abc
/dev/vgora ----/b/cds
/dev/oradata----/ghg/gg


file systems in B

/dev/finsol -----/kjhf/jhf
/dev/solns ----/jsdfj/jdhfj

and the file systems above are coming from a common storage point. And FS on A cannot be seen from B. and File systems on B cannot be seen from A.

Here do I need to create a different VG on server A and export it to B. as I need to have lock enabled also in ascii fileâ ¦

Please help me on this if you can provide me the detailed steps of cluster setup.

SM
Svetoslav Gyurov
Valued Contributor

Re: cluster issue

Hi,

To create a cluster you need several things to do. Add node hostnames to the right places:

vi /etc/hosts
192.168.1.122 host1
192.168.1.123 host2

vi /etc/cmcluster/cmclnodelist
host1 root
host2 root

vi ~/.rhosts
host1 root
host2 root

And now you need shared storage, you need to present one LUN to both nodes and after that at any of the nodes create new volume group and export it to the other:

pvcreate /dev/dsk/c13t0d0

mkdir /dev/vg01

mkdir /dev/vg01/group c 64 0x010000

vgcreate vg01 /dev/dsk/c13t0d0

vgexport -p -s -m vg01 /tmp/vg01.map


After that copy vg01.map on the other node and import the volume group:

mkdir /dev/vg01

mkdir /dev/vg01/group c 64 0x010000

vgimport -s -m /tmp/vg01.map vg01


Before executing cmquerycl try to activate the volume group on the first node and after that on the second node. From the first node try to ping the second and after that try to login using rlogin. Repeat the same procedure from the second node against the first one. If everything is working you can now start cmquerycl, create configuration file and create cluster.
Regards.


--
sve
Lakshmikanth Baddam
Frequent Advisor

Re: cluster issue

i got it rectified. now i got the solution.