An existing client LPAR has been manually moved from one physical machine to another. The administrator updated the SAN zoning to deallocate from the source VIO Server and allocate to the…

A recreated LPAR profile on the HMC does not retain the original boot device list, so upon first activation the LPAR enters SMS (System Management Services) and halts waiting for a boot device selection. The administrator must navigate SMS to select the VIO Server-mapped virtual disk as the boot device before AIX can be loaded. This is a required and expected manual step any time an LPAR profile is built from scratch on a new HMC without importing the original profile data.

While the system clock may drift during a physical migration, AIX synchronizes time via NTP automatically on boot and manual clock correction is not a prerequisite to activating and booting the LPAR.

The terminal type for the HMC virtual terminal session is determined by the HMC client and does not require any manual correction as part of the LPAR activation process.

Importing non-root volume groups is an AIX-level varyon operation performed after the OS has fully booted; it cannot be the first required manual step because the system cannot reach the OS prompt until a boot device is first selected.