Your current Power 7 model and Linux workload
Separate an older ppc64 installation from the ppc64le packages used on newer servers. Current vendor processor requirements can rule out the desired release on Power 7.
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 |
|---|---|
| 710 8231-E1C | Match the capacity change to the actual bottleneck |
| 710 8231-E1D | Match the capacity change to the actual bottleneck |
| 710 8231-E2B | Match the capacity change to the actual bottleneck |
| 710 8268-E1D | Match the capacity change to the actual bottleneck |
| 720 8202-E4B | Match the capacity change to the actual bottleneck |
| 720 8202-E4C | Match the capacity change to the actual bottleneck |
| 720 8202-E4D | Match the capacity change to the actual bottleneck |
| 730 8231-E2B | Match the capacity change to the actual bottleneck |
| 730 8231-E2C | Match the capacity change to the actual bottleneck |
| 730 8231-E2D | Match the capacity change to the actual bottleneck |
| 740 8205-E6B | Match the capacity change to the actual bottleneck |
| 740 8205-E6C | Match the capacity change to the actual bottleneck |
| 740 8205-E6D | Match the capacity change to the actual bottleneck |
| 750 8233-E8B | Match the capacity change to the actual bottleneck |
| 750 8408-E8D | Match the capacity change to the actual bottleneck |
| 755 8236-E8C | Match the capacity change to the actual bottleneck |
| 760 9109-RMD | Match the capacity change to the actual bottleneck |
| 770 9117-MMB | Size each partition and its storage connections |
| 770 9117-MMC | Size each partition and its storage connections |
| 770 9117-MMD | Size each partition and its storage connections |
| 775 9125-F2C | Plan the compute fabric and application together |
| 780 9179-MHB | Size each partition and its storage connections |
| 780 9179-MHC | Size each partition and its storage connections |
| 780 9179-MHD | Size each partition and its storage connections |
| 795 9119-FHB | Size each partition and its storage connections |
| 7R1 8246-L1C | Match the capacity change to the actual bottleneck |
| 7R1 8246-L1D | Match the capacity change to the actual bottleneck |
| 7R1 8246-L1S | Match the capacity change to the actual bottleneck |
| 7R1 8246-L1T | Match the capacity change to the actual bottleneck |
| 7R2 8246-L2C | Match the capacity change to the actual bottleneck |
| 7R2 8246-L2D | Match the capacity change to the actual bottleneck |
| 7R2 8246-L2S | Match the capacity change to the actual bottleneck |
| 7R2 8246-L2T | Match the capacity change to the actual bottleneck |
| 7R4 8248-L4T | Match the capacity change to the actual bottleneck |
| PS700 8406-70Y | Replace chassis dependencies along with the workload |
| PS701 8406-71Y | Replace chassis dependencies along with the workload |
| PS702 8406-71Y | Replace chassis dependencies along with the workload |
| PS703 7891-73X | Replace chassis dependencies along with the workload |
| PS704 7891-74X | Replace chassis dependencies along with the workload |
| p24L 1457-7FL | Replace chassis dependencies along with the workload |
| p260 7895-22X | Replace chassis dependencies along with the workload |
| p260 7895-23A | Replace chassis dependencies along with the workload |
| p260 7895-23X | Replace chassis dependencies along with the workload |
| p270 7954-24X | Replace chassis dependencies along with the workload |
| p460 7895-42X | Replace chassis dependencies along with the workload |
| p460 7895-43X | Replace chassis dependencies along with the workload |
710 8231-E1C: 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 Three or six SAS SFF bays depending on the backplane; 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.
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.
710 8231-E1C catalog details · Choose the installed-release branch · Prepare the migration inventory
710 8231-E1D: 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 Three or six SAS SFF bays depending on the backplane; 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.
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.
710 8231-E1D catalog details · Choose the installed-release branch · Prepare the migration inventory
710 8231-E2B: 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 1.8 TB of internal disk; three or six SAS SFF bays depending on the 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.
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.
710 8231-E2B catalog details · Choose the installed-release branch · Prepare the migration inventory
710 8268-E1D: 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 Three or six internal SFF SAS bays; five low-profile PCIe Gen2 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.
710 8268-E1D catalog details · Choose the installed-release branch · Prepare the migration inventory
720 8202-E4B: 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 SAS SFF drive bays for HDD or SSD; confirm the installed backplane and controller. 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.
720 8202-E4B catalog details · Choose the installed-release branch · Prepare the migration inventory
720 8202-E4C: 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 SAS SFF bays; up to 4.8 TB internal; 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.
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.
720 8202-E4C catalog details · Choose the installed-release branch · Prepare the migration inventory
720 8202-E4D: 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 or eight SAS SFF bays depending on the backplane; 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.
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.
720 8202-E4D catalog details · Choose the installed-release branch · Prepare the migration inventory
730 8231-E2B: 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 1.8 TB of internal disk; three or six SAS SFF bays depending on the 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.
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.
730 8231-E2B catalog details · Choose the installed-release branch · Prepare the migration inventory
730 8231-E2C: 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 Three or six SAS SFF bays depending on the backplane; 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.
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.
730 8231-E2C catalog details · Choose the installed-release branch · Prepare the migration inventory
730 8231-E2D: 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 Three or six SAS SFF bays depending on the backplane; 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.
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.
730 8231-E2D catalog details · Choose the installed-release branch · Prepare the migration inventory
740 8205-E6B: 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 SAS SFF bays, up to 2.4 TB internal; up to 72 disks with four 5802 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 L1022 9786-22H and L1122 9856-22H. Size and qualify the proposed configuration against this workload; these are candidates rather than guaranteed equivalents.
740 8205-E6B catalog details · Choose the installed-release branch · Prepare the migration inventory
740 8205-E6C: 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 4.8 TB internal SSD or HDD; 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.
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.
740 8205-E6C catalog details · Choose the installed-release branch · Prepare the migration inventory
740 8205-E6D: 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 2.5-inch SFF bays and two media bays; up to 7.2 TB internal HDD or SSD. 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.
740 8205-E6D catalog details · Choose the installed-release branch · Prepare the migration inventory
750 8233-E8B: 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 internal 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.
750 8233-E8B catalog details · Choose the installed-release branch · Prepare the migration inventory
750 8408-E8D: 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 SFF SAS bays; six PCIe Gen2 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.
750 8408-E8D catalog details · Choose the installed-release branch · Prepare the migration inventory
755 8236-E8C: 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 internal 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.
755 8236-E8C catalog details · Choose the installed-release branch · Prepare the migration inventory
760 9109-RMD: 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 SFF SAS bays; six PCIe Gen2 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.
760 9109-RMD catalog details · Choose the installed-release branch · Prepare the migration inventory
770 9117-MMB: 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; external 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.
770 9117-MMB catalog details · Choose the installed-release branch · Prepare the migration inventory
770 9117-MMC: 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; external 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.
770 9117-MMC catalog details · Choose the installed-release branch · Prepare the migration inventory
770 9117-MMD: 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; external 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.
770 9117-MMD catalog details · Choose the installed-release branch · Prepare the migration inventory
775 9125-F2C: 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 Dedicated storage nodes and high-speed cluster fabric. 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.
775 9125-F2C catalog details · Choose the installed-release branch · Prepare the migration inventory
780 9179-MHB: 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; external 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.
780 9179-MHB catalog details · Choose the installed-release branch · Prepare the migration inventory
780 9179-MHC: 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; external 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.
780 9179-MHC catalog details · Choose the installed-release branch · Prepare the migration inventory
780 9179-MHD: 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; external 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.
780 9179-MHD catalog details · Choose the installed-release branch · Prepare the migration inventory
795 9119-FHB: 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 Boot and data drives reside in attached 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.
795 9119-FHB catalog details · Choose the installed-release branch · Prepare the migration inventory
7R1 8246-L1C: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R1 8246-L1C catalog details · Choose the installed-release branch · Prepare the migration inventory
7R1 8246-L1D: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R1 8246-L1D catalog details · Choose the installed-release branch · Prepare the migration inventory
7R1 8246-L1S: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R1 8246-L1S catalog details · Choose the installed-release branch · Prepare the migration inventory
7R1 8246-L1T: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R1 8246-L1T catalog details · Choose the installed-release branch · Prepare the migration inventory
7R2 8246-L2C: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R2 8246-L2C catalog details · Choose the installed-release branch · Prepare the migration inventory
7R2 8246-L2D: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R2 8246-L2D catalog details · Choose the installed-release branch · Prepare the migration inventory
7R2 8246-L2S: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R2 8246-L2S catalog details · Choose the installed-release branch · Prepare the migration inventory
7R2 8246-L2T: 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 Three or six internal SFF SAS drives; five low-profile PCIe Gen2 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.
7R2 8246-L2T catalog details · Choose the installed-release branch · Prepare the migration inventory
7R4 8248-L4T: 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 SFF SAS bays; six PCIe Gen2 expansion 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.
7R4 8248-L4T catalog details · Choose the installed-release branch · Prepare the migration inventory
PS700 8406-70Y: 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 internal drive 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.
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.
PS700 8406-70Y catalog details · Choose the installed-release branch · Prepare the migration inventory
PS701 8406-71Y: 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 internal drive 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.
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.
PS701 8406-71Y catalog details · Choose the installed-release branch · Prepare the migration inventory
PS702 8406-71Y: 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, one on each blade internal drive 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.
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.
PS702 8406-71Y catalog details · Choose the installed-release branch · Prepare the migration inventory
PS703 7891-73X: 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 HDD or two SSDs with the interposer internal drive 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.
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.
PS703 7891-73X catalog details · Choose the installed-release branch · Prepare the migration inventory
PS704 7891-74X: 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 HDDs or four SSDs with the interposers internal drive 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.
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.
PS704 7891-74X catalog details · Choose the installed-release branch · Prepare the migration inventory
p24L 1457-7FL: 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 internal HDDs or SSDs; two Flex I/O adapter connectors. 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.
p24L 1457-7FL catalog details · Choose the installed-release branch · Prepare the migration inventory
p260 7895-22X: 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 internal HDDs or SSDs; two Flex I/O adapter connectors. 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.
p260 7895-22X catalog details · Choose the installed-release branch · Prepare the migration inventory
p260 7895-23A: 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 internal HDDs or SSDs; two Flex I/O adapter connectors. 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.
p260 7895-23A catalog details · Choose the installed-release branch · Prepare the migration inventory
p260 7895-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 internal HDDs or SSDs; two Flex I/O adapter connectors. 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.
p260 7895-23X catalog details · Choose the installed-release branch · Prepare the migration inventory
p270 7954-24X: 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 internal HDDs or SSDs; two Flex I/O adapter connectors. 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.
p270 7954-24X catalog details · Choose the installed-release branch · Prepare the migration inventory
p460 7895-42X: 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 internal HDDs or SSDs; four Flex I/O adapter connectors. 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.
p460 7895-42X catalog details · Choose the installed-release branch · Prepare the migration inventory
p460 7895-43X: 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 internal HDDs or SSDs; four Flex I/O adapter connectors. 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.
p460 7895-43X catalog details · Choose the installed-release branch · Prepare the migration inventory
Your installed Linux release on Power 7
A Linux-only PowerLinux model still needs a model-specific distribution and boot check. Rebuild and transfer application data when the architecture changes.
| 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. |
| RHEL 7 | 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 11 / 12 | 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 7
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 7 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.