AS400 to IBM Power 11 Partners
(888) 682-5335

Power 9 Linux upgrades by current model

What can your Power 9 Linux system move to?

Compare OS and capacity changes for your Power 9 Linux workload. Start with the exact model and installed release so Midland can scope an upgrade or a suitable replacement.

Your current Power 9 model and Linux workload

Power 9 meets the RHEL 9 processor baseline but not the Power 10 baseline for RHEL 10 or SLES 16. Canonical supports Power 9 in Ubuntu 22.04 LTS and later eligible releases.

Choose the exact catalog identity below for its planning notes. The list identifies assessment starting points; eligibility still depends on the installed edition and configuration.

Power 9 Linux model planning
Current modelConfiguration question
AC922 8335-GTCKeep accelerator dependencies with the application
AC922 8335-GTGKeep accelerator dependencies with the application
AC922 8335-GTHKeep accelerator dependencies with the application
AC922 8335-GTWKeep accelerator dependencies with the application
AC922 8335-GTXKeep accelerator dependencies with the application
E950 9040-MR9Size each partition and its storage connections
E980 9080-M9SSize each partition and its storage connections
H922 9223-22HCheck the workload allocation and certification
H922S 9223-22SCheck the workload allocation and certification
H924 9223-42HCheck the workload allocation and certification
H924S 9223-42SCheck the workload allocation and certification
IC922 9183-22XKeep accelerator dependencies with the application
L922 9008-22LIdentify the boot firmware and virtualization layer
LC921 9006-12PIdentify the boot firmware and virtualization layer
LC922 5104-22CIdentify the boot firmware and virtualization layer
LC922 9006-22CIdentify the boot firmware and virtualization layer
LC922 9006-22PIdentify the boot firmware and virtualization layer
S914 9009-41AMatch the capacity change to the actual bottleneck
S914 9009-41GMatch the capacity change to the actual bottleneck
S922 9009-22AMatch the capacity change to the actual bottleneck
S922 9009-22GMatch the capacity change to the actual bottleneck
S924 9009-42AMatch the capacity change to the actual bottleneck
S924 9009-42GMatch the capacity change to the actual bottleneck

AC922 8335-GTC: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Confirm drive and accelerator carrier configuration. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

AC922 8335-GTC catalog details · Choose the installed-release branch · Prepare the migration inventory

AC922 8335-GTG: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Confirm drive and accelerator carrier configuration. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

AC922 8335-GTG catalog details · Choose the installed-release branch · Prepare the migration inventory

AC922 8335-GTH: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Two SFF drive bays with optional PCIe NVMe. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

AC922 8335-GTH catalog details · Choose the installed-release branch · Prepare the migration inventory

AC922 8335-GTW: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Confirm drive and accelerator carrier configuration. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

AC922 8335-GTW catalog details · Choose the installed-release branch · Prepare the migration inventory

AC922 8335-GTX: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Two SFF drive bays with optional PCIe NVMe. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

AC922 8335-GTX catalog details · Choose the installed-release branch · Prepare the migration inventory

E950 9040-MR9: size each partition and its storage connections

Capture the busy periods and resource allocation for each logical partition. Review external storage, multipath software and management-console levels. A consolidation plan must retain the isolation and recovery behavior the applications need.

The catalog’s storage and I/O context is Enterprise storage and I/O drawers; confirm the installed topology. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review E1050 9043-MRX and E1150 9043-MRU. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

E950 9040-MR9 catalog details · Choose the installed-release branch · Prepare the migration inventory

E980 9080-M9S: size each partition and its storage connections

Capture the busy periods and resource allocation for each logical partition. Review external storage, multipath software and management-console levels. A consolidation plan must retain the isolation and recovery behavior the applications need.

The catalog’s storage and I/O context is Storage and I/O scale with node and drawer topology. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review E1050 9043-MRX and E1150 9043-MRU. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

E980 9080-M9S catalog details · Choose the installed-release branch · Prepare the migration inventory

H922 9223-22H: check the workload allocation and certification

Keep model-specific allocation limits beside the applications that use the server. For SAP or other certified software, confirm the exact application, database and OS combination. A compatible Linux or AIX kernel is only one part of that check.

The catalog’s storage and I/O context is SAS and NVMe options; confirm installed backplane. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

H922 9223-22H catalog details · Choose the installed-release branch · Prepare the migration inventory

H922S 9223-22S: check the workload allocation and certification

Keep model-specific allocation limits beside the applications that use the server. For SAP or other certified software, confirm the exact application, database and OS combination. A compatible Linux or AIX kernel is only one part of that check.

The catalog’s storage and I/O context is SAS and NVMe options; confirm installed backplane. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

H922S 9223-22S catalog details · Choose the installed-release branch · Prepare the migration inventory

H924 9223-42H: check the workload allocation and certification

Keep model-specific allocation limits beside the applications that use the server. For SAP or other certified software, confirm the exact application, database and OS combination. A compatible Linux or AIX kernel is only one part of that check.

The catalog’s storage and I/O context is SAS and NVMe options; confirm installed backplane. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

H924 9223-42H catalog details · Choose the installed-release branch · Prepare the migration inventory

H924S 9223-42S: check the workload allocation and certification

Keep model-specific allocation limits beside the applications that use the server. For SAP or other certified software, confirm the exact application, database and OS combination. A compatible Linux or AIX kernel is only one part of that check.

The catalog’s storage and I/O context is SAS plus supported U.2 NVMe options. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

