Record the full AIX release, TL and SP
Use oslevel -s and keep the full result. It identifies the AIX release, Technology Level (TL), Service Pack (SP) and build date. Record prtconf output with the exact machine type and model. A label such as AIX 7.2 leaves out the maintenance level that can enable the destination.
Also record the logical partition’s processor compatibility mode and its physical or virtual I/O ownership. The operating system can support the processor while the adapters require a different maintenance level.
| Installed AIX family | Useful planning boundary |
|---|---|
| AIX 7.3 | Eligible Power 8 and later hardware; match model, TL/SP and I/O. |
| AIX 7.2 | Eligible Power 7 and later hardware; Power 11 requires specific later levels. |
| AIX 7.1 | Legacy and compatibility-mode assessment; do not assume unchanged Power 11 eligibility. |
| AIX 5.3 / 6.1 | Check application dependencies, recovery media and a supported OS/hardware sequence. |
AIX 7.3: qualify the TL and the server
AIX 7.3 requires eligible Power 8 or later processors. It is not an OS-only destination for Power 5, Power 6 or Power 7 systems. IBM excludes the Power 8 CS821 and CS822 hyperconverged systems from AIX 7.3 support.
On Power 11, IBM’s processor guidance enables native Power 11 mode with AIX 7.3 TL3 SP1 or later. Earlier mapped levels use older compatibility modes. The exact server and I/O map can add requirements, so use that map to qualify the installation rather than applying the processor baseline to every model.
IBM describes OS migration installations from earlier AIX environments, including eligible older starting releases. Review the target TL’s release notes and pre-migration checks to establish the exact sequence. A direct software migration option does not mean the source hardware can boot the target.
Read the AIX 7.3 TL4 release notes · Read IBM’s AIX OS migration guidance
AIX 7.2: match the technology level to the hardware
AIX 7.2 requires eligible Power 7 or later hardware. A Power 7 owner may therefore compare a 7.2 software upgrade with replacing hardware for 7.3. Later Power generations can require higher TL/SP levels and specific I/O arrangements.
For Power 11, keep the exact virtual-I/O or physical-I/O requirement from the model map. AIX 7.2 TL5 at one service pack must not be treated as interchangeable with every later service pack.
Read AIX 7.2 TL5 release notes · Choose the exact IBM model map
AIX 7.1: keep compatibility-mode exceptions explicit
AIX 7.1 workloads need their exact TL/SP, hardware and support arrangement recorded. Selected newer servers can run mapped 7.1 levels in older processor compatibility modes. Physical adapter ownership and virtual-I/O-only requirements can differ.
Power 10 AIX 7.1 support is a qualified virtual-I/O case, not an assurance that every old adapter or partition layout can move unchanged. For Power 11, plan a qualified 7.2 or 7.3 environment rather than assuming 7.1 can be carried forward.
Plan the AIX hardware move after the source and destination requirements are established.
AIX 5.3 and 6.1: preserve recovery before changing releases
Record application builds and middleware dependencies along with the OS. Preserve a tested system backup and separate backups of application data volumes. Confirm access to the installation media and filesets needed for the selected sequence.
A newer AIX release may support an OS migration from an older starting point on hardware that can boot the target. Use IBM’s target release notes and pre-migration checks to confirm that case. Do not turn a software install option into a blanket direct move to current hardware.
Choose the current model guide and assemble the legacy workload inventory.
Native I/O, virtual I/O and processor mode are different checks
A partition with physical I/O owns its adapters. A virtual-I/O client receives devices through Virtual I/O Server (VIOS). IBM publishes separate AIX maps for these arrangements because their minimum levels can differ.
Processor compatibility mode controls which processor features the partition can use. It does not supply a missing device driver or turn an unsupported model into an eligible server. Capture both the mode and I/O ownership before a migration quote.
AIX TL updates, fix support and a usable fallback
A newer Service Pack within the chosen TL is a different change from moving to another AIX release. IBM’s TL lifecycle has its own end-of-fix-support dates; it is not the same as the release’s service lifecycle or the customer’s contract.
Before a TL or release change, preserve a tested system backup. IBM documents alternate-disk and NIM methods that can retain the prior root volume group. Qualify the method and rehearse its fallback; it does not by itself reverse new transactions in application data volumes.
Check current AIX TL fix-support dates · Plan application-aware rollback · Discuss the AIX upgrade with Midland
Sources and release checks
Guidance checked October 21, 2026. Midland catalog identities stay with their exact model. Hardware eligibility, software maintenance and application certification need separate checks for the installed configuration.