re-install hpux 11i and SG 11.16

[Hanry Zhou]

I currently have a two-nodes cluster, ruunnig 11.0 and SG 11.12. Now, we plan to re-install 11i and SG 11.16. I'm going to create the cluster by following sequences:

1. install(cold) hpux 11i on both nodes.
2. install SG 11.16 on one node, then another.

My questions are following:

1. Is that sequence I listed above correct?
2. Since all cluster configurations is already created, including hardware, and cabling...
Is there anything I could/should do to prereserve current configurations, and then after I create new cluster, it will help me to make my work easier?

Thanks,
1. Is shtat

[Patrick Wallek]

Yes those steps sound correct. If you are starting over completely from scratch and building a whole new cluster, I would just start completely from scratch.

You could keep your /etc/cmcluster directory just as a reference if you like, but I don't know that I would actually use any of it.

[melvyn burnard]

You could keep:
map files of shared VGs
Pkg files to easily migrate to new cluster
hosts file to keep host names/ip addreses.
just a few ideas

Otherwise have fun and create a cluster from scratch

[Hoang Chi Cong_1]

Yep!
Need to backup all VG configuration file, All cluster's package configuration file.
You will need them after config again your cluster(Just change device file name, for example....)

Goodluck
Regard,
HoangChiCong

[Geoff Wild]

Just so you know, you can NOT have 11.16 and 11.12 in the same cluster. However - we are upgrading a cluster as follows:

existing 2 node cluster w/hpux 11.0 and 11.12 MC/SG.

Bring new "temp" server running 11iv2. We downgraded it to 11.12 MC/SG (Unsupported!) - and created a 3 node cluster. Then, halted one of the other nodes - cold install 11iv2, with 11.16 MC/SG. Then upgraded the "temp" node to 11.16. We had to "manually" copy the binary file - as we still had 1 node @ 11.12 - we then halted that node (11.12) - and will be re-installing 11iv2 on it - then bring it back in.

Your plan is fine - you will have to delete the existing cluster with a cmdelteconf - else your cmquerycl will fail as the cluster lock will say it already belongs to an existing cluster.

Before you begin - I would make a backup of your /etc/cmcluster directory....

Rgds...Geoff

[Mark Nieuwboer]

Hi,

Before you start halt the cluster.
Then change the value AUTOSTART_CMCLD=
in /etc/rc.config.d/cmcluster to 0
so you prevent the startup of the cluster at boot time.

[Hanry Zhou]

Geoff, I'm not going to upgrade the current SG
cluster, instead, to setup a new cluster with new
version of hpux(11i) and sg(11.16) on the top of the
current hardware and network SG configurations, so it
will wipe out the current environment.

Here is a few more questions:

1. Because the current SG environment already
possessed hardware and networking configurations that
SG reqires, so when I create the new SG cluster, I
don't need to worry about the part of work with
regards hardware(shared disks...), and
networking(standby lan...). I just need to a ahead to
install SG software after hpux 11i is installed.
Is that correct?

2. after swinstall sg bundle. I need to perform the
following:
- created exclusive shared vg
- lock disk
- cmquerycl
- modify cluster configuration file, pkg configuration
file, and pkg scripts.
- cmapplyconf
- cmruncl

Is this a correct sequencies/steps?
I know there is very good document out there "managing
sg", but if there is clear step by step commands
setup, that will be helpful. Is there such document
anybody can share with me?

[Geoff Wild]

1. Is that correct?

Yes - but cmdeleteconf first - that will clear the old cluster lock.


2. after swinstall sg bundle. I need to perform the following:


- created exclusive shared vg
- lock disk
- cmquerycl
- modify cluster configuration file, pkg configuration file, and pkg scripts.
- cmapplyconf
- cmruncl

Correct...

Actual steps are in this doc:

http://docs.hp.com/en/B3936-90079/index.html

Particularly, Chapter 5...

Rgds...Geoff

[Kent Ostby]

I would also add in there somewhere ... vgimport shared volume groups.