[JodyTek]

I have a system I am to upgrade from AIX 5300-00 to 5300-08-00-0818 or current release. I have to order certified media on cd's from IBM to satisfy the client. Realizing that this is far to big of a jump to go directly to 5300-08-00-0818, can anyone recommend an upgrade path to best get to 5300-08-00-0818 with the least amount of problems? I do not mind doing multiple updates.

[ross.mather]

All AIX updates are cumulative - so the jump you are suggesting is no more dangerous than a series of TLs.

PLease make suer you know what TL level your applications require.

[duke900ssd]

As Ross said, one step is easier than hopping.
If you think TL08 is stable enough to install (brave person) then I strongly suggest you look at TL08 SP1 (5300-08-01-0819 ) fixes before you go there.
Any base TL has "issues" so as per the best practice for AIX I'd wait for at least SP3 before going to a new TL.

[JodyTek]

Thanks for the advise. I know that the ML's and TL's are cumulative and the theory is that you should be able to make the leap, I guess I am looking for any got ya's for such a large update.

[john.samons]

I would strongly suggest you make sure your applications & databases support this level. Also have a look at the firmware you're currently running on your pSeries system. I wouldn't recommend running far outdated firmware with the latest OS level.

Have a look at a stable level of both, if you'd like to be conservative, use the 2nd latest level.

Also when doing OS updates, make sure you have a previous backup of rootvg, either use the mksysb or alt_disk_install tools...

[JodyTek]

Thanks for the input everyone, I do appreciate it. Here is a little more info on this.
The only application installed on the server runs as a vm and is os independent. The system was installed 4 years ago, and never had any updates. I have been requested to update the microcode on the box (p5-520), and the OS to current maximum supported levels. I went onsite about a month ago, and the system was disconnected from the HMC and would not reconnect. I upgraded the HMC to ver7.3.x and was able to reconnect the p520 to the HMC but had to delete and recreate the partition data in order to access the console. I upgraded the firmware to SF240_335 level and that was successful, I then updated the OS to 5300-06-05, but the update failed. From my understanding and testing I should be able to install the TL 06 and SP 05 at the same time as it is bundled together on the same media. I tried to reject and clean up after the installed update and that seemed fine, but then after a reboot the system would not come back up, I got reference code "AIX IS STARTING", and the system hung there. So I restored from the makesysb, oh, yeah, the system gets full backup weekly and I always do a backup before doing any updates to a system. I learned that one the hard way. lol...

Anyway, so now I am going to go back in another couple weeks to complete this update and want to do all I can to ensure it is successful. The system does not have a disk that I can do an alt_disk_install to so I have to work with what’s in front of me.

My thought this point is to first apply the firmware update and then maybe install 5300-01-00, and just get the system up to a new level and then go from there to TL7 5300-07-00-0747 and then apply SP3 5300-07-03-0811. Does this sound like a plan?

[john.samons]

Some how the phrase "Don't fix something that's not broken" comes to mind... Well now for the next steps...

Just a note: You could have fixed the HMC issue differently... I guess the p5 was rebooted or started while NOT being connected to the HMC? During this stage the service processor will assign a it's own IP address to HMC1 & HMC2 ports... Also to have the current configuration populated onto the HMC, you could have used the rebuild managed node options in the HMC... But at least you see the configuration now...

Good that you have backups in place. Many people don't see the importance of it...

I wouldn't suggest that firmware & OS be upgraded at the same time. For best results I would recommend you upgrade the firmware first (maybe to latest level - but read up on it first to check for advisories) and monitor it for a week. Also note that your previous firmware update of SF240_335 is still in effect, if you didn't rollback...

If you don't have any issues, proceed with the OS. I haven't tested 5300-07-03 completely, but 5300-07-02 seems pretty stable.

First health check the system and make sure there are no hardware or software issues. Make sure file systems have enough space and not filled up. Make sure rootvg has enough space to extend if it needs to.

Also make sure you can do a bosboot and a savebase -V without any errors.


I would go straight from the 5300-00-00 to 5300-07-02 or which ever level you decide on.

When you've upgraded the system, again so a bosboot and savebase and check for errors. Check your bootlist, errpt etc. Also do:
instfix -i | grep AIX
lppchk -v
lppchk -f
lppchk -f

When you're happy with the system and ready to tae the leap, reboot that system.

If it fails, investigate why it failed. Boot from CD and look around why the system won't boot. Else you'll have this cycle forever and not know the answer...and won't be able to provide us with info on the problem...

Good luck!

[nfry]

So where do you find a READ ME about each release. Would lioke to know what the TL and/or fix pack is doing before attempting a install. IBM description is real helpful, 'Service Packs contain important fixes delivered between Technology Levels. 5300-08-03 is Service Pack 3 for the 5300-08 Technology Level.'....

[JodyTek]

Sorry to diss the forum by not attending. Always on the g ths days....


Anyway, thanks for the input John, I can appreciate where you are coming from, but the circum stances are that I work for an IBM BP and the project is initiated at my clients request. The client is across the country and has requested me to travel to be onsite and then have a 4 hour window to complete this project. And on and on, so you can see not normal situation. Anyway, this is somewhat completed, I went onsite and checked in oslevel, fix packages and lpp source installed and what I found was that the client had attempted to to an update and that it had failed, but they committed the file sets instead of backing out. Anyway long story short there were over 150 filesets that needed to be brought up to level to get the system right. But instead the client upgraded to a new P6 550 and will then use the older system for test/dev. So after the new system is in production then I will reload th old one fresh.


For the README's on TL's and SP's there is a package details tab on the download page, or if you order on CD you will get the patch reference numbers.

Thanks all, catch you on a different topic soon....