I have a cluster with HP-UXv1 with 2 nodes.
1- rp7420
1- rp7410
I want to replace the rp7410 with another rp7420.
What is the best process to do??
What considerations should we have?
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
>>I have a cluster with HP-UXv1 with 2 nodes. 1- rp7420 -- say it is server: A 1- rp7410 -- say it is server: B
>>replace the rp7410 with another rp7420 -- say C.
- Build server C with same config as B , and same lan connection & subnet. - Take ignite tape/network image of B and restore image on C. - Move all pacakges of B server to A. - Halt the node B. - Remove the node B from cluster.ASCII file and package config files. - Compile the pkg and ascii file:
- Configure the ip of B system to C system (new target rp7420) - Zone all the pkg vgs of B system , to new CC system, make the luns visible. - create vgdir /group files/ copy map files / import the pkg vgs to this system.
- create the users that supposed to be on system C, and the pkg users.
- copy server A : /etc/cmcluster/pkg[*] directories to system C.
- Add the hostname of server C in cluster. ascii file. Make sure the lan parametrs are configured correctly as it was in B , or edit ascii file for C's lan parameters.
- compile cluster.ascii file , make sure quorum server or lock/disk mentioned properly. #cmcheckconf -v -C cluster.ascii #cmapplyconf -v -C cluster.ascii
- At this point the new rp7420 (system C) will be part if the 2 node cluster. A & C.
- Add system C's node name in pkg.conf file and compile the pkgs. # cmcheckconf -v -P pkg.conf # cmapplyconf -v -P pkg.conf
- check with cmviewcl.
- Bring back the packages to the new node C . # halt its packages on A. # start its packages on C.
- A good idea would be to check the FO_test of node A packages as well to this new node (C) if applicable.
-verify with cmviewcl and check vg/lv/fs's and application(s).
okay, now i am assuming that your OS is installed on the new box.
You have to go this way.
1) Move all the packages from Node B to Node A. 2) Halt your node B. 3) Move your node B out of the cluster config by editing the cluster.ASCII and package.conf files and reapllying the new configuration with checkconf and cmapplyconf.
Now, your cluster is having only one node A and your other node B is out of the cluster.
4) Now, down the node B. 5) configure your node C(new server) with same configurations as your node B was having i.e. Ip address, VG creation, user creation, /etc/hosts, /etc/group, /etc/resolv.conf. 6) copy /etc/cmcluster/* from node A to node C.
Your server is now ready to add to the cluster 7) Edit the cluster.ASCII and package.conf to add node C in them. Make sure to take care of cluster lock disk configuration. 8) reapllying the new configuration with cmcheckconf and cmapplyconf.
Now you have two nodes (A and C) cluster again.
9) test the cluster by restarting the cluster and by switching packages from one node to other.
just a small question... why wouldn't you put the new server C as a third node ? This way you could still let your primary/failover be intact or what...
Printable version
