AIX 5100-08 on a 7078-6E1
rootvg is on hdisk0 and hdisk1 is unassigned.
Have the AIX 5.3 install CDs + Update (ML02) CD, etc.

Question: Can I do an 5.1-to-5.3 *migration* installation onto hdisk1 while
5.1 is up and running on hdisk0 ?

I RTFM, and it seems that NIM is the only way to do it with cloning. Is there
any other way, not using NIM (which seems to be an overkill with one machine)?

Do I have to bite the bullet and aither go with NIM or
alt_disk_install -C hdisk1
followed by booting from the install CD and do a migration on hdisk1 ?
--
"... I shook my family tree, and a bunch of NUTS fell out ..."

On Wed, 24 Aug 2005 13:53:38 -0500, Bela <bela@bluedog.cc.emory.edu> wrote:

> AIX 5100-08 on a 7078-6E1
> rootvg is on hdisk0 and hdisk1 is unassigned.
> Have the AIX 5.3 install CDs + Update (ML02) CD, etc.
>
> Question: Can I do an 5.1-to-5.3 *migration* installation onto hdisk1
> while
> 5.1 is up and running on hdisk0 ?
>
> I RTFM, and it seems that NIM is the only way to do it with cloning. Is
> there
> any other way, not using NIM (which seems to be an overkill with one
> machine)?
>
> Do I have to bite the bullet and aither go with NIM or
> alt_disk_install -C hdisk1
> followed by booting from the install CD and do a migration on hdisk1 ?

NIM is required to clone/update hdisk1 to the new level while the 5.1
system is running

Al Barth <alDOTbarth@mindspring.com> wrote:
AB> On Wed, 24 Aug 2005 13:53:38 -0500, Bela <bela@bluedog.cc.emory.edu> wrote:
AB>
>> Question: Can I do an 5.1-to-5.3 *migration* installation onto hdisk1
>> while
>> 5.1 is up and running on hdisk0 ?
>>
>> I RTFM, and it seems that NIM is the only way to do it with cloning. Is
>> there
>> any other way, not using NIM (which seems to be an overkill with one
>> machine)?

AB>
AB> NIM is required to clone/update hdisk1 to the new level while the 5.1
AB> system is running

Thanks, Al. Now, shouldn't the NIM master be at 5.3 to bring the client up
to 5.3 (SPOT)?

--
"... I shook my family tree, and a bunch of NUTS fell out ..."

On Fri, 26 Aug 2005 05:22:31 -0500, <bela@bluedog.cc.emory.edu> wrote:

> Al Barth <alDOTbarth@mindspring.com> wrote:
> AB> On Wed, 24 Aug 2005 13:53:38 -0500, Bela <bela@bluedog.cc.emory.edu>
> wrote:
> AB>
>>> Question: Can I do an 5.1-to-5.3 *migration* installation onto hdisk1
>>> while
>>> 5.1 is up and running on hdisk0 ?
>>>
>>> I RTFM, and it seems that NIM is the only way to do it with cloning. Is
>>> there
>>> any other way, not using NIM (which seems to be an overkill with one
>>> machine)?
>
> AB>
> AB> NIM is required to clone/update hdisk1 to the new level while the 5.1
> AB> system is running
>
> Thanks, Al. Now, shouldn't the NIM master be at 5.3 to bring the client
> up
> to 5.3 (SPOT)?
>

