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

Power 8 Linux upgrades by current model

What can your Power 8 Linux system move to?

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

Your current Power 8 model and Linux workload

RHEL 9 requires Power 9 or later; RHEL 10 and SLES 16 require Power 10 or later. Canonical identifies Ubuntu 20.04 LTS as its last Power 8 release. Check eligible RHEL 8 or SLES 15 configurations in the model maps.

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 8 Linux model planning
Current modelConfiguration question
CS821 8005-12NTreat the appliance stack as part of the move
CS822 8005-22NTreat the appliance stack as part of the move
E850 8408-E8ESize each partition and its storage connections
E850C 8408-44ESize each partition and its storage connections
E870 9119-MMESize each partition and its storage connections
E870C 9080-MMESize each partition and its storage connections
E880 9119-MHESize each partition and its storage connections
E880C 9080-MHESize each partition and its storage connections
S812 8284-21AConfirm the processor edition and direct I/O
S812L 8247-21LMatch the capacity change to the actual bottleneck
S812LC 8348-21CIdentify the boot firmware and virtualization layer
S814 8286-41AMatch the capacity change to the actual bottleneck
S821LC 8001-12CIdentify the boot firmware and virtualization layer
S822 8284-22AMatch the capacity change to the actual bottleneck
S822L 8247-22LMatch the capacity change to the actual bottleneck
S822LC 8001-22CKeep accelerator dependencies with the application
S822LC 8335-GCAKeep accelerator dependencies with the application
S822LC 8335-GTAKeep accelerator dependencies with the application
S822LC 8335-GTBKeep accelerator dependencies with the application
S824 8286-42AMatch the capacity change to the actual bottleneck
S824L 8247-42LMatch the capacity change to the actual bottleneck

CS821 8005-12N: treat the appliance stack as part of the move

Identify the installed hyperconverged software and guest workloads before choosing a replacement. Appliance support and management software have their own requirements. A standard Linux host installation is not a substitute for the appliance migration procedure.

The catalog’s storage and I/O context is Confirm local drives, accelerator use, and software-defined storage layout. 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.

CS821 8005-12N catalog details · Choose the installed-release branch · Prepare the migration inventory

CS822 8005-22N: treat the appliance stack as part of the move

Identify the installed hyperconverged software and guest workloads before choosing a replacement. Appliance support and management software have their own requirements. A standard Linux host installation is not a substitute for the appliance migration procedure.

The catalog’s storage and I/O context is Confirm local drives, accelerator use, and software-defined storage layout. 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.

CS822 8005-22N catalog details · Choose the installed-release branch · Prepare the migration inventory

E850 8408-E8E: 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 Confirm internal drives and attached enterprise storage. 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.

E850 8408-E8E catalog details · Choose the installed-release branch · Prepare the migration inventory

E850C 8408-44E: 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 Confirm internal drives and attached enterprise storage. 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.

E850C 8408-44E catalog details · Choose the installed-release branch · Prepare the migration inventory

E870 9119-MME: 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 SAN and attached storage; confirm adapters, drawers, and VIOS ownership. 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.

E870 9119-MME catalog details · Choose the installed-release branch · Prepare the migration inventory

E870C 9080-MME: 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 SAN and attached storage; confirm adapters, drawers, and VIOS ownership. 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.

E870C 9080-MME catalog details · Choose the installed-release branch · Prepare the migration inventory

E880 9119-MHE: 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 SAN and attached storage; confirm adapters, drawers, and VIOS ownership. 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.

E880 9119-MHE catalog details · Choose the installed-release branch · Prepare the migration inventory

E880C 9080-MHE: 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 SAN and attached storage; confirm adapters, drawers, and VIOS ownership. 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.

E880C 9080-MHE catalog details · Choose the installed-release branch · Prepare the migration inventory

S812 8284-21A: confirm the processor edition and direct i/o

Keep the one-core IBM i configuration separate from the four-core AIX/Linux configuration. The S812 has direct-I/O and partition restrictions; do not build a migration around an assumed VIOS layout.

The catalog’s storage and I/O context is Confirm the installed SAS backplane, drive format, and expansion drawers. 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.

S812 8284-21A catalog details · Choose the installed-release branch · Prepare the migration inventory

S812L 8247-21L: 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 SFF-3 bays or six SFF-3 plus six 1.8-inch SSD 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.

S812L 8247-21L catalog details · Choose the installed-release branch · Prepare the migration inventory

S812LC 8348-21C: 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 drive carrier, backplane, and software-defined storage layout. 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.

S812LC 8348-21C catalog details · Choose the installed-release branch · Prepare the migration inventory

S814 8286-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 Up to 32 TB internal storage; eight PCIe Gen3 slots. 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.

S814 8286-41A catalog details · Choose the installed-release branch · Prepare the migration inventory

S821LC 8001-12C: 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 local drives, accelerator use, and software-defined storage layout. 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.

S821LC 8001-12C catalog details · Choose the installed-release branch · Prepare the migration inventory

S822 8284-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 SAS SFF and selected SSD options; confirm the installed backplane 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.

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.

S822 8284-22A catalog details · Choose the installed-release branch · Prepare the migration inventory

S822L 8247-22L: 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 SFF SAS and SSD choices; confirm carrier, backplane, 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.

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.

S822L 8247-22L catalog details · Choose the installed-release branch · Prepare the migration inventory

S822LC 8001-22C: 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 local drives, accelerator use, and software-defined storage layout. 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.

S822LC 8001-22C catalog details · Choose the installed-release branch · Prepare the migration inventory

S822LC 8335-GCA: 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 local drives, accelerator use, and software-defined storage layout. 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.

S822LC 8335-GCA catalog details · Choose the installed-release branch · Prepare the migration inventory

S822LC 8335-GTA: 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 local drives, accelerator use, and software-defined storage layout. 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.

S822LC 8335-GTA catalog details · Choose the installed-release branch · Prepare the migration inventory

S822LC 8335-GTB: 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 local drives, accelerator use, and software-defined storage layout. 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.

S822LC 8335-GTB catalog details · Choose the installed-release branch · Prepare the migration inventory

S824 8286-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 SFF bays standard or 18 SFF bays with eight 1.8-inch SSD 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.

S824 8286-42A catalog details · Choose the installed-release branch · Prepare the migration inventory

S824L 8247-42L: 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 Confirm the internal bay, carrier, backplane, and attached expansion 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.

S824L 8247-42L catalog details · Choose the installed-release branch · Prepare the migration inventory

Your installed Linux release on Power 8

Record whether the source is ppc64 or ppc64le. A capacity change cannot make a newer distribution’s processor baseline disappear.

Power 8: 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.
SLES 11 / 12Review 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 8

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 8 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.