Moving Machines, Changing IPs, ServiceGuard

[Ron Levy]

I'll be moving a cluster of MC/ServiceGuard machiens and their packages to a different location and this I'll have to be giving them new IP addresses (host, packages, and heartbeat network) for them to work with the new scheme.

Are there any gotchas I should know about? Is it as simple as changing the package files and bringing up the packages, or is there more?

Thanks,
-Ron Levy

[Sridhar Bhaskarla]

Hi Ron,

If you are changing the IPs, then you will need to make sure that all the external clients that connect to your packages are aware of the changes.

You will certainly need to recompile your cluster ascii file and package ascii files (if you change them).

I would suggest to go for a clean migration. Delete the cluster configuration (cmdeleteconf) after halting the cluster before moving the servers. Move the servers, make modifications to your ascii and control files as required and re-apply the configuration. Be sure to test the failover.

Good luck,
Sridhar

[Ashwani Kashyap]

Hey , lot of changes there .
At the new site don't bring up your cluster . Make all your networking changes that you have to and when you are fully satisfied that they are functional then go ahead and modify the cluster ascii file and package ascii file to reflect those changes .

THen do a cmcheckconf again . Make sure you have no errors .
Then do a cmapplyconf and recreate the binary .

THen bring up your cluster and packages . Check all the functionalities including failover .

Update your host/DNS entries , check again .

THen you are ready to release it to your users .

[melvyn burnard]

suggested steps:

a) halt the cluster activities, and set /etc/rc.config.d/cmcluster variable from 1 to 0, then make sure you have a backup, preferably Ignite Make_recover tape.
b) change netconf file to at least have a primary ip/subnet/route settings ready for hte move
c) halt the nodes.
d) move htem
e) boot them, and see if they get onto the new network, check DNS, make any other network configuration changes and check again.
f)run cmquerycl and create a test ascii file, just to make sure that you have what you expect to see.
g)If all the above has worked, and you get what you expect, change the cluster ascii file, and hte package cntl/conf files to reflectnew ip's/subnets etc.
and then do a cmcheckconf.
h) if this worked, cmapplyconf,
and then cmruncl to see if cluster will form and packages start.
j) change cmcluster variable back from 0 to 1.
k) back up any changes made!