Your current Power 6 model and Linux workload
Power 6 Linux planning starts with the installed distribution, kernel and architecture. Modern ppc64le media should not be treated as an in-place upgrade of an older big-endian installation.
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 |
|---|---|
| 520 8203-E4A | Match the capacity change to the actual bottleneck |
| 520 9407-M15 | Match the capacity change to the actual bottleneck |
| 520 9408-M25 | Match the capacity change to the actual bottleneck |
| 550 8204-E8A | Match the capacity change to the actual bottleneck |
| 550 9409-M50 | Match the capacity change to the actual bottleneck |
| 560 8234-EMA | Match the capacity change to the actual bottleneck |
| 570 9117-MMA | Size each partition and its storage connections |
| 570 9406-MMA | Size each partition and its storage connections |
| 575 9125-F2A | Plan the compute fabric and application together |
| 595 9119-FHA | Size each partition and its storage connections |
| JS12 7998-60X | Replace chassis dependencies along with the workload |
| JS22 7998-61X | Replace chassis dependencies along with the workload |
| JS23 7778-23X | Replace chassis dependencies along with the workload |
| JS43 7778-23X | Replace chassis dependencies along with the workload |
| Smart Cube 8261-E4S | Match the capacity change to the actual bottleneck |
520 8203-E4A: 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 Six 3.5-inch or eight SFF SAS drives; three PCIe and two PCI-X 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
520 8203-E4A catalog details · Choose the installed-release branch · Prepare the migration inventory
520 9407-M15: 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 Six internal SAS drive positions; five system I/O 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
520 9407-M15 catalog details · Choose the installed-release branch · Prepare the migration inventory
520 9408-M25: 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 Six internal SAS drive positions; five system I/O 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
520 9408-M25 catalog details · Choose the installed-release branch · Prepare the migration inventory
550 8204-E8A: 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 Six 3.5-inch or eight SFF SAS bays; three PCIe and two PCI-X 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
550 8204-E8A catalog details · Choose the installed-release branch · Prepare the migration inventory
550 9409-M50: 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 Six 3.5-inch or eight SFF SAS bays; five system I/O 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
550 9409-M50 catalog details · Choose the installed-release branch · Prepare the migration inventory
560 8234-EMA: 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 Six 3.5-inch SAS bays per enclosure; up to twelve PCI slots across two enclosures. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
560 8234-EMA catalog details · Choose the installed-release branch · Prepare the migration inventory
570 9117-MMA: 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 Six 3.5-inch SAS bays per enclosure; external RIO/12X I/O 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
570 9117-MMA catalog details · Choose the installed-release branch · Prepare the migration inventory
570 9406-MMA: 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 Six internal SAS bays per enclosure; RIO/12X expansion is configuration dependent. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
570 9406-MMA catalog details · Choose the installed-release branch · Prepare the migration inventory
575 9125-F2A: plan the compute fabric and application together
Capture the cluster fabric, scheduler and storage layout. Record cooling and rack dependencies with the current system. The application’s scale-out behavior and recovery design matter as much as a processor comparison.
The catalog’s storage and I/O context is Two internal SFF SAS positions; four PCIe slots per node. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
575 9125-F2A catalog details · Choose the installed-release branch · Prepare the migration inventory
595 9119-FHA: 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 Drives and PCI adapters reside in attached 19-inch or 24-inch I/O 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
595 9119-FHA catalog details · Choose the installed-release branch · Prepare the migration inventory
JS12 7998-60X: replace chassis dependencies along with the workload
Include the BladeCenter or Flex chassis and shared networking in the inventory. Record the actual virtual-I/O provider and storage mappings. Moving the workload to a rack server also means replacing the services supplied by the chassis.
The catalog’s storage and I/O context is Two local SAS drive positions; chassis-connected expansion cards. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
JS12 7998-60X catalog details · Choose the installed-release branch · Prepare the migration inventory
JS22 7998-61X: replace chassis dependencies along with the workload
Include the BladeCenter or Flex chassis and shared networking in the inventory. Record the actual virtual-I/O provider and storage mappings. Moving the workload to a rack server also means replacing the services supplied by the chassis.
The catalog’s storage and I/O context is One local SAS drive positions; chassis-connected expansion cards. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
JS22 7998-61X catalog details · Choose the installed-release branch · Prepare the migration inventory
JS23 7778-23X: replace chassis dependencies along with the workload
Include the BladeCenter or Flex chassis and shared networking in the inventory. Record the actual virtual-I/O provider and storage mappings. Moving the workload to a rack server also means replacing the services supplied by the chassis.
The catalog’s storage and I/O context is One local SAS drive positions; chassis-connected expansion cards. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
JS23 7778-23X catalog details · Choose the installed-release branch · Prepare the migration inventory
JS43 7778-23X: replace chassis dependencies along with the workload
Include the BladeCenter or Flex chassis and shared networking in the inventory. Record the actual virtual-I/O provider and storage mappings. Moving the workload to a rack server also means replacing the services supplied by the chassis.
The catalog’s storage and I/O context is Two local SAS drive positions; chassis-connected expansion cards. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
JS43 7778-23X catalog details · Choose the installed-release branch · Prepare the migration inventory
Smart Cube 8261-E4S: 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 Shared 520 service family has 3.5-inch and SFF SAS backplanes; identify the installed one. 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.
If the destination uses little-endian packages while this workload uses big-endian binaries, plan an application rebuild and a supported data conversion rather than an unchanged root-disk restore.
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.
Smart Cube 8261-E4S catalog details · Choose the installed-release branch · Prepare the migration inventory
Your installed Linux release on Power 6
Preserve a bootable recovery set and identify application source or vendor builds before planning the target. Include the older storage and console dependencies.
| Installed release or architecture | Planning next step |
|---|---|
| Older Linux releases | 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. |
| ppc64, ppc64le and byte order | 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 6
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 6 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.