H924S 9223-42S catalog details · Choose the installed-release branch · Prepare the migration inventory

IC922 9183-22X: keep accelerator dependencies with the application

Record GPU or accelerator features and their driver/runtime versions. Confirm whether the workload requires NVLink, a specific CUDA build or a certified analytics stack. A newer general-purpose Power server is not automatically an equivalent accelerator platform.

The catalog’s storage and I/O context is Linux server storage; confirm carrier, controller, and sector format. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

Choose the destination from the application or appliance certification first. Request a model comparison after the required accelerator and software combination has been established.

IC922 9183-22X catalog details · Choose the installed-release branch · Prepare the migration inventory

L922 9008-22L: identify the boot firmware and virtualization layer

Record whether the host uses OPAL, KVM, PowerVM or another documented arrangement. A PowerVM partition restore and a bare-metal or KVM installation use different boot and device assumptions.

The catalog’s storage and I/O context is Eight SFF bays with backplane and expansion options. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

L922 9008-22L catalog details · Choose the installed-release branch · Prepare the migration inventory

LC921 9006-12P: identify the boot firmware and virtualization layer

Record whether the host uses OPAL, KVM, PowerVM or another documented arrangement. A PowerVM partition restore and a bare-metal or KVM installation use different boot and device assumptions.

The catalog’s storage and I/O context is Four SAS or SATA bays plus four front NVMe bays. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

LC921 9006-12P catalog details · Choose the installed-release branch · Prepare the migration inventory

LC922 5104-22C: identify the boot firmware and virtualization layer

Record whether the host uses OPAL, KVM, PowerVM or another documented arrangement. A PowerVM partition restore and a bare-metal or KVM installation use different boot and device assumptions.

The catalog’s storage and I/O context is Confirm from installed backplane and carrier. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

LC922 5104-22C catalog details · Choose the installed-release branch · Prepare the migration inventory

LC922 9006-22C: identify the boot firmware and virtualization layer

Record whether the host uses OPAL, KVM, PowerVM or another documented arrangement. A PowerVM partition restore and a bare-metal or KVM installation use different boot and device assumptions.

The catalog’s storage and I/O context is Confirm from installed backplane and carrier. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

LC922 9006-22C catalog details · Choose the installed-release branch · Prepare the migration inventory

LC922 9006-22P: identify the boot firmware and virtualization layer

Record whether the host uses OPAL, KVM, PowerVM or another documented arrangement. A PowerVM partition restore and a bare-metal or KVM installation use different boot and device assumptions.

The catalog’s storage and I/O context is 12 SAS or SATA bays plus four front NVMe bays. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

LC922 9006-22P catalog details · Choose the installed-release branch · Prepare the migration inventory

S914 9009-41A: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is SAS backplane options; capacity depends on processor and backplane. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S914 9009-41A catalog details · Choose the installed-release branch · Prepare the migration inventory

S914 9009-41G: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is SAS and U.2 NVMe options; confirm the installed backplane. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S914 9009-41G catalog details · Choose the installed-release branch · Prepare the migration inventory

S922 9009-22A: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is Eight SFF bays with backplane and expansion options. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S922 9009-22A catalog details · Choose the installed-release branch · Prepare the migration inventory

S922 9009-22G: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is SAS plus up to 14 NVMe devices, subject to configuration. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S922 9009-22G catalog details · Choose the installed-release branch · Prepare the migration inventory

S924 9009-42A: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is 12 or 18 SFF SAS bays with storage and expansion options. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S924 9009-42A catalog details · Choose the installed-release branch · Prepare the migration inventory

S924 9009-42G: match the capacity change to the actual bottleneck

Compare processor use, memory pressure and storage response before choosing an upgrade. Record the installed processor feature and attached devices so the quote addresses the current workload rather than the model’s maximum specification.

The catalog’s storage and I/O context is SAS plus up to 14 NVMe devices, subject to configuration. Check the installed adapters and recovery devices against the destination; their presence on the source does not establish reuse eligibility.

Record the distribution’s full release and the output of uname -m. Then match the package architecture and boot arrangement to the Power Linux architecture guide.

For a replacement comparison, review L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.

S924 9009-42G catalog details · Choose the installed-release branch · Prepare the migration inventory

Your installed Linux release on Power 9

Separate PowerVM servers from OpenPOWER, accelerator and Linux-only variants. The target’s boot firmware, hypervisor and application certification still control.

Power 9: Linux release starting points
Installed release or architecturePlanning next step
RHEL 7Review the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.
RHEL 8Review the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.
RHEL 9Review the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.
SLES 15Review the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.
Ubuntu LTSReview the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.
ppc64, ppc64le and byte orderReview the exact source release and hardware requirements before selecting the target. This branch is an assessment topic, not confirmation that every listed model runs the release.

Find the installed release information.

Upgrade Linux or add capacity on Power 9

Start with the application result you need. A supported OS change can keep the existing server useful; a capacity change can address resource pressure. Neither establishes a supported release on hardware the vendor excludes.

Migration from your Power 9 Linux system

Moving to another server is a separate task from updating the OS. The plan must qualify the destination, transfer the workload and prove the application works before the final switch.

  1. Record the source configuration.
  2. Choose a compatible transfer method.
  3. Rehearse application recovery and acceptance.
  4. Agree the rollback decision before new production transactions begin.

Return to Linux upgrades · Plan the Linux migration

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.