SEO

Hi,

I'm new to AIX and am trying to establish procedures for applying
maintenance to our systems. This is my first stab at it.

We've got AIX 5.2 at ML 3. I thought I'd try applying ML 4 by doing
an alt_disk_install clone of rootvg. Here's the command I'm using:

alt_disk_install -C -b update_all -l /ml04_dir hdisk1

Everything seems to go okay, and I can boot from hdisk1. My problem
is that once on the new rootvg, an 'oslevel -r' still shows me at
5200-03. If I do a smit update_all and preview an install of ML4, it
tells me that it would install the following filesets:

csm.client 1.4.0.0
csm.core 1.4.0.0
csm.dsh 1.4.0.0
devices.pci.3310e000.rte 5.2.0.0
invscout.com 2.2.0.0
invscout.ldb 2.2.0.0
invscout.rte 2.2.0.0

So apparently these were not updated during the alt_disk_install
process. I apply these, reboot, and now 'oslevel -r' says I'm at
5200-04.

My question is: why didn't this last bit of maintenance get applied
when I did the alt_disk_install? I checked the output from that
command, and there's no mention of any of these filesets one way or
the other (no failures, "I'm skipping these", or anything else).

Am I missing something? Is this normal for an apply of an ML (either
via alt_disk_install or 'normal' install (i.e., would I have had to go
through 2 rounds of applies whether or not I was using
alt_disk_install)?

Any insight would be appreciated.

Thanks,
Bill

Bill Kelly
Auburn University OIT

On Fri, 08 Oct 2004 12:08:22 -0700, Bill Kelly wrote:

> Hi,
>
> I'm new to AIX and am trying to establish procedures for applying
> maintenance to our systems. This is my first stab at it.
>
> We've got AIX 5.2 at ML 3. I thought I'd try applying ML 4 by doing an
> alt_disk_install clone of rootvg. Here's the command I'm using:
>
> alt_disk_install -C -b update_all -l /ml04_dir hdisk1
>
> Everything seems to go okay, and I can boot from hdisk1. My problem is
> that once on the new rootvg, an 'oslevel -r' still shows me at 5200-03.
> If I do a smit update_all and preview an install of ML4, it tells me that
> it would install the following filesets:
>
> csm.client 1.4.0.0 csm.core
> 1.4.0.0 csm.dsh 1.4.0.0
> devices.pci.3310e000.rte 5.2.0.0 invscout.com
> 2.2.0.0 invscout.ldb 2.2.0.0 invscout.rte
> 2.2.0.0
>
> So apparently these were not updated during the alt_disk_install process.
> I apply these, reboot, and now 'oslevel -r' says I'm at 5200-04.
>
> My question is: why didn't this last bit of maintenance get applied when I
> did the alt_disk_install? I checked the output from that command, and
> there's no mention of any of these filesets one way or the other (no
> failures, "I'm skipping these", or anything else).

I don't know the answer to your question, but the technique we use is to
create an alt_disk_install from the current system for a backup, then
apply the maintenance to the current system. This has always worked.

And we have never had to use the backup. ML upgrades, especially a minor
one like this, are normally eventless. Unlike version upgrades BTW, these
normally have problems IME.

Regards, Ian

Bill Kelly wrote:
> Hi,
>
>
> csm.client 1.4.0.0
> csm.core 1.4.0.0
> csm.dsh 1.4.0.0
> devices.pci.3310e000.rte 5.2.0.0
> invscout.com 2.2.0.0
> invscout.ldb 2.2.0.0
> invscout.rte 2.2.0.0
>
> So apparently these were not updated during the alt_disk_install
> process. I apply these, reboot, and now 'oslevel -r' says I'm at
> 5200-04.
>
> My question is: why didn't this last bit of maintenance get applied
> when I did the alt_disk_install?

you did an update all, which means
update some.fileset from 1.2.x to 1.2.y
but not from 1.2.x to 1.3.y

you probably had invscout.com (f.e.) at 2.1, this way it wont upgraded
same as if you used
installp -acpgXB -d /somewhere all

I am not sure how to tell alt_disk_install to do it automatically - but
-w flag sounds promising

or -F 5200-04_AIX_ML