Your current Power 10 model and Linux workload
Power 10 meets the processor baseline for RHEL 10 and SLES 16. Exact model support, release level and virtualization requirements still apply; a generation-wide CPU baseline is not a complete certification.
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.
| Current model | Configuration question |
|---|---|
| E1050 9043-MRX | Size each partition and its storage connections |
| E1080 9080-HEX | Size each partition and its storage connections |
| L1022 9786-22H | Check the workload allocation and certification |
| L1024 9786-42H | Check the workload allocation and certification |
| S1012 9028-21B | Match the capacity change to the actual bottleneck |
| S1014 9105-41B | Match the capacity change to the actual bottleneck |
| S1022 9105-22A | Match the capacity change to the actual bottleneck |
| S1022s 9105-22B | Match the capacity change to the actual bottleneck |
| S1024 9105-42A | Match the capacity change to the actual bottleneck |
E1050 9043-MRX: 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.
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.
E1050 9043-MRX catalog details · Choose the installed-release branch · Prepare the migration inventory
E1080 9080-HEX: 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.
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.
E1080 9080-HEX catalog details · Choose the installed-release branch · Prepare the migration inventory
L1022 9786-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.
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.
L1022 9786-22H catalog details · Choose the installed-release branch · Prepare the migration inventory
L1024 9786-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.
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.
L1024 9786-42H catalog details · Choose the installed-release branch · Prepare the migration inventory
S1012 9028-21B: 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.
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.
S1012 9028-21B catalog details · Choose the installed-release branch · Prepare the migration inventory
S1014 9105-41B: 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.
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.
S1014 9105-41B catalog details · Choose the installed-release branch · Prepare the migration inventory
S1022 9105-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.
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.
S1022 9105-22A catalog details · Choose the installed-release branch · Prepare the migration inventory
S1022s 9105-22B: 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.
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.
S1022s 9105-22B catalog details · Choose the installed-release branch · Prepare the migration inventory
S1024 9105-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.
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.
S1024 9105-42A catalog details · Choose the installed-release branch · Prepare the migration inventory
Your installed Linux release on Power 10
Compare a supported distribution upgrade with a rebuild or hardware move. Check the SAP or other application certification separately from the base operating system.
| Installed release or architecture | Planning next step |
|---|---|
| RHEL 8 | Review 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 9 | Review 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 10 | Review 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 15 | Review 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 16 | Review 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 LTS | Review 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. |
Upgrade Linux or add capacity on Power 10
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.
- Compare processor allocations with measured Linux workload demand.
- Review memory capacity separately from processor demand.
- Review the Linux release guide for the installed level and desired destination.
- Ask Midland to compare an OS/capacity upgrade with replacement.
Migration from your Power 10 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.
- Record the source configuration.
- Choose a compatible transfer method.
- Rehearse application recovery and acceptance.
- Agree the rollback decision before new production transactions begin.
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.