SEO

Hi,

Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?

Thanks!

In article <%yiPb.15477$lGr.9132@twister01.bloor.is.net.cable .rogers.com>, wrote:
> Hi,
>
> Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
>
> Thanks!
>
>

I have performed ~15 migrations from 4.3.3 to 5.2.0. The only problems
I have had are with applications on the servers and not with the OS
itself. Make sure your firmware is current before doing the migration.
(I use the 'smitty nimadm' method)

"June Bug" <fake@bugs.com> wrote in message news:<%yiPb.15477$lGr.9132@twister01.bloor.is.net. cable.rogers.com>...
> Hi,
>
> Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
>
> Thanks!

If your rootvg is mirrored, unmirror it.
Be sure the CD-ROM microcode is updated.

E-mail me at bverzal@komatsuna.com and I'll send you my project plans
from my upgrades. I did at least 5 over the past 3 months.

BV

"June Bug" <fake@bugs.com> wrote in message news:<%yiPb.15477$lGr.9132@twister01.bloor.is.net. cable.rogers.com>...
> Hi,
>
> Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
>
> Thanks!


5.1 has been around for over two years now so it's pretty mature.
I've done a lot of upgrades and had very few problems.

Iain.

"Bill" <bverzal@komatsuna.com> wrote in message
news:51157c68.0401210809.743fabec@posting.google.c om...
> If your rootvg is mirrored, unmirror it.

can you explain your logic in this? I've only done a handful of upgrades,
but having rootvg mirrored didn't matter a bit, save for remembering to
bosboot -ad the mirrordisk.

... unless you're using alt_disk_install as a upgrade or fallback method, I
don't see the point.

-r

BV, is the unmirrowing a prereq for upgrade...what sort of problem did
you run into?

Thanks

Bill wrote:
> "June Bug" <fake@bugs.com> wrote in message news:<%yiPb.15477$lGr.9132@twister01.bloor.is.net. cable.rogers.com>...
>
>>Hi,
>>
>>Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
>>
>>Thanks!
>
>
> If your rootvg is mirrored, unmirror it.
> Be sure the CD-ROM microcode is updated.
>
> E-mail me at bverzal@komatsuna.com and I'll send you my project plans
> from my upgrades. I did at least 5 over the past 3 months.
>
> BV

In article <mv_Qb.14809$5K1.1019872@twister.southeast.rr.com> , No Body wrote:
> "Bill" <bverzal@komatsuna.com> wrote in message
> news:51157c68.0401210809.743fabec@posting.google.c om...
>> If your rootvg is mirrored, unmirror it.
>
> can you explain your logic in this? I've only done a handful of upgrades,
> but having rootvg mirrored didn't matter a bit, save for remembering to
> bosboot -ad the mirrordisk.
>
> .. unless you're using alt_disk_install as a upgrade or fallback method, I
> don't see the point.
>
> -r
>
>

We have all the servers here mirrored, but the servers do not generally
have four disks internally. So I break the mirrored pair and upgrade
on only a single drive. I'm exposed while the upgrade is going on,
but as you pointed out I have a built-in fallback method. If the app
does not run in production with the new OS version, I boot back to
the original os and re-mirror.

Mike

Rick <rmunn@eastlink.ca> wrote in message news:<w50Rb.3808$Ja2.51227@nnrp1.uunet.ca>...
> BV, is the unmirrowing a prereq for upgrade...what sort of problem did
> you run into?
>
> Thanks
>
> Bill wrote:
> > "June Bug" <fake@bugs.com> wrote in message news:<%yiPb.15477$lGr.9132@twister01.bloor.is.net. cable.rogers.com>...
> >
> >>Hi,
> >>
> >>Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
> >>
> >>Thanks!
> >
> >
> > If your rootvg is mirrored, unmirror it.
> > Be sure the CD-ROM microcode is updated.
> >
> > E-mail me at bverzal@komatsuna.com and I'll send you my project plans
> > from my upgrades. I did at least 5 over the past 3 months.
> >
> > BV

After upgrading my H80 to 5.2, the system hung and would not reboot.
I called IBM after about an hour of troubleshooting. We determined
that the SSA adapter fileset did not get upgraded, and as well, the
bos.mp for some reason did not get upgraded. I also discovered that
for some reason, /tmp was missing from /etc/filesystems. The IBM tech
informed me there was a known issue upgrading to AIX 5 on system with
rootvg mirrored. As of November, 2003, there was no fix from IBM. We
determined that was not the case with my system, forced these 2
filesets to be applied, I added a "/tmp" stanza to /etc/filesystems,
then booted. No problems.

If you get the "bug", the system will not boot. fsck will run on all
filesystems and might even fix things, but the filesystems still will
not mount. The only fix as of November, 2003 was a mksysb restore and
try again. The way around the "bug" was to unmirror rootvg first.

BV

June Bug <fake@bugs.com> wrote:
> Hi,

> Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?

> Thanks!

I've had one "huh?" on both of the systems I upgraded from
AIX 4.3.3-11 to 5.1.0-04 (and then ML05). I run "diag" (or boot into service
mode), select "Task Selection", and get:

....snipped
Run Diagnostics
Run Error Log Analysis
Display or Change Diagnostic Run Time Options

** CATALOG ERROR ** (68)
Add Resource to Resource List
....snipped

Anyone have any idea what that "CATALOG ERROR" line is all about?

Thanks,
Steve

----------------------------------------------------------------------------
Steve Roseman
Lehigh University Computing Center
lusgr@Lehigh.Edu

"Stephen G. Roseman" wrote:
>
> June Bug <fake@bugs.com> wrote:
> > Hi,
>
> > Anyone had experiences with 4.3 to 5.1 upgrade? Is there any gotchas?
>
> > Thanks!
>
> I've had one "huh?" on both of the systems I upgraded from
> AIX 4.3.3-11 to 5.1.0-04 (and then ML05). I run "diag" (or boot into service
> mode), select "Task Selection", and get:
>
> ...snipped
> Run Diagnostics
> Run Error Log Analysis
> Display or Change Diagnostic Run Time Options
>
> ** CATALOG ERROR ** (68)
> Add Resource to Resource List
> ...snipped
>
> Anyone have any idea what that "CATALOG ERROR" line is all about?
>
> Thanks,
> Steve
>
> ----------------------------------------------------------------------------
> Steve Roseman
> Lehigh University Computing Center
> lusgr@Lehigh.Edu

Message text is stored in catalogs (*.cat) files.
The smit & diag panels can use these catalogs to
get the text to be displayed for panel entries.
There are catalogs for each locale (e.g. en_US,
de_DE) and usually for each fileset.

I would suggest taking a look at the filesets:
bos.msg.en_US.diag.rte
and
devices.msg.en_US.diag.rte
(substitute your $LANG for en_US).
One or both of these may not have been updated to 5.1,
and if they are old (or not installed at all), then
the 'diag' command can't find the right text to
display for message #68.

lslpp -h | grep diag | grep msg
lppchk -f bos.msg.en_US.diag.rte
lppchk -f devices.msg.en_US.diag.rte

If they are not installed, install them from the
5.1 base media and then apply ML5 again.

Paul Landay