Very Computer

Hello NG,

as i wrote yesterday i had to migrate the systems, i tried it last night. i
tried the migration installation per AIX5.2CDs. As in APAR-database
written with NIM-update we have the problem, that the migration hangs up at
93%. so now we dont know, what to do.

Has anyone the same problems?

kind regards,

sven morling....

Quote:>Hello NG,

>as i wrote yesterday i had to migrate the systems, i tried it last night. i
>tried the migration installation per AIX5.2CDs. As in APAR-database
>written with NIM-update we have the problem, that the migration hangs up at
>93%. so now we dont know, what to do.

>Has anyone the same problems?

Have you checked the firmware level of the regatta ?
There are some pre requesites for AIX 5.2.

the firmware is today updated in the two (yes, two, one 690 and one 670).
so i think i would try it after the succesful firmware update. because the
SE still try to get our 690 running ;-) perhaps there has to come a new
serviceprocessormodule ;-). not very nice from them.

thanks for your fast answers and a nice weekend,

sven morling

Quote:> Hello NG,

> as i wrote yesterday i had to migrate the systems, i tried it last
> night. i tried the migration installation per AIX5.2CDs. As in
> APAR-database written with NIM-update we have the problem, that the
> migration hangs up at 93%. so now we dont know, what to do.

> Has anyone the same problems?

> kind regards,

> sven morling....

hi ng,

sorry for that request, but it seems that we dont have enough time to
wait a little bit more than 20minutes up to 40minutes. there is no
problem. perhaps it time is needed by the number of rpm-packages that
have to be registered.

so thank you for that.

another point that we expect is, in the new 5.2 all mountpoints that are
not in the rootvg are not created. this means, there no directories, so
that you have to create at first all directories manually (or a little
bit automatic:
'for FS in `lsfs | awk ' /jfs2/ { print $3 }'`; do mkdir $FS; done'

and than you can make 'mount -a'.

thanks for your help.

sven morling....

There is a fix for NFS mount points, I believe this only occurs during
migrations, normal 5.2 Install does not have any issues, but
migrations have NFS issues.

where it is not automatically mounting NFS shares defined in
/etc/filesystems.
This is a known problem: IY40215, and occurs because an upgrade from
5.1
to 5.2 was done. Is this what you did to get the standard build?

The details are on this page:

http://www-1.ibm.com/support/docview.wss?rs=0&context=SWG00&q=AIX+5.2+NF
S+mount&uid=isg1IY40215&loc=en_US&cs=utf-8&cc=us&lang=en

kind regards

Aamir

Quote:> There is a fix for NFS mount points, I believe this only occurs during
> migrations, normal 5.2 Install does not have any issues, but
> migrations have NFS issues.

> where it is not automatically mounting NFS shares defined in
> /etc/filesystems.
> This is a known problem: IY40215, and occurs because an upgrade from
> 5.1
> to 5.2 was done. Is this what you did to get the standard build?

> The details are on this page:

> http://www-1.ibm.com/support/docview.wss?rs=0&context=SWG00&q=AIX+5.2
+N
> F S+mount&uid=isg1IY40215&loc=en_US&cs=utf-8&cc=us&lang=en

> kind regards

> Aamir

hi aamir,

the mountpoints werent nfsmounts. they were simple mountpoints in
not-rootvgs. thats all.

but what i forgot is, that i made a alt_disk_install before the
migration. that means i dont tried the cloned rootvg so that i
installed 5.2 on untested altinst_rootvg. maybe there was two steps too
much for that. because i think, at another time i made an
alt_disk_install and where i booted from cloned disk, there also werent
the mountpoints!

sven....