University of Wisconsin-Madison  My UW
Computing @ UW-Madison

Installing AIX
Tuning AIX
Patching, Fixes, APARs
Compilers
Tips & Tricks

TSM Clients

IBM pSeries Support
TechLib
IBM Redbooks
IBM Documentation Library

Back to DoIT

Upgrading AIX 4.3.3 to 5.1

READ THE 4.3.3 Migration Document (which applies to 5.1, too).

http://techsupport.services.ibm.com/server/aix.techTips?refNo=91623329313242

Please ensure that you have a full system backup (using sysback or mksysb if possible).

These are the highlights & local notes:

  1. Break all mirrors.

    NOTE: You can use the Alternate Disk Installation facility to clone rootvg onto one of the mirrored disks for backup purposes. Issue a "bootlist -m normal hdisk0" after cloning. If something goes wrong you can then boot from the old copy of the OS, reclone it, and try again.
  2. Make sure "lppchk -v" returns no errors. Fix any errors you encounter.
  3. Commit all packages.
  4. Uninstall packages you don't need. This usually isn't a problem, except that more packages equates to more time spent installing software.
  5. Ensure all user definitions are correct: "usrck -n ALL". Fix them if not. (usrck -t)
  6. Ensure all group definitions are correct: "grpck -n ALL". Fix them if not (grpck -t)
  7. Ensure that rootvg has 100MB of space free, or if not, there is 100MB of space in /usr. Ensure that /tmp has 15Mb of space. Ensure that / has 10MB of space.
  8. It's best to delete everything in /tmp if you can.
  9. Make a full system backup (sysback or otherwise).
  10. Do the migration. AIX 5.1 can tell you right before you migrate what packages might be messed up. Choose those options.
  11. Reboot into the hdisk that you migrated (not the alternate disk clone).
  12. Exit from the SMIT menu that starts at boot. Mount post.doit.wisc.edu:/aix/51/inst.images and update_all (don't install everything, just update things that may have been missed). Reboot.
  13. Run "lppchk -v" to see what packages are messed up. Fix them.

    This will probably include reinstalling parts of the compiler sets, and then
    patching them immediately afterwards.
  14. Issue an "oslevel" command. If the system reports anything less than 5.1.0.0 then
    try "oslevel -l 5.1.0.0" to find the offending packages. Fix them.
  15. If you use IBM Enterprise Storage systems, the subsystem device driver (SDD) may need to be updated to a 5.1-compatible version. You will have to remove the 432 package and install the 510 package, and to do that you will need to unmount the affected filesystems, vary off the affected volume groups, remove SDD and all the other packages (ibm2105, ibmpfe, ibm_Sdd), remove the fibre channel devices (do this in SMIT so you can recursively delete all the attached hdisks and vpaths), install the new SDD & utility packages, run cfgmgr to detect all the software, and remount the filesystems. Annoying.
  16. Update DoIT.local.OpenSSH to the 5.1 package available. If you are not working with DoIT, rebuild OpenSSH. Changes to the AIX 5.1 OS break OpenSSH, and the only way to have the changes take effect is with a recompile.
  17. Resecure the machine. Follow the AIX 5.1 checklist to ensure that the machine is at the standard configuration, and that you are not running any services you do not need. The AIX 5.1 migration will reenable lots of services in /etc/inetd.conf that you probably don't want on (all the r* services, all the rpc* stuff).
  18. If you had custom shells in /etc/security/login.cfg (like /usr/local/bin/tcsh) put them back in the "shells=" line again. The migration install preserved the old line in login.cfg but it is commented out. You will have to re-add the shell to /etc/shells, though.
  19. Once you are sure your migration worked, remirror the drives.

 

Copyright © 2003 The Board of Regents of the University of Wisconsin System