Operating environments and minimum software levels
A model’s operating-system list identifies supported environments, not a promise that every release works with every feature. Firmware, adapters and the processor configuration can add requirements. Keep minimum releases with their native-I/O or virtual-I/O context.
Compare Power Systems models or discuss your installed configuration.
IBM i and model-specific partition limits
IBM i combines the operating system with integrated database and system functions. Some Power models restrict IBM i to selected configurations or limit cores per partition. The model’s IBM i CPW and partition limits control the comparison; a larger AIX configuration does not remove those limits.
Compare Power Systems models or discuss your installed configuration.
AIX and native or virtual I/O
AIX is IBM’s UNIX operating system for supported Power systems. Minimum levels can differ between partitions owning physical adapters and partitions using only virtual I/O. Keep the source table’s I/O scope with the stated AIX release and rPerf configuration.
S1124: keep the native-I/O and virtual-I/O-only AIX requirements with their own table rows.
Linux distributions and Power support
Linux support depends on the distribution, release and processor architecture. Red Hat Enterprise Linux and SUSE Linux Enterprise Server have their own supported levels. A Linux-only Power model must not be treated as an IBM i system because a related chassis supports IBM i.
Compare Power Systems models or discuss your installed configuration.
Virtual I/O Server: VIOS
VIOS provides shared physical I/O resources to client logical partitions. A virtual-I/O-only requirement means the client uses that arrangement instead of owning the physical adapter directly. VIOS needs its own compatible release and resources; a client operating-system minimum is a different requirement.
S1122 ERGQ ten-core: review the IBM i virtual-I/O requirement with the partition cap.
Hardware Management Console: HMC
An HMC manages supported Power systems and their partitions. Its supported release must match the server generation and firmware. Include the HMC model or virtual appliance level with a hardware change so management support can be checked along with the operating system.
Compare Power Systems models or discuss your installed configuration.
Logical partitions and allocation limits
An LPAR is a logical partition with assigned processing, memory and I/O resources. Maximum partitions and maximum cores per partition are different limits. The physical server’s total capacity does not establish how much IBM i capacity one LPAR can use.
Compare Power Systems models or discuss your installed configuration.
IBM i software tiers and entitlements
An IBM i software tier identifies the pricing or licensing class associated with the applicable offering. It is separate from CPW and physical cores. Keep the tier with its exact model or configuration and confirm current entitlements before assuming a replacement inherits the same terms.
Power 7 720: compare the processor features with their stated IBM i software tiers.
Red Hat OpenShift on Power
Red Hat OpenShift is a container platform with its own supported Power hardware and software combinations. A model listing OpenShift does not establish support for every platform release. Include the intended release and Linux environment when planning the configuration.
Compare Power Systems models or discuss your installed configuration.
Withdrawal, end of support and replacement planning
Withdrawal from marketing is an ordering milestone. End of support or service is a support milestone. The two dates do not mean the same thing. A recommended replacement is a model comparison starting point; migration still depends on the workload, software and attached hardware.
Compare Power Systems models or discuss your installed configuration.