AIX 4.3.3 to 5L

[dlanni]

Has anyone Upgraded from AIX 4.3.3 to AIX 5.1, if so is it a Migration or a New and Complete Overwrite. Any doc's would be helpful.

Thanks

 

[DSMARWAY]

Hi,

The upgrade is a purchasable upgrade , and a migration upgrade will suufice , some of the things to check for are :-

the following is a list of things to look out for on AIX 5.1 install:

EEH and 64-bit Support of ARTIC960 Adapters

AIX 5L Version 5.1 Supported Devices and Machines
2751 ESCON CNTRL UNIT, PCI/LONG/32BIT/5V
2947 ARTIC960HX ADPTR + 4PRT MP AIB, PCI/LONG/32BIT/3.3 OR 5V
6310 ARTIC960RXD, DIGITAL TRUNK, PCI/LONG/32BIT/3.3 OR 5V


Enablement for Enhanced Error Handling (EEH) for the ARTIC adapters,
feature codes 2751, 2947 and 6310, and enablement for 64-bit support for
the ARTIC adapter, feature code 2751, is available by downloading
devices.artic960.2001 from the following website:


ftp://service.software.ibm.com/devices/rs6000/artic


If ARTIC adapter access is dependent on an additional LPP being installed,
full EEH capability will depend on the ability of that LPP to support EEH.

Use of JFS2 on the 32-bit Kernel


There is a known problem with using JFS2 filesystems on the 32-bit kernel.
The problem generally manifests itself as a hang of filesystem commands to
the affected JFS2 filesystem, but not a system hang. These hanging commands
generally cannot be killed. Some examples of commands which can cause
problems are ls, rm, and cp. Generally, multiple instances of these
commands must be running concurrently for the problem to manifest itself.


This problem is caused by a limitation imposed by the 32-bit kernel on how
much memory is available for use by JFS2. Running multiple instances of
these commands concurrently, running them against a very large file, or
running them against a file which is highly fragmented may cause this
problem to manifest.


Once the problem occurs, The only way to clear the problem is to reboot the
system.


There are three solutions to this issue:
1. Install APAR IY32280, which eliminates this problem. APAR IY32280 is
included in the 5100-03 and later Recommended Maintenance packages.
2. Use JFS instead of JFS2 on the 32-bit kernel.
For customers who do not require filesystems larger than 1 terabyte,
or individual files larger than 64 gigabytes, this tends to be the
preferred option.
3. Use the 64-bit kernel with JFS2.


Because of this limitation, it is strongly recommended that customers not
use the JFS2 filesystem with the 32-bit kernel.

Missing Maintenance Level Information


The "oslevel -r" command on systems updated from the 4/2002 AIX 5.1 Update
CD may not correctly output 5100-02. This problem is corrected by APAR
IY29612.

Updating AIX 5.1.0 Systems


When updating an existing AIX 5.1.0 system using JFS2 filesystems in the
root volume group (rootvg), you must first install and commit the 5.1.0.1
level kernel update (bos.mp, bos.mp64, or bos.up) using APAR IY19375. The
system must be rebooted in order for the update to take effect before
additional updates are applied. Failure to follow this procedure could
result in a failed update and possibly filesystem corruption.


When updating an AIX 5.1.0 level system to a later level, you should first
update the bos.rte.install fileset, and then install additional updates.

SECURITY: Integrated Login Issue


Users may be able to log into a system with an invalid passord if the
system is configured to use loadable authentication modules, as used in
integrated login methods. This problem occurs when bos.rte.libc is
installed at the 5.1.0.10 or 5.1.0.15 levels.


This failure does not occur using local password files, which is the
default authentication mechanism for AIX, or when using NIS.


This problem is fixed by APAR IY26302 in bos.rte.libc 5.1.0.16.


To determine the level of bos.rte.libc installed on your system, use the
command:
lslpp -L bos.rte.libc

Performance Regression


APAR IY25375 (bos.mp, bos.mp64, or bos.up 5.1.0.15) introduced a 7%
regression in JFS2 filesystem performance. The performance can be regained
by installing APAR IY25793.

IDE CD-ROM Driver Update Required


One of the following AIX device driver updates is required for the IDE
CD-ROM drive (feature 2633) on the 7028 models 6C1 and 6E1. Without the
update, data errors can occur on the CD-ROM drive.



AIX Release APAR Number Fileset Name Fileset
Level

4.3 IY24671 devices.pci.ad100501.rte 4.3.3.2


5.1 IY24696 devices.pci.ad100501.rte 5.1.0.15







Note that APAR IY24696 on AIX 5.1 was initially fixed in
devices.pci.ad100501.rte 5.1.0.1, but with that update installed, the
CD-ROM drive will not configure. All new orders for APAR IY24696 will
deliver the 5.0.1.15 level update.


To determine if the correct level update is installed, use the command:


lslpp -L devices.pci.ad100501.rte

Stack Overflow Limitation


There is a stack overflow limitation in AIX that can result in a system
hang or crash. This problem has been observed in the following
environments.
32-bit kernel
Workload Management (WLM)
IBM Subsystem Device Driver (SDD)
JFS2 file system on a Fibre Channel attached device


and
32-bit kernel
iptrace running
net_malloc_police enabled
The stack overflow condition can be avoided by eliminating one of the
elements of the environment, such as WLM or iptrace, or by running the
64-bit kernel.

Conflict between krb5.server.rte and Linux Toolbox


krb5.server.rte 1.1.0.0 on the AIX Expansion Pack ships a /usr/lib/libdb.a
file which is not a Berkeley database library. This could cause problems
when building open source software which requires the Berkeley database
interfaces. The Berkely database interfaces may be found in
/opt/freeware/lib.

mksysb Installation Failure


System backups (mksysb) made on systems using JFS2 filesystems in rootvg
will fail to install with an error similar to the following.
mkfs: cannot execute module "/sbin/helpers/jfs2/mkfs".
Check for existence. BOS Install: could not create the / file system.
To circumvent this problem, boot from volume 1 of the AIX 5.1 installation
media and then restore the mksysb tape.


This problem is resolved by APAR IY18859. After installing the updates for
APAR IY18859, you must recreate your mksysb.

Update_all Failure on NIM SPOT


Atempting to do an update_all into a NIM SPOT will fail with a message
similar to the following.
0042-175 c_instspot: An unexpected result was returned by the
"/usr/sbin/installp" command:
See the log file:
/export3/spot/spot_15E/usr/lpp/bos/inst_root/var/adm/ras/nim.installp
for details or use the "showlog" operation.
This problem is resolved by APAR IY19531. The update for APAR IY19531 must
be applied to the NIM master before attempting to apply other updates to a
SPOT.

System Crash Applying Updates


Systems using JFS2 filesystems in rootvg can crash when applying updates
that archive library members. The failure could also occur when using the
'ar' command in a JFS2 filesystem.


This problem is resolved by APAR IY19375 in the following fileset updates.


bos.mp 5.1.0.1
bos.mp64 5.1.0.1
bos.up 5.1.0.1



The updates for APAR IY19375 must be installed separately and the system
must be rebooted before other updates can be safely applied.



HTH

 

[dlanni]

Thanks for the info.

I have purchased AIX 5.1 and just wanted to know when I boot fron the CD do I do a Migration or a full Install, I have check all Hardware and Software on my systenm already and all is compatible with 5L.

I couldn't find and Migration docs from 4.3.3 to 5.1 and was trying to find if there were any.

 

[Yegolev]

we are developing procedures for migrating 4.3.3 to 5.1.0 but it's pretty straightforward. there is no reason to NOT do a migration that we have found. we are using NIM.

we have found that EMC does not support the fibre HBAs we use under AIX 5.1, so we are having to set jumpers on them and install IBM drivers. The HBAs work fine, they are just unsupported.

AIX 5.1 comes with Perl 5.6, while AIX 5.2 comes with Perl 5.8, if that is important. IBM sent us a .bff with 5.8 for our 5.1 machines, however so far I have not gotten LWP to work with the IBM version. Works fine with compiled Perl 5.8, and we are looking at finding out why our Oracle 9.2 install had trouble with Perl 5.6, but then we have that LWP problem again. IBM Certified -- AIX 4.3 Obfuscation

 

[dlanni]

Thanks

I am going to try the Migration today, let you know if I have any problems