topic Re: dual node cluster with different sg version and different os in Operating System - Linux

dual node cluster with different sg version and different os

anat heilper — Wed, 22 Aug 2007 08:40:35 GMT

Hi,
I have the following configuration:
on 1 node :
os - Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
2.6.9-34.EL
sg - 11.16.09

on 2 node :
os - Red Hat Enterprise Linux AS release 3 (Taroon Update 2)
sg - 11.15.02

can this configuration work correctly? I understood that different sg versions are valid only during rolling upgrade.
Secondly, can 2 nodes in the cluster have differnet os version?
Anat.

Re: dual node cluster with different sg version and different os

anat heilper — Wed, 22 Aug 2007 08:44:52 GMT

I have another questions:
Assuming that in this wituation it's forbidden to change the package configuration, is it possible to change only the control scripts of the packages ( the *.sh files?)

Re: dual node cluster with different sg version and different os

skt_skt — Wed, 22 Aug 2007 22:41:07 GMT

RHEL AS 3/U2 is too old now and i am not sure SG is well supported here.

An ideal scenario should be to keep all nodes in the same OS/software/patch level. Your requirment really looks strange.

Re: dual node cluster with different sg version and different os

anat heilper — Thu, 23 Aug 2007 01:44:42 GMT

Hi,
how can I know if this version of os is supported with serviceguard 11.16 in order to do upgrade?

Re: dual node cluster with different sg version and different os

Peter Leddy_1 — Thu, 23 Aug 2007 02:56:10 GMT

Hi,

This certification matrix will help you.

ftp://ftp.compaq.com/pub/products/servers/ha/linux/svcguard-certmatrix.pdf

Regards,

Peter

Re: dual node cluster with different sg version and different os

Serviceguard for Linux — Thu, 23 Aug 2007 08:36:49 GMT

I don't have it in front of me, but if you review the rolling upgrade section of the release notes you will see a few things:

1) when you want to do a rolling upgrade of both the operating system and the Serviceguard version you should do that one at a time. As an example upgrade the OS on all nodes first and then upgrade the Serviceguard version. In this case, upgrade Serviceguard first since 11.16 is supported with RHEL 3. Then upgrade to RHEL 4.

2) Various commands will not work when the rolling upgrade is incomplete. Specifically if you have two different versions of Serviceguard.

3) You cannot keep the cluster with different OS versions of the nodes. We test rolling upgrades but not running the cluster in this mode long term.

The previous posting pointing to the Certification matrix is a good source.

Re: dual node cluster with different sg version and different os

anat heilper — Thu, 23 Aug 2007 09:27:25 GMT

Hi,
According to the support matrix, it seems that sg 11.16 will support the os Red Hat Enterprise Linux AS release 3. I couldn't see at the documentation any restriction of 2 different os system at the same cluster.
My question is, if I will upgrade the sg version to 11.16 on the machine described above, will that be sufficient? or is there a documented restriction of having the same os system on all of hte nodes of the cluster?
Thanks in advance,
Anat.

Re: dual node cluster with different sg version and different os

melvyn burnard — Thu, 23 Aug 2007 15:59:17 GMT

under normal operating conditions, you must have the same OS version on all nodes in the cluster.

Re: dual node cluster with different sg version and different os

anat heilper — Sun, 26 Aug 2007 02:08:49 GMT

Hi All,
Is this the official Hp support about this? the operating system versions on different nodes of cluster must be identical? ( for example, one node with linux rh3 and one node with linux rh4 with the same sg version say sg 11.17 won't work?

Re: dual node cluster with different sg version and different os

Steven E. Protter — Sun, 26 Aug 2007 09:14:49 GMT

Shalom,

1) HP will not support a mixed node cluster, its not permitted on any version of Linux or HP-UX for that matter. The version of SG and The OS/Kernel must match exactly.

I don't speak for HP, I merely parrot the documentation.

SEP