I would have to say it has to be at 5.3, because I'm in the same boat with
trying to use NIM to do alt-disk upgrades of 4.3.3 to 5.2. I had to get
my NIM to 5.2 (which I've just done), and now am in the the process of
positioning for other system upgrades. I've been doing a lot of reading
on NIM as I've not used it before. Closest thing was PSSP on an SP2 about
6 years ago.

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Al Barth <alDOTbarth@mindspring.com> wrote:
AB> On Fri, 26 Aug 2005 05:22:31 -0500, <bela@bluedog.cc.emory.edu> wrote:
AB>
>> Al Barth <alDOTbarth@mindspring.com> wrote:
>> AB> On Wed, 24 Aug 2005 13:53:38 -0500, Bela <bela@bluedog.cc.emory.edu>
>> wrote:
>> AB>
>>>> Question: Can I do an 5.1-to-5.3 *migration* installation onto hdisk1
>>>> while
>>>> 5.1 is up and running on hdisk0 ?
>>>>
>>>> I RTFM, and it seems that NIM is the only way to do it with cloning. Is
>>>> there
>>>> any other way, not using NIM (which seems to be an overkill with one
>>>> machine)?
>>
>> AB>
>> AB> NIM is required to clone/update hdisk1 to the new level while the 5.1
>> AB> system is running
>>
>> Thanks, Al. Now, shouldn't the NIM master be at 5.3 to bring the client
>> up
>> to 5.3 (SPOT)?
>>
AB>
AB> I would have to say it has to be at 5.3, because I'm in the same boat with
AB> trying to use NIM to do alt-disk upgrades of 4.3.3 to 5.2. I had to get
AB> my NIM to 5.2 (which I've just done), and now am in the the process of
AB> positioning for other system upgrades. I've been doing a lot of reading
AB> on NIM as I've not used it before. Closest thing was PSSP on an SP2 about
AB> 6 years ago.
AB>

Yep, that's my conclusion as well; No live, alternate disk installation for
the NIM server. Darn!

--
"... I shook my family tree, and a bunch of NUTS fell out ..."

Hi Bela,

To answer your original question of "Question: Can I do an 5.1-to-5.3
*migration* installation onto hdisk1 while 5.1 is up and running on
hdisk0 ?", Yes.

If the hdisk1 that is unassigned is the same size as hdisk0, then you
are set. All you need to do is ensure that the level of the Alternate
Disk Install filesets are at the same level as the current running OS
and then you can use the alt_disk_install command to clone hdisk0 to
hdisk1 and then apply the upgrade to the cloned hdisk1. The only
downtime will be when you boot to hdisk1 to inspect the system and
perform post migration tasks by removing old_rootvg and remirroring
rootvg.

The alt_disk_install method is convenient and preserves the

In article <1126084521.663567.320200@g43g2000cwa.googlegroups .com>, John.Hummel <xSS88x@hotmail.com> wrote:
>
> To answer your original question of "Question: Can I do an 5.1-to-5.3
> *migration* installation onto hdisk1 while 5.1 is up and running on
> hdisk0 ?", Yes.
>
> If the hdisk1 that is unassigned is the same size as hdisk0, then you
> are set. All you need to do is ensure that the level of the Alternate
> Disk Install filesets are at the same level as the current running OS
> and then you can use the alt_disk_install command to clone hdisk0 to

# alt_disk_install -C hdisk1 ... that's easy enough.

> hdisk1 and then apply the upgrade to the cloned hdisk1. The only

How do you apply the upgrade from 5.1 to 5.3 while the system is running?

-Dan

You can accomplish all in 1 command.

alt_disk_install -C -l
/export/lpp_source/aix53_ml02_lpp_source/installp/ppc -w all hdisk1

In article <1126092931.748748.180940@g44g2000cwa.googlegroups .com>, John.Hummel <xSS88x@hotmail.com> wrote:
> You can accomplish all in 1 command.
>
> alt_disk_install -C -l
> /export/lpp_source/aix53_ml02_lpp_source/installp/ppc -w all hdisk1

Ahh! Cool. I'd noticed the -l option but wasn't sure if the installation
required any special scripts or processing not a part of these packages.

Guess not.

Thanks!

-Dan

No problem. It works nicely and I use it all the time.

Just be sure that if the disk you are cloning to and migrating has a
boot logical volume. Otherwise the alt_disk_install (AIX 5.1 atleast)
completes the migration and gives you the following:

Modifying ODM on cloned disk.
Building boot image on cloned disk.

0301-150 bosboot: Invalid or no boot device specified!


Good Luck !