[PaulClayton]

In our production environment, we have an eServer running AIX 5.3 TL06.
We take a monthly mksysb, and send this to our DR site, which is a pSeries P55a.
On attempting to build this paritition from a mksysb, with the lpp source, the mksysb builds with no problems, except the following messages appear at the end.
Missing file sets
~~~~~~~~~~
devices.chrp_lpar.base
devices.vdevice.l-lan
devices.vdevice.vty
devices.vsci.disk

On reboot, the display hangs at the loading kernel page.
Other partitions we build, go from lpar to lpar and work fine. However this unit is a standalone unit, that we want to push to lpar. From what I can see, the above drivers do not exist in the lpp source or the distro CD.
Nim_move_up seems an option, but is not quite what we are looking for, as we would be assuming a non-functional system to recover.

Any thoughts, etc.

[ross.mather]

An mksysb is designed to restore to identical hardware that it came from. If it works for anything else great.

You've hit that hole. I would suggest trying to restore the mksysb with a full lpp_source available to install any needed device drivers.

It could also be stalling because it can't find the consloe device properly - the older server will have a serial console and the LPAR a vty for the console.

As you have a DR facility you could also simply install the DR LPAR from scratch and configure it for the applicaion again.

[duke900ssd]

Seems like your lpp source is incomplete, it is missing the LPAR / virtual device drivers required to deploy your mksysb on to an LPAR'd environment.

As Ross says, you need a full lpp source to do this type of system migration with a mksysb over nim.

Even then you will also need a little bit of luck because this in not what nim / mksysb was designed for.

[steevojb]

Hi There,

For current p5* You should be able to restore any mksysb onto any model booting from a higher or equal TL/ML CD/DVD. There is an option to ensure the later filesets are not applied following restore.

Steve