Replacing a node in Cluster

[Sreejith Kaliyam]

We have a two node cluster setup (rp 4440 and rp 5470) . Now we are going to replace the rp 5470 with rp 4440 (target config will be rp4440-rp4440). Please provide the steps to achieve this.

OS version 11.11
Service Guard A.11.16.00

Rgds
Vinayan

[Matti_Kurkela · Accepted solution]

You want to add the new rp4440 system to the cluster, and remove the old rp5470. You can add the new node before removing the old one, so your cluster's fault tolerance will not be impacted during the replacement operation.

See the "Managing Serviceguard" manual: chapter 7, sub-chapter "Reconfiguring a running cluster".

Here's a direct link to the appropriate version of the manual:
http://docs.hp.com/en/B3936-90079/ch07s04.html#ciibdgcg

It includes the steps to add & remove nodes while the cluster is running. You can use either the Serviceguard Manager GUI, or the Serviceguard cm* commands.

MK

[Sreejith Kaliyam]

Hello Matti,

I read the document ...Thanks for that !!!

I have one package running on rp5470 . Do I have to do something apart from executing cmapplyconf -C asciifile . I mean , does my package will run on the new server after copying all the package directory from old to new. Or do I have to run cmapplyconf -P package_ascii file

Rgds
Vinayan

[Stephen Doud]

If the new node will take on the hostname of the departing node, and the network configuration details, you will not have to update the package configuration file and perform a cmapplyconf on it.

If the new node will use a different hostname, then you will need to edit the package configuration file, replacing the old hostname in the NODE_NAME parameter with the new node name, and cmapplyconf -P the file.

[likid0]

What I normally do, so I don't have to reconfigure a hole new machine and it's apps is:

1.clone the rp5470 ignite image to the rp4440
2.map sandisks and import all vgs
3.shutdown and remove from the cluster the rp5470 node
4. boot the rp4440, add it to the cluster and you are ready to go.

[Sreejith Kaliyam]

Hello Stephen,

As you said I am going to use the same Hostname and IP address of the departing server for the new server.

bat-bc1:/root>cmviewcl

CLUSTER STATUS
bc up

NODE STATUS STATE
bat-bc1 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running enabled bat-bc1

NODE STATUS STATE
bat-bc2 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg2 up running enabled bat-bc2
bat-bc1:/root>



bat-bc2 is going to be get replaced.We have enough downtime so doing it in offline

So the Steps will be ,


1. Make the new server identical as the existing (OS / Software)

2. map the VMAX luns to the new server.

3. Export / Import the volume groups from bat-bc1

4. Edit cmgetconf -c bc cmclconfnew.ascii to change the lan configuration.

5. Halt the cluster.

6. Remove old bat-bc2 from network.

7. Assign the bat-bc2 hostname to new server


8. cmcheckconf -C cmclconfnew.ascii

9. cmapplyconf -C cmclconfnew.ascii

10. Bring up the cluster and packages.


Stephen please correct me if I am wrong somewhere


Rgds
Vinayan

[Aneesh Mohan]

Few things got in my mind...apart from the list you have mentioned above.


a) Make sure the Cluster patch level and Versions are identical on both nodes.

b) Confirm the device files of qurom disk/data disks are identical on both nodes

c) Copy cmnodelist file to new node

d) Confirm hacl entries on /etc/inetd.conf and /etc/services on new node as similar to the another node.

e) Package Configuration files/scripts has to be copied to the new server.

f) update /etc/lvmrc of the new node (Auto VG activation Entry)


cmapplyconf -C clusterA.config could be sufficient since you are not changing any attributes/parameters of the packages.


Regards,
Aneesh

[Sreejith Kaliyam]

Thanks Matty , Stephen, Aneesh for your valuable suggestions. We will perform this activity today night and will update you the success rate !!!