AIX upgrade 5.3 to 6.1 using NIM

Hello,

Is there a step by step guide to upgrade 5.3 to 6.1?   We have  NIM setup as well.
mokkanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

woolmilkporcCommented:
Hi,

the Infocenter contains a detailed description how to migrate from AIX 5 to 6 using the installation media:

http://pic.dhe.ibm.com/infocenter/aix/v6r1/topic/com.ibm.aix.howtos/doc/howtos/HT_insgdrf_migrationinstall.htm

There is also a description how to use NIM and its Alternate Disk Migration Facility (NIMADM):
http://pic.dhe.ibm.com/infocenter/aix/v6r1/topic/com.ibm.aix.install/doc/insgdrf/alternate_disk_installation.htm

Since the latter seems a valid option for you let me explain in short what you'll need and how it works.

You'll need:

- A working NIM server at the same or higher level than the target client level
- The filesets bos.alt_disk_install.boot_images, bos.alt_disk_install.rte installed on the NIM server.
- A complete lppsource NIM resource at the level you're going to migrate the client to, which means including all TLs and SPs needed for that level.
- The above filesets bos.alt_disk_install.boot_images, bos.alt_disk_install.rte contained in this lppsource.
- A SPOT created from the mentioned lppsource.
- rsh communications between server and client: rshd enabled in /etc/inetd.conf and started on the client, the NIM server's hostname contained in ~root/.rhosts  of the client.
- A free hdisk on the client at least as big as the client's original rootvg disk. This disk must not be a member of any volume group! If the client's rootvg is mirrored a migration can be done to a single target disk nevertheless.

How nimadm works behind the stage:

- Create a copy of the client's rootvg named altinst_rootvg with LVs named altinst_<lvname>.
- Export these LVs and mount them on the NIM server via NFS
- Migrate mounted LVs to new level on the NIM server by means of an lppsource and a SPOT at the target level.
- Change the client's bootlist to boot from the new disk next time.
- Rename altinst_rootvg to rootvg, rename rootvg to old_rootvg, rename LVs according to the same scheme at the reboot.

What you must do:

Having created the lppsource and the SPOT, having established rsh communication and having provided a free disk just run on the NIM server:

nimadm -c client_name -s spot_name -l lppsource_name -d hdiskname -Y

If something goes wrong:

1) If you already tried to reboot the client:
Set the client's bootlist to boot from the old disk and reboot. Use the SMS menus for this if required.
Run nimadm -C -c client_name -s spot_name on the server to clean everything up.
Correct errors and try again.

2) If you didn't reboot:
Run nimadm -C -c client_name -s spot_name on the server to clean everything up.
Correct errors and try again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mokkanAuthor Commented:
Thank you very much.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.