I was attempting to install the new AIX Runtime Expert on an LPAR today. I found that the base level fileset for this new utility was not included with the supporting Technology Level i.e. TL4 for AIX 6.1.

I was presented with the following 'Requisite Failures' message:

Requisite Failures

------------------

SELECTED FILESETS:The following is a list of filesets that you asked to

install.They cannot be installed until all of their requisite filesets

are also installed.See subsequent lists for details of requisites.

artex.base.rte 6.1.4.1# AIX Runtime Expert

MISSING REQUISITES:The following filesets are required by one or more

of the selected filesets listed above.They are not currently installed

and could not be found on the installation media.

artex.base.rte 6.1.0.0# Base Level Fileset

However, I discovered that the base fileset IS included with the latest Fix Pack for the Virtual I/O Server i.e. FP22 for VIOS 2.1.

I was then able to install the base filesets i.e. the AIX Runtime Expert and the sample profiles. i.e.

artex.base

+ 6.1.4.0AIX Runtime Expert

+ 6.1.4.0AIX Runtime Expert sample profiles

After the filesets installed successfully I needed to then apply the latest level from TL4. e.g.

The trace data shows that IVM is calling the migmover -m end command on the destination partition. That command in turn calls a system call. When everything is in the correct state, that system call will end the migration and cleanup. The problem is it is not being called because the mover has not yet been notified that VASI is in the END state as indicated by the mover's state being: MIG_STATE_COMPLETED. The trace shows this notification arriving a split second after the migmover -m end command was issued.

On a good migration, the mover is notified by VASI of the state change before IVM calls migmover -m. IVM runs migmover -m end once it gets a migration completed message from phyp. If this message is issued about the same time as the message that tells VASI that the migration has ended, a timing issue seems a real possibility.

The problem was fixed in the VIOS code. A new call was added when the "end" state change comes in from IVM/HMC. If the state is complete we are good to go, otherwise we issue an error.”

Installing this fix on my VIOS resolved the problem. My VIOS are running 2.1.1.10-FP21. If you are running FP22 for VIOS 2.1, then you must request a different ifix from IBM support.