1837893 Members
2962 Online
110122 Solutions
New Discussion

upgrading 10.20 to 11.0

 
SOLVED
Go to solution
Joseph C. Denman
Honored Contributor

upgrading 10.20 to 11.0

sorry about the last...hit the wrong key.


What's going on:

I have serveral k460s that I plan on upgrading to 11.0. Well, I say upgrading, but I will do a cold install of the os. I am attempting to come up with a sequence of events/checklist to make sure I don't miss anything. Could someone please let me know if I have anything incorrect or have any suggestions for me.

1. ignite backup
2. export all vg
3. backup all conf files and maps from step 2. to tape.
4. load 11.0 os
5. load online diags
6. load hp apps (ignite, omni, jetadmin, etc)
7. load hw/sw patches
8. put items in step 3 in /tmp dir
9. check diff in conf files...make appropriate changes.
10. import all vg using map files.
11. ignite backup

Did I miss anything?? Does anyone have a complete list of system conf files (ie /etc/passwd /etc/*.conf). I have been working on a list but want to make sure I get them all.

...jcd...
If I had only read the instructions first??
1 REPLY 1
James R. Ferguson
Acclaimed Contributor
Solution

Re: upgrading 10.20 to 11.0

Hi Joseph:

First, make sure you have the required minimum PDC revision and minimum firmware revision installed for your K-class processor.

If you have the Diagnostic Support Tools loaded, you can obtain the values by doing the following:

# ioscan -fn -C processor
# echo "sel path 32;info;wait;infolog"|cstm > /tmp/infolog

The above assumes that the hardware path of the processor in question was "32" as returned by ioscan.

Match the PDC and firmware values to the table found in chapter-2 of "Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0":

http://docs.hp.com/hpux/onlinedocs/B2355-90679/B2355-90679.html

Next, as to your original question, your scheme looks good.

I prefer to load the Core OS followed by the Applications, the Diagnostics and then the GR release patches. That way, I have the Support CDROM in the drive for both the Diagnostics and the patch bundles.

You are correct in capturing the configuration files, "diffing" them and applying the parts from 10.20 that specifically customize the new templates as loaded.

The essential list of configuration files that I "carry" along, include the following at least so I can easily reference them as I finalize my 11.x build:

# /.forward
# /.profile
# /etc/profile
# /etc/group
# /etc/hosts
# /etc/inetd.conf
# /etc/inittab
# /etc/nsswitch
# /etc/ntp.conf
# /etc/passwd
# /etc/rc.config.d/netconf
# /etc/rc.config.d/netdaemons
# /etc/rc.config.d/nfsconf
# /etc/resolv.conf
# /etc/sendmail.cf
# /etc/services
# /etc/shells
# /etc/shutdown.allow
# /var/adm/cron/*.allow
# /var/adm/fbackupfiles/*
# /var/spool/cron/crontabs/*
# /sbin/init.d/

...JRF...