Family 9043+01 IBM Power E1050 enterprise midrange technology-based server

IBM United States Sales Manual
Revised: December 6, 2022


Table of contents
Product life cycle datesProduct life cycle datesTechnical descriptionTechnical description
AbstractAbstractPublicationsPublications
HighlightsHighlightsFeaturesFeatures
DescriptionDescriptionAccessoriesAccessories
ModelsModelsSuppliesSupplies


Product life cycle dates

Top rule

Type Model Announced Available Marketing Withdrawn Service Discontinued
9043-MRX 2022-07-12 2022-07-22 - -


Back to topBack to top

Abstract

Top rule

Power enterprise servers combines cloud management with leadership performance, scale, reliability, availability, and security to efficiently run the most data-intensive, mission-critical workloads.

This Power E1050 (9043-MRX) server is designed to improve scale performance and security while delivering class-leading reliability. This design responds faster to business demands, protects data from core to cloud, and streamlines insights and automation. The enterprise family of systems can help deliver business agility by extending mission-critical workloads across a hybrid cloud with increased flexibility.

  • Respond faster to business demands: The Power10 processor delivers higher levels of performance as compared to IBM Power9 for the same workloads without increasing energy or carbon footprint, enabling more efficient scaling1. Power Private Cloud with Dynamic Capacity includes metering of Linux, OpenShift, and AIX environments for flexible consumption consistently across public, private, and hybrid cloud when combined with the Power E1050.
  • Protect data from core to cloud: You can support end- to-end security with simplified encryption using memory encryption at the processor level--without management overhead or performance impact. Power10 can also help you to stay ahead of future threats with support for post-quantum cryptography and fully homomorphic encryption.
  • Streamline insights and automation: You can deduce insights faster as compared to Power9 from enhanced in-core AI inferencing capability with no additional specialized hardware required. You can extract insights from your most sensitive data where it resides, eliminating the time and risk of data movement.
  • Maximize availability and reliability: You can help ensure your business stays up and running with built-in advanced recovery and self-healing for infrastructure redundancy and disaster recovery (DR) in IBM Cloud.

The Power E1050 server includes the following additional software and services:

  • IBM Cloud Management Console (CMC) for Power. CMC is a cloud-native platform that provides apps that give powerful insights into your Power infrastructure across data centers and geographies. With no additional software or infrastructure setup, you can get single pane of glass views of your inventory, software levels, resource capacity utilization, as well as launch-in-context of your on-premises software, such as IBM PowerVC and IBM PowerHA. Each new Power E1050 server purchase includes 12 months of CMC service, which can be renewed. For more information, visit IBM Cloud Management Console website.
  • Open source cloud automation and configuration tooling for AIX. IBM has expanded its commitment to keep key open source cloud management packages updated and to provide timely security fixes to enable you to leverage open source skills. The Power E1050 enables you to take advantage of key packages to enable cloud automation, including:
  • chef automation for configuration, deployment, and management. IBM is collaborating with clients in this community to provide useful resources for using chef with AIX systems.
  • yum package management is available with repository access from both ftp and https protocols. rpm is also updated to enable automatic dependency discovery.
  • cloud-init and all dependencies are available in the repository and includes support for licensed AIX users. For more information, see the AIX Toolbox for Open Source Software website.

Securely connect system-of-record workloads and data-to-cloud native applications. IBM API and IBM WebSphere Connect provide secure connectivity to cloud-based applications, giving you the ability to rapidly develop new applications and services, thereby helping accelerate your time to value. IBM's Power to Cloud services can help you get started with these solutions and in designing new applications that leverage IBM Cloud. Cloud enables you to rapidly build, deploy, and manage your cloud applications, while tapping a growing ecosystem of available services and runtime frameworks. To learn more about all the new cloud capabilities that come with the Power E1050 server, see the IBM Power Enterprise Cloud Index website.

  • eBMC is built on Open BMC Linux Foundation Project, with industry collaboration and industry-standard APIs.
  • Power to Cloud Rewards Program. The Power to Cloud Rewards Program helps you design, build, and deliver cloud platforms on Power. Clients purchasing a Power E1050 server earn 5,000 IBM Power to Cloud Reward Program points per system. The points can be used for a range of services to transform traditional IT platforms to private and hybrid cloud platforms. Power to Cloud Reward Program service offerings leverage the proven expertise of IBM Systems Lab Services consultants. Visit ibm.biz/PowertoCloud or contact your IBM representative, IBM Business Partner, or ibmsls@us.ibm.com for full program details.

Power E1050 hardware components

The Power E1050 server delivers a high-performing and reliable four-socket system, with simultaneous multithreading of up to eight threads per core (SMT8). Each Power E1050 server's Power10 dual-chip module delivers 409 GB/sec of memory bandwidth per socket. I/O bandwidth is also increased to double that of the predecessor Power9 systems with the introduction of PCIe Gen5 integrated controllers.

The Power E1050 server utilizes the following Power10 processor options:

  • Twelve-core with up to 48 cores typical 3.35-4.0 GHz (max)
  • Eighteen-core with up to 72 cores typical 3.2--4.0 GHz (max)
  • Twenty-four-core with up to 96 cores typical 2.95--3.90 GHz (max)

A minimum of two processor modules must be installed in each system, with a minimum quantity of one processor module's cores activated.

A Power E1050 server supports the following memory options:

  • 64 GB (2x32GB) DDR4 DDIMMs, or
  • 128 GB (2x64GB) DDR4 DDIMMs, or
  • 256 GB (2x128GB) DDR4 DDIMMs, or
  • 512 GB (2x256GB) DDR4 DDIMMs

E1050 provides 16 DDIMMs per socket to enable a maximum configuration of 16 TB. Minimum of 4 DDIMM's per sockect must be installed.

A minimum of 50% or 256 GB, whichever is higher, of installed memory must be activated.

The PCIe capabilities provide up to 11 PCIe slots:

  • Two PCIe Gen5 x8
  • Three PCIe Gen4 x8
  • Six PCIe Gen4 x16 or Gen5 8x

PCIe slots support concurrent maintenance (hot plug).

Additional PCIe adapters can be attached through up to four PCIe I/O expansion drawers, providing up to 48 additional PCIe Gen3 slots.

The external USB DVD plugs into one of the two front USB ports.

The Power E1050 server comes standard with phase-redundant power regulators for processors, memory, disk, and I/O. Hot-plug, redundant power supplies and a hot-plug time-of-day battery are also standard, and AMM for Hypervisor is available as an option.

Model abstract 9043-MRX

The IBM Power E1050 server (9043-MRX) is an enhanced enterprise class four-socket, 4U server that provides massive scaleability and flexibility. This system is agile and delivers extreme density in an energy-efficient design with superior reliability and resiliency. It will provide enterprise clients with a secure environment that balances mission-critical and modernization applications to deliver a frictionless hybrid cloud experience.

Power E1050 features include:

  • IBM Power10 processor modules with 12, 18, or 24 cores options.
    • Twelve-core processor modules provide up to 48 cores per system typical 3.35-4.0 GHz (max).
    • Eighteen-core processor modules provide up to 72 cores per system typical 3.20--4.0 GHz (max).
    • Twenty-four-core processor modules provide up to 96 cores per system typical 2.95--3.90 GHz (max).
  • Enterprise class 4U differential dual in-line memory module (DDIMM) memory technology with enhanced reliability, availability, and serviceability with 256 GB to 16 TB of memory capacity.
    • A two-processor module configuration provides 32 DDIMM slots and a maximum of 8 TB.
    • A three-processor module configuration provides 48 DDIMM slots and a maximum of 12 TB.
    • A four-processor module configuration provides 64 DDIMM slots and a server maximum of 16 TB.
  • Peripheral Component Interconnect Express (PCIe) slots.
    • System unit supports up to 11 PCIe Gen5/4 slots.
    • One PCIe Gen3 slot reserved for default Ethernet adapter.
    • PCIe I/O expansion drawers support up to 40 additional PCIe slots.
  • Ten nonvolatile memory express (NVMe) backplanes.
  • Integrated USB controller provides two front and two rear USB ports.
  • Additional storage can be attached.
    • Up to 1,536 SFF-2 bays for hard disk drives (HDDs) and solid-state drives (SSDs) with 64 EXP24SX I/O drawer.
    • Fibre Channel (FC) and local area network (LAN) adapters.
  • Enterprise Base Machine Controller (eBMC) managed
  • Titanium power supplies for the most stringent environmental regulations
  • IBM Power Private Cloud with Dynamic Capacity (Elastic Capacity on Demand and Power Enterprise Pools 2.0).
  • IBM Power to Cloud Rewards Program.
  • Active Memory Expansion (AME) and Active Memory Mirroring (AMM) for Hypervisor.
  • Packaged in a standard 19-inch rack mount 4U drawer.
  • Support for IBM AIX and Linux operating systems.
  • Standard three-year warranty with IBM Power Expert Care services


Back to topBack to top

Highlights

Top rule

The IBM Power E1050 server (9043-MRX) is an enhanced enterprise class four-socket, 4U server that provides massive scalability and flexibility. This system is agile and delivers extreme density in an energy-efficient design with superior reliability and resiliency. It will provide enterprise clients with a secure and flexible environment that balances mission-critical and modernization applications to deliver a frictionless hybrid cloud experience.

Power E1050 features include:

  • IBM Power10 processor modules with 12, 18, or 24 cores options.
    • Twelve-core processor modules provide up to 48 cores per system typical 3.35-4.0 GHz (max).
    • Eighteen-core processor modules provide up to 72 cores per system typical 3.20--4.0 GHz (max).
    • Twenty-four-core processor modules provide up to 96 cores per system typical 2.95--3.90 GHz (max).
  • Enterprise class 4U differential dual in-line memory module (DDIMM) memory technology with enhanced reliability, availability, and serviceability with 256 GB to 16 TB of memory capacity.
    • A two-processor module configuration provides 32 DDIMM slots and a maximum of 8 TB.
    • A three-processor module configuration provides 48 DDIMM slots and a maximum of 12 TB.
    • A four-processor module configuration provides 64 DDIMM slots and a server maximum of 16 TB.
  • Peripheral Component Interconnect Express (PCIe) slots.
    • System unit supports up to 11 PCIe Gen5/4 slots.
    • One PCIe Gen4 slot reserved for default Ethernet adapter.
    • PCIe I/O expansion drawers support up to 48 additional PCIe slots.
  • Up to ten nonvolatile memory express (NVMe) drive bays.
  • Integrated USB controller provides two front and two rear USB ports.
  • Additional storage can be attached.
    • Up to 1,536 SFF-2 bays for hard disk drives (HDDs) and solid-state drives (SSDs) with 64 EXP24SX I/O drawers.
    • Fibre Channel (FC) and local area network (LAN) adapters.
  • Enterprise Base Machine Controller (eBMC) managed
  • Titanium power supplies to meet the most stringent regulations on Power Supply Efficiency
  • IBM Power Private Cloud with Dynamic Capacity (Elastic Capacity on Demand and Power Enterprise Pools 2.0).
  • IBM Power to Cloud Rewards Program for IBM Lab Services engagements.
  • Active Memory Expansion (AME) and Active Memory Mirroring (AMM) for Hypervisor.
  • Packaged in a standard 19-inch rack mount 4U drawer.
  • Support for IBM AIX, Linux and VIOS operating systems.
  • Standard three-year warranty with IBM Power Expert Care services


Back to topBack to top

Description

Top rule

Power E1050feature summary

The following features are available on the new Power E1050 server:

  • The Power E1050 supports 24 to 96 processor cores with two to four Power10 processor modules.
  • The Power E1050 delivers 256 GB--16 TB high-performance DDR4 memory with L4 cache.
  • Each Power E1050 server can support up to 10 NVMe storage devices.
  • Up to 11 hot-swap PCIe slots in the system unit:
    • 6 PCIe Gen5 x8 or Gen4 x16 slots.
    • 3 PCIe Gen4 x8 slots.
    • 2 PCIe Gen5 x 8 slots.
    • With two processor modules, there are seven PCIe slots; with three modules and four modules, there are eleven PCIe slots.
  • The PCIe I/O Expansion Drawer (#EMX0) expands the number of full- high, hot-swap slots:
    • Up to two PCIe drawers with two processor modules (maximum 31 slots on the server).
    • Up to four PCIe drawers with four processor modules (maximum 51 slots on the server).
  • Up to 64 EXP24SX SFF Drawers (#ESLS) can be attached, providing up to 1,536 SAS bays for disks or SSDs.
  • System unit I/O (integrated I/O):
    • USB 3.0 ports: four 3.0 ports, two front and two rear.
    • USB 2.0 ports: two rear 2.0 ports for limited use.
    • HMC ports: two 1 GbE RJ45.
  • Four hot-plug and redundant power supplies 2300 W (200--240 V AC) (#EB39).
  • System unit only 4U in a 19-inch rack-mount hardware.
  • Primary operating systems:
    • AIX (#2146): small-tier licensing.
    • Linux (#2147): RHEL and SLES.

Processor modules

  • The Power E1050 supports 24 to 96 processor cores:
    • Twelve-core typical 3.35-4.0 GHz (max) EPEU Power10 processor
    • Eighteen-core typical 3.20--4.0 GHz (max) #EPEV Power10 processor
    • Twenty-four-core typical 2.95--3.90 GHz (max) #EPGW Power10 processor
  • A minimum of two and a maximum of four processor modules are required for each system. The modules can be added to a system at a later time through an MES order, but they will require scheduled downtime to install. All processor modules in one server must be the same gigahertz (same processor module feature number). They cannot be mixed.
  • Permanent CoD processor core activations are required for the first processor module in the configuration and are optional for the second, third and fourth modules. Specifically:
    • Two, three, or four 12-core, typical 3.35-4.0 GHz (max) processor modules (#EPEU) require 12 processor core activations (#EPUR) at a minimum.
    • Two, three, or four 18-core, typical 3.20--4.0 GHz (max) processor modules (#EPEV) require 18 processor core activations (#EPUS) at a minimum.
    • Two, three, or four 24-core, typical 2.95--3.90 GHz (max) processor modules (#EPGW) require 24 processor core activations (#EPYT) at a minimum.
  • Temporary CoD capabilities are optionally used for processor cores that are not permanently activated:
    • An HMC is required for temporary CoD.

System memory

  • 256 GB--16 TB high-performance up to 3200 MHz DDR4 OMI memory:
    • 64 GB DDR4 (2 x 32GB DDIMM's) Memory (#EM75)
    • 128 GB DDR4 (2 x 64GB DDIMM's) Memory (#EM76)
    • 256 GB DDR4 (2 x 128GB DDIMM's) Memory (#EM77)
    • 512 GB DDR4 (2 x 256GB DDIMM's) Memory (#EM7J)
    • Optional Active Memory Expansion (#EMBM).
  • As your memory requirements increase, the system capabilities are increased as follows:
    • With two processor modules installed, 32 DDIMM slots are available; minimum memory is 256 GB.
    • With three processor modules installed, 48 DDIMM slots are available; minimum memory is 384 GB
    • With four processor modules installed, 64 DDIMM slots are available; minimum memory is 512 GB. Sixteen DDIMMs are available per socket.
    • The more DDIMM slots that are filled, the larger the available bandwidth available to the server.

      Permanent CoD memory activations are required for at least 50% of the physically installed memory or 256 GB of activations, whichever is larger. Use 1 GB activation (#EMCP) and 100 GB activation (#EMCQ) features to order permanent memory activations.

  • Temporary CoD for memory is available for memory capacity that is not permanently activated:
    • Delivery through Virtual Capacity machine type/model (MTM) (4586-COD) using Entitled Systems Support (ESS) process.
    • An HMC is required for temporary CoD.

Notes:

  • A memory feature code consists of 2 DDIMMs.
  • The Minimum memory orderable is 4 DDIMMs per processor socket.
  • For 2-socket system, minnimum memory orderable is 8 DDIMMs.
  • For 3-socket system, minnimum memory orderable is 12 DDIMMs.
  • For 4-socket system, minnimum memory orderable is 16 DDIMMs.
  • Next memory increment is multiple of 4 DDIMMs.
  • All DDIMMs belong to a processor must be of same size and type, i.e. same feature code.
  • Each processor socket can have different total memory capacity from other processor sockets.
  • The minimum memory supported per two Power10 processors installed is 256 GB.
  • The minimum memory supported per three Power10 processors installed is 384 GB.
  • The minimum memory supported per four Power10 processors installed is 512 GB.

Storage options

The Power E1050 supports up to ten NVMe 7-milimeter or 15-milimeter drives:

  • Six NVMe drives within two or three-socket configuration
  • Ten NVMe drives within a four-socket configuration

All NVMe drives are driven directly from the system backplane with no PCIe card or cables required.

The 7-milimeter NVMe drives from the IBM Power E950 are also supported on the Power E1050 with a carrier conversion feature that is offered to hold these drives.

Power Private Cloud Solution with Dynamic Capacity

The Power Private Cloud Solution with Dynamic Capacity is an infrastructure offering that enables you to take advantage of cloud agility and economics while getting the same business continuity and flexibility that you already enjoy from Power servers. The Power Private Cloud Solution offers:

  • Cost optimization with pay-for-use pricing
  • Automated and consistent IT management with Red Hat Ansible for Power
  • IBM Proactive Support for Power services
  • IBM Systems Lab Services Assessment and implementation assistance

Both Elastic and Shared Utility Capacity options are now available on all Power E1050 systems through the Virtual Capacity (4586-COD) MTM and the ESS website.

Elastic Capacity on the Power E1050 system enables you to deploy pay-for-use consumption of processor, memory, and supported operating systems, by the day, across a collection of Power E1050 and Power E950 systems.

Shared Utility Capacity on Power E1050 systems provides enhanced multisystem resource sharing and by-the-minute tracking and consumption of compute resources across a collection of systems within a Power Enterprise Pools (2.0). It delivers a complete range of flexibility to tailor initial system configurations with the right mix of purchased and pay-for-use consumption of processor, memory, and software. Clients with existing Power Enterprise Pools of Power E950 systems can simply add Power E1050 systems into their pool and migrate to them at the rate and pace of their choosing, as any Power E950 and Power E1050 server may seamlessly interoperate and share compute resources within the same pool.

A Power Private Cloud Solution infrastructure consolidated onto Power E1050 systems has the potential to greatly simplify system management so IT teams can focus on optimizing their business results instead of moving resources around within their data center.

Shared Utility Capacity resources are easily tracked by virtual machine (VM) and monitored by a CMC, which integrates with local HMCs to manage the pool and track resource use by system and VM, by the minute, across a pool.

You no longer need to worry about overprovisioning capacity on each system to support growth, as all available processor and memory on all systems in a pool are activated and available for use.

Base Capacity for processor, memory, and supported operating system entitlement resources is purchased on each Power E950 and Power E1050 system and is then aggregated across a defined pool of systems for consumption monitoring.

Metered Capacity is the additional installed processor and memory resource above each system's Base Capacity. It is activated and made available for immediate use when a pool is started, then monitored by the minute by a CMC.

Metered resource usage is charged only for minutes exceeding the pool's aggregate Base resources, and usage charges are debited in real-time against your purchased Capacity Credits (5819-CRD) on account.

IBM offers a Private Cloud Capacity Assessment and Implementation Service performed by Systems Lab Services professionals, which can be preselected at time of purchase or requested for qualifying Power E1050 servers.

I/O support

PCIe slots

The Power E1050 server has up to eight PCIe Gen5 and three PCIe Gen4 general purpose hot-plug slots, providing configuration flexibility and expandability. Six adapter slots are x16 Gen5/4, two adapter slots are x8 Gen5, and three adapter slots are x8 Gen4 . All adapter slots are full height, half length.

The number of slots supported vary by the number of processor modules.

Processor modules         2      3/4
                          socket socket
------------------------- ------ ------
x16 Gen4 or x8 Gen5 slots 2      6
x8 Gen4 slots             3      3
x8 Gen5 slots             2      2

Notes:

  • The PCIe Genx8 slot, C1, is reserved for an Ethernet adapter to help ensure proper manufacture and test of the server.
  • Blind-swap cassettes (BSC) are used for adapters in the system unit.
  • All PCIe slots in the system unit are single root I/O virtualization (SR-IOV) capable.
  • Each NVMe SSD interface is a Gen4 x4 PCIe bus. The NVMe drives can be in an OS-controlled RAID0, RAID1 array. Hardware RAID is not supported on the NVMe drives.

The x16 slots can provide up to twice the bandwidth of x8 slots because they offer twice as many PCIe lanes. PCIe Gen5 slots can support up to twice the bandwidth of a PCIe Gen4 slot and up to four times the bandwidth of a PCIe Gen3 slot, assuming an equivalent number of PCIe lanes. PCIe Gen1, PCIe Gen2, PCIe Gen3, PCIe Gen4, and PCIe Gen5 adapters can be plugged into a PCIe Gen5 slot, if that adapter is supported. The x16 slots and selective x8 slots can be used to attach PCIe Gen3 I/O expansion drawers.

This server is smarter than earlier servers about energy efficiency for cooling the PCIe adapter environment. They can sense which IBM PCIe adapters are installed in their PCIe slots. If an adapter is known to require higher levels of cooling, they automatically speed up fans to increase airflow across the PCIe adapters.

USB DVD external and boot devices

The Power E1050 provides two front USB ports, mainly to support the external USB DVD.

System boot is supported through these options:

  1. NVMe drives
  2. A SAN attached to FC or FCoE adapters and indicated to the server by the 0837 specify code
  3. USB front port for external USB-based DVD
  4. USB front port for USB memory key/flash drive

Assuming option 1 above, the minimum system configuration requires at least one NVMe disk drive in the system for AIX and Linux.

I/O drawer attachment

Clients migrating from earlier-generation servers may have been using I/O drawers such as the GX++ attached feature 5802 or feature 5877 PCIe 12X I/O drawers with PCIe Gen1 slots. Though most PCIe adapters in the feature 5802 or feature 5877 drawers can be moved to this server and its disk drives converted and moved to the feature ESLS EXP24SX drawer, the feature 5802 and feature 5877 drawers are not supported on this newer Power technology-based server. Similarly, the GX++ attached EXP30 Ultra SSD Drawer (#EDR1 or #5888) is not supported.

Up to 64 EXP24SX storage drawers can be attached to a Power E1050 server. With 24 drives per drawer, this means up to 1,536 SFF-2 drives are supported. A maximum of 16 EXP24SX per PCIe Gen3 I/O drawer is supported due to cable management considerations.

The older 3.5-inch-based EXP12S SAS Disk Drawer (#5886) and EXP24 SCSI Disk Drawer (#5786) are not supported.

IBM offers a 1U multimedia drawer that can hold one or more DVDs, tape drive, or RDX docking stations. The 7226-1U3 is the most current offering. The earlier 7216-1U2 and 7214-1U2 are also supported. Up to six of these multimedia drawers can be attached.

PCIe I/O expansion drawer

PCIe I/O Expansion Drawers (#EMX0) can be attached to the system unit to expand the number of full-high, hot-swap slots available to the server. The maximum number of PCIe I/O drawers depends on the number of processor modules physically installed. The maximum is independent of the number of processor core activations.

  • Up to two PCIe drawers with two processor modules.
  • Up to three PCIe drawers with three processor modules.
  • Up to four PCIe drawers with four processor modules.
  • The 19-inch 4 EIA (4U) PCIe I/O Expansion Drawer (#EMX0) and two PCIe fanout modules (#EMXG) provide 12 PCIe I/O full-length, full- height slots. One fanout module provides six PCIe slots labeled C1 through C6. Slots C1 and C4 are x16 slots, and C2, C3, C5, and C6 are x8 slots. All six slots in a PCIe3 6-slot fanout module are SR-IOV enabled. The feature EC2S and feature EC2U adapters are supported in slots C1 through C6, but only four feature EC2S and feature EC2U adapters can be in SR-IOV shared mode at a time.
  • An EMX0 drawer can be configured with one or two EMXG fanout modules. Adding a second fanout module is not a hot-plug operation and requires scheduled downtime.
  • PCIe Gen1, Gen2, and Gen3 full-high adapter cards are supported. The set of full-high PCIe adapters that are supported is found in the Sales Manual, identified by feature number. See the PCI Adapter Placement manual for the Power E1050 for details and rules associated with specific adapters supported and their supported placement in x8 or x16 slots.
  • Each fanout module requires one PCIe Cable Adapter (#EJ08), which is placed in a x16 PCIe slot and selective x8 slots of the system unit.
  • A cable pair attaches the PCIe Cable Adapter (#EJ08) to the fanout module. Feature ECC7 provides a pair of 3-meter optical cables with transceivers. Feature ECC8 provides a pair of 10-meter optical cables with transceivers. Feature ECCS provides a pair of 3-meter copper cables. Two cables of identical length, or one feature, is required for each fanout module. Optical cables are smaller diameter and more flexible and can be longer than the copper cables. Copper cables are lower cost. Copper and optical cables have the same performance and reliability characteristics.
  • The cable adapter (#EJ08) can be placed in any of the system units' available x16 slots and selective x8 slot and attached to any fanout module in any of the server's PCIe I/O drawers (#EMX0). The PCIe I/O drawer cannot be shared by two different servers.
  • Recommendation: Locate any attached PCIe I/O expansion drawer in the same rack as the Power10 server for ease of service. However, the drawers can be installed in separate racks if the application or other rack content requires it. It is recommended to use 3-meter cables for PCIe drawers in the same rack as the system unit and 10-meter cables for drawers located in a different rack.
  • Concurrent repair and add/removal of PCIe adapter cards is done by HMC-guided menus or by operating system support utilities.
  • When the operating system is Linux, PowerVM is required for support of the I/O expansion drawer.

Rack cable brackets

The cable bracket is used to secure the communications cables so that they can be raised to remove the blind swap cassettes containing the PCIe adapters. To enable the server to be pulled forward on its rails for service access to memory, processors and voltage regulator modules requires the disconnecting the cables from the server.

Integrated I/O ports

E1050 integrated IO consists of four Operation System (OS) USB 3.0 port and those of the service processor eBMC. Two of the four OS USB 3.0 ports are at the front and 2 are at the rear physically on the eBMC card tailstock. The front OS USB 3.0 ports have higher current capacity than the two rear USB 3.0. The front USB 3.0 ports are typically used for the external DVD drive and for other general USB devices such as USB key. The two rear USB 3.0 are typical used for general USB devices such as USB key. Do not use the rear USB 3.0 port for external DVD drive.

The eBMC integrated IO consists of two Ethernet RJ45 ports and two USB 2.0 ports. All these ports are at the eBMC card tailstock, together with 2 OS USB 3.0 ports.

The two eBMC Ethernet are typically used for HMC connection, one for the primary HMC and the other could be used for an HMC secondary.

When HMC is not used, one of the Ethernet ports is typically connected to a network so that eBMC interface can be used to control and manage the system by means of the GUI, Redfish interface or command line .

The eBMC two USB2.0 can be used for USB key to update eBMC code or for Uninterruptible Power System (UPS) control cable. For UPS application, a converter cable, feature code ECCF, provides a USB-to-9-pin, D-shell connection to some UPS. The IBM 9910 Uninterruptible Power System, models E66 and E67, are supported as purchase options with the Power E1050 server.

Racks

The Power E1050 server is designed to fit a standard 19-inch rack. IBM Development has tested and certified the system for the following rack support:

  • 7965-S42 (42U): field integration only
  • 7014-T42 (42U): supported only

Clients can choose to place the server in other racks if they are confident those racks have the strength, rigidity, depth, and hole- pattern characteristics that are needed. Clients should work with IBM Service to determine the appropriateness of other racks. The Power E1050 rails can adjust their depth to fit a rack that is 22.75 inches--30.5 inches in depth based on the adjustable outer brackets going from the front rail to the rear rail.

IBM Manufacturing does not support the use of other racks with the Power E1050 initial system order or model upgrade. The 7965-S42 (#ECR0) or 7014-T42 (#0553) are 2-meter enterprise racks that provide 42U or 42 EIA of space.

Additional Power E1050 PCIe I/O Drawers (#EMX0) for an already- installed server can be MES ordered with or without a rack.

Typical good cable management practices apply. For example, it is usually a good practice to leave 1U or 2U open at the top or bottom of the rack for cables exiting the rack or to hold extra cable lengths. Or if you have more than four PCIe I/O drawers in the same rack, carefully consider how many four-port PCIe adapters have cables attached to all their ports. If you are not using something like the 8-inch extension for a 7965-S42 rack for extra space to lay the cables, service access can be a challenge, especially with thicker I/O cables. Or another example, if there are a lot of I/O cables in the rack, horizontally mounting the power distribution units (PDUs) versus mounting them vertically in the side pockets eases service access.

Rack front door options supported are the acoustic door (#6248 or #6249), the attractive geometrically accented door (#ERG7), and the cost-effective plain front door (#6068 or #6069). The front trim kit is also supported (#6263 or #6272).

PDUs

Using previously provided IBM PDU features 7188, 7109, and 7196 reduces the number of Power E1050 servers and other equipment that can be held most efficiently in a rack. The high-function PDUs provide more electrical power per PDU and thus offer better PDU footprint efficiency. In addition, they are intelligent PDUs that provide insight to actual power usage by receptacle and also provide remote power on/off capability for easier support by individual receptacle. The new PDUs are features ECJJ, ECJL, ECJN, and ECJQ.

One 9043-MRX can be supported on a single PDU or pair of PDUs with 6654, 6655, 6658 or ELC1 line cords ordered on S42 racks.

IBM Manufacturing will only integrate the newer PDUs with the Power E1050 server. IBM Manufacturing does not support integrating earlier PDUs, such as the feature 7188, 7109, or 7196. You can choose to use older IBM PDUs in your racks, but you will have to install those earlier PDUs at your site.

                       1-phase   3-phase
                       or        208 V,
                       3-phase   depending
                       wye,      on
                       depending country
                       on        wiring
                       country   standards
                       wiring
                       standards
---------------------- --------- ---------
Nine C19 receptacles   #ECJJ     #ECJL
Twelve C13 receptacles #ECJN     #ECJQ
  • High-Function 9 x C19 PDU: Switched, Monitoring (#ECJJ) . This is an intelligent, switched 200--240 V AC PDU with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack, making the nine C19 receptacles easily accessible. Each receptacle has a 20-amp circuit breaker. Depending on country wiring standards, the PDU is single-phase or three-phase wye. The PDU can be mounted vertically in rack side pockets, or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features 6489, 6491, 6492, 6653, 6654, 6655, 6656, 6657, 6658, and 6667.
  • High-Function 9 x C19 PDU 3-Phase: Switched, Monitoring (#ECJL) . This is an intelligent, switched 208 V three-phase AC PDU with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack, making the nine C19 receptacles easily accessible. Each receptacle has a 20-amp circuit breaker. The PDU can be mounted vertically in rack side pockets, or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One wall line cord is provided with the PDU (no separate feature number) and has an IEC60309 60A plug (3P+G). The PDU supports up to 48 amps. Two RJ45 ports on the front of the PDU enable you to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password, and IBM strongly urges clients to change it upon installation.
  • High-Function 12 x C13 PDU: Switched, Monitoring (#ECJN) . This is an intelligent, switched 200--240 V AC PDU with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack, making the twelve C13 receptacles easily accessible. Each receptacle has a 20-amp circuit breaker. Depending on country wiring standards, the PDU is single-phase or three-phase wye. The PDU can be mounted vertically in rack side pockets, or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. Device power cords with a C14 plug connect to C13 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features 6489, 6491, 6492, 6653, 6654, 6655, 6656, 6657, 6658, and 6667. Two RJ45 ports on the front of the PDU enable you to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password, and IBM strongly urges clients to change it upon installation.
  • High-Function 12 x C13 PDU 3-Phase: Switched, Monitoring (#ECJQ) . This is an intelligent, switched 208 V three-phase AC PDU with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack, making the twelve C13 receptacles easily accessible. Each receptacle has a 20-amp circuit breaker. The PDU can be mounted vertically in rack side pockets, or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. Device power cords with a C14 plug connect to C13 PDU receptacles and are ordered separately. One wall line cord is provided with the PDU (no separate feature number) and has a IEC60309 60A plug (3P+G). The PDU supports up to 48 amps. Two RJ45 ports on the front of the PDU enable you to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password, and IBM strongly urges clients to change it upon installation.

Lifting considerations

Three to four service personnel are required to manually remove or insert a system unit into a rack, given its dimensions, weight, and content. To avoid the need for this many people to assemble at your site for a service action, a lift tool can be very useful. If you have chosen to install this customer setup (CSU) system, similar lifting considerations apply.

The Power E1050 server has a maximum weight of 69 kilograms (153 pounds). However, by temporarily removing the power supplies, fans, and RAID assembly, the weight is easily reduced to a maximum of 55 kilograms (121 pounds).

When lowering the Power E1050 server onto its rails in the rack, the server must be tilted on one end about 15 degrees so that the pins on the server enclosure fit onto the rails. This equates to lifting one end of the server about 4 centimeters (1.6 inches). This can be done using a tip plate on a lift tool or manually adjusting the load on a lift tool or tilting during the manual lift. Consider the optional feature EB2Z lift tool.

PowerVM Enterprise Edition License Entitlement is now included with each Power E1050 server.

PowerVM Enterprise Edition is available as a hardware feature (#EPVV) and supports up to 20 partitions per core, VIOS, and multiple shared processor pools. It also offers LPM, Active Memory Sharing, and PowerVP performance monitoring.

Other PowerVM technologies include:

  • System Planning Tool simplifies the process of planning and deploying IBM Power LPARs and virtual I/O.
  • VIOS is a single-function appliance that resides in a Power partition. It facilitates the sharing of physical I/O resources between AIX, Linux, and client partitions within the server. VIOS provides shared Ethernet adapter (SEA) virtual I/O to client LPARs.
  • Virtual SCSI (VSCSI) enables the sharing of physical storage adapters (FC) and storage devices (disk and optical) between logical partitions.
  • With virtual networking, a SEA enables connectivity between internal and external virtual LANs (VLANs); virtual Ethernet provides high-speed connections between partitions.

With LPM, you can move a running AIX or Linux VM from one physical server to another with no downtime. You can use this capability to:

  • Evacuate workloads from a system before performing scheduled maintenance.
  • Move workloads across a pool of different physical resources as business needs shift.
  • Move workloads away from underutilized machines so that they can be powered off to save on energy and cooling costs.
  • Move your workloads to new Power10 systems for upgrades without having to schedule an outage. With Active Memory Sharing, memory is dynamically moved between running partitions for optimal resource usage.

Active Memory Expansion

AME is an innovative technology supporting the AIX operating system that helps enable the effective maximum memory capacity to be larger than the true physical memory maximum. Compression or decompression of memory content can enable memory expansion up to 100% or more. This can enable a partition to do significantly more work or support more users with the same physical amount of memory. Similarly, it can enable a server to run more partitions and do more work for the same physical amount of memory.

AME uses CPU resource to compress or decompress the memory contents. The trade-off of memory capacity for processor cycles can be an excellent choice, but the degree of expansion varies on how compressible the memory content is. It also depends on having adequate spare CPU capacity available for this compression or decompression.

Power10 chips include a hardware accelerator designed to boost AME efficiency and use less Power core resource. The Power10 accelerator includes some minor enhancements and also leverages Power10 higher bandwidth and lower latency characteristics.

You have a great deal of control over AME usage. Each individual AIX partition can turn on or turn off AME. Control parameters set the amount of expansion desired in each partition to help control the amount of CPU used by the AME function. An IPL is required for the specific partition that is turning on memory expansion. When turned on, monitoring capabilities are available in standard AIX performance tools, such as lparstat, vmstat, topas, and svmon.

A planning tool is included with AIX, enabling you to sample actual workloads and estimate both how expandable the partition's memory is and how much CPU resource is needed. Any Power model can run the planning tool. In addition, a one-time, 60-day trial of AME is available to enable more exact memory expansion and CPU measurements. You can request the trial using the Power Capacity on Demand website.

AME is enabled by chargeable hardware feature EMAM, which can be ordered with the initial order of the system node or as an MES order. A software key is provided when the enablement feature is ordered, which is applied to the system node. An IPL is not required to enable the system node. The key is specific to an individual system node and is permanent. It cannot be moved to a different server.

The additional CPU resource used to expand memory is part of the CPU resource assigned to the AIX partition running AME. Normal licensing requirements apply.

IBM Power E1050 Solution Edition for Healthcare

The Power E1050 Solution Edition for Healthcare provides a cost- effective up to 96-core processor and 16 TB memory solution for eligible healthcare industry clients running approved ISV applications, such as Epic.

  • Solution Edition for Healthcare 24-core typical 2.95--3.90 GHz processor (#EHC8)
  • Processor Activations (24) for #EHC8 (#EPYT)
  • No-cost Processor Activations (#EHCA)
  • Memory Activation (512 GB) for #EHC8 (#EMCE)
  • No-cost Memory Activation (512 GB) (#EHCB)

The Power E1050 Solution Edition for Healthcare minimum requirement is a server with 2x typical 2.95--3.90 GHz processor modules, 48 cores (all active), and 1 TB memory (all active).
Note: For every purchased Processor Activation #EPYT, get one free activation #EHCA up to the max in the table below. Additional #EPYT may be purchased without #EHC8 required.

Sockets Required Processor  Free       Total
        feature  Activation Processor  maximum
        EHC8     #EPYT      Activation Processor
                            of #EHCA   Activations
------- -------- ---------- ---------- ----------- --------
                 Min        Max
2       2        24         24         up to 24    up to 48
3       3        24         36         up to 36    up to 72
4       4        24         48         up to 48    up to 96

Note: For every purchased Memory Activation #EMCE, get one free activation #EHCB up to the max in the table below. Additional #EMCE may be purchased without #EHC8 required.
Sockets Required Memory     Free       Total
        feature  Activation Memory     maximum
        EHC8     #EMCE      Activation Memory
                            of #EHCB   Activations
------- -------- ---------- ---------- ----------- ----------
                 Min        Max
------- -------- ---------- ---------- ----------- ----------
2       2        1          2          up to 2     up to 2 TB
3       3        1          3          up to 3     up to 3 TB
4       4        1          4          up to 4     up to 4 TB

For eligibility rules and registration of the Power Solution Edition for Healthcare by the sales channel, go to the IBM Power Solution Editions website.

Reliability, Availability, and Serviceability

Reliability, fault tolerance, and data correction

The reliability of systems starts with components, devices, and subsystems that are designed to be highly reliable. During the design and development process, subsystems go through rigorous verification and integration testing processes. During system manufacturing, systems go through a thorough testing process to help ensure the highest level of product quality.

The Power10 processor-based E1050 system comes with the following RAS characteristics:

  • Power10 processor RAS
  • Open Memory Interface, differential DIMMs RAS
  • Enterprise BMC service processor for system management and service
  • Active Memory Mirroring for Hypervisor
  • NVMe drives concurrent maintenance
  • PCIe adapters concurrent maintenance
  • Redundant and hot-plug cooling
  • Redundant and hot-plug power
  • Redundant voltage regulators
  • Time-of-day battery concurrent maintenance
  • Lightpath enclosure and FRU LEDs
  • Service and FRU labels
  • Client or IBM install
  • Proactive support and service -- call home
  • Client or IBM service

Service processor

The Power10 processor-based E1050 system comes with a redesigned service processor based on a Baseboard Management Controller (BMC) design with firmware that is accessible through open-source industry standard APIs, such as Redfish. An upgraded ASMI web browser user interface preserves the required RAS functions while allowing the user to perform tasks in a more intuitive way.

Diagnostic monitoring of recoverable error from the processor chipset is performed on the system processor itself, while the fatal diagnostic monitoring of the processor chipset is performed by the service processor. It runs on its own power boundary and does not require resources from a system processor to be operational to perform its tasks.

The service processor supports surveillance of the connection to the HMC and to the system firmware (hypervisor). It also provides several remote power control options, environmental monitoring, reset, restart, remote maintenance, and diagnostic functions, including console mirroring. The BMC service processors menus (ASMI) can be accessed concurrently during system operation, allowing nondisruptive abilities to change system default parameters, view and download error logs, check system health.

Redfish, an industry standard for server management, enables the Power servers to be managed individually or in a large data center. Standard functions such as inventory, event logs, sensors, dumps, and certificate management are all supported with Redfish. In addition, new user management features support multiple users and privileges on the BMC via Redfish or ASMI. User management via LDAP is also supported. The Redfish events service provides a means for notification of specific critical events such that actions can be taken to correct issues. The Redfish telemetry service provides access to a wide variety of data (eg. power consumption, ambient, core, DIMM and I/O temperatures, etc) that can be streamed on periodic intervals.

Mutual surveillance

The service processor monitors the operation of the firmware during the boot process and also monitors the hypervisor for termination. The hypervisor monitors the service processor and reports a service reference code when it detects surveillance loss. In the PowerVM environment, it will perform a reset/reload if it detects the loss of the service processor.

Environmental monitoring functions

The Power family does ambient and over temperature monitoring and reporting. It also adjusts fan speeds automatically based on those temperatures.

Memory subsystem RAS :

The Power10 processor-based E1050 system introduces a new 4U tall differential DIMM (DDIMM), which has new open CAPI memory interface known as OMI for resilient and fast communication to the processor. This new memory subsystem design delivers solid RAS as described below.

  • Memory Buffer: The DDIMM contains a memory buffer with key RAS features, including protection of critical data/address flows using CRC, ECC, and parity, a maintenance engine for background memory scrubbing and memory diagnostics, and a Fault Isolation Register (FIR) structure, which enables firmware attention-based fault isolation and diagnostics.
  • OMI (Open Memory Interface): The OMI interface between the memory buffer and processor memory controller is protected by dynamic lane calibration, as well as a CRC retry/recovery facility to retransmit lost frames to survive intermittent bit flips. A complete lane fail can also be survived by triggering a dynamic lane reduction from 8 to 4, independently for both up and downstream directions. A key advantage of the OMI interface is that it simplifies the number of critical signals that must cross connectors from processor to memory compared to a typical industry-standard DIMM design.
  • Memory ECC: The DDIMM includes a robust 64-byte Memory ECC, with 8-bit symbols, capable of correcting up to five symbol errors (one x4 chip and one additional symbol), as well as retry for data and address uncorrectable errors.
  • Dynamic row repair: To further extend the life of the DDIMM, the dynamic row repair feature can restore full use of a DRAM for a fault contained to a DRAM row, while system continues to operate.
  • Spare temperature sensors : Each DDIMM provides spare temperature sensors, such that the failure of one does not require a DDIMM replacement.
  • Spare DRAMs: 4U DDIMMs include two spare x4 memory modules (DRAMs) per rank. These can be substituted for failed DRAMs during runtime operation. Combined with ECC correction, the 2 spares allow the 4U DDIMM to continue to function with 3 bad DRAMs per rank, compared to 1 (single device data correct) or 2 (double device data correct) bad DRAMs in a typical industry standard DIMM design. This extends self-healing capabilities beyond what is provided with dynamic row repair capability.
  • Spare power management integrated circuits (PMICs) : 4U DDIMMs include PMICs such that the failure of one PMIC does not require a DDIMM replacement .

Power10 processor functions

As in Power9, the Power10 processor has the ability to do processor instruction retry for some transient errors and core-contained checkstop for certain solid faults. The fabric bus design with CRC and retry persists in Power10 where a CRC code is used for checking data on the bus and has an ability to retry a faulty operation.

Cache availability

The L2/L3 caches in the Power10 processor in the memory buffer chip are protected with double-bit detect, single-bit correct error detection code (ECC). In addition, a threshold of correctable errors detected on cache lines can result in the data in the cache lines being purged and the cache lines removed from further operation without requiring a reboot in the PowerVM environment.

Modified data would be handled through Special Uncorrectable Error handling. L1 data and instruction caches also have a retry capability for intermittent errors and a cache set delete mechanism for handling solid failures.

Special Uncorrectable Error handling

Special Uncorrectable Error (SUE) handling prevents an uncorrectable error in memory or cache from immediately causing the system to terminate. Rather, the system tags the data and determines whether it will ever be used again. If the error is irrelevant, it will not force a check stop. When and if data is used, I/O adapters controlled by an I/O hub controller would freeze if data were transferred to an I/O device, otherwise, termination may be limited to the program/kernel or if the data is not owned by the hypervisor.

PCI extended error handling

PCI extended error handling (EEH)-enabled adapters respond to a special data packet generated from the affected PCI slot hardware by calling system firmware, which will examine the affected bus, allow the device driver to reset it, and continue without a system reboot. For Linux, EEH support extends to the majority of frequently used devices, although some third-party PCI devices may not provide native EEH support.

Uncorrectable error recovery

When the auto-restart option is enabled, the system can automatically restart following an unrecoverable software error, hardware failure, or environmentally induced (AC power) failure.

Serviceability

The purpose of serviceability is to efficiently repair the system while attempting to minimize or eliminate impact to system operation. Serviceability includes system installation, MES (system upgrades/downgrades), and system maintenance/repair. Depending upon the system and warranty contract, service may be performed by the client, an IBM representative, or an authorized warranty service provider.

The serviceability features delivered in this system help provide a highly efficient service environment by incorporating the following attributes:

  • Design for SSR setup, install, and service
  • Error Detection and Fault Isolation (ED/FI)
  • First Failure Data Capture (FFDC)
  • Light path service indicators
  • Service and FRU labels available on the system
  • Service procedures documented in IBM Documentation or available through the HMC
  • Automatic reporting of serviceable events to IBM through the Electronic Service Agent Call Home application

Service environment

In the PowerVM environment, the HMC is a dedicated server that provides functions for configuring and managing servers for either partitioned or full-system partition using a GUI or command-line interface (CLI) or REST API. An HMC attached to the system enables support personnel (with client authorization) to remotely, or locally to the physical HMC that is in proximity of the server being serviced, log in to review error logs and perform remote maintenance if required.

The Power10 processor-based systems support several service environments:

  • Attachment to one or more HMCs or vHMCs is a supported option by the system with PowerVM. This is the default configuration for servers supporting logical partitions with dedicated or virtual I/O. In this case, all servers have at least one logical partition.
  • No HMC. There are two service strategies for non-HMC systems.
    • Full-system partition with PowerVM: A single partition owns all the server resources and only one operating system may be installed. The primary service interface is through the operating system and the service processor.
    • Partitioned system with NovaLink: In this configuration, the system can have more than one partition and can be running more than one operating system. The primary service interface is through the service processor.

Service interface

Support personnel can use the service interface to communicate with the service support applications in a server using an operator console, a graphical user interface on the management console or service processor, or an operating system terminal. The service interface helps to deliver a clear, concise view of available service applications, helping the support team to manage system resources and service information in an efficient and effective way. Applications available through the service interface are carefully configured and placed to give service providers access to important service functions.

Different service interfaces are used, depending on the state of the system, hypervisor, and operating environment. The primary service interfaces are:

  • LEDs
  • Operator panel
  • BMC Service Processor menu
  • Operating system service menu
  • Service Focal Point on the HMC or vHMC with PowerVM

In the light path LED implementation, the system can clearly identify components for replacement by using specific component-level LEDs and can also guide the servicer directly to the component by signaling (turning on solid) the enclosure fault LED, and component FRU fault LED. The servicer can also use the identify function to blink the FRU-level LED. When this function is activated, a roll-up to the blue enclosure identify will occur to identify an enclosure in a rack. These enclosure LEDs will turn on solid and can be used to follow the light path from the enclosure and down to the specific FRU in the PowerVM environment.

First Failure Data Capture and error data analysis

First Failure Data Capture (FFDC) is a technique that helps ensure that when a fault is detected in a system, the root cause of the fault will be captured without the need to re-create the problem or run any sort of extending tracing or diagnostics program. For the vast majority of faults, a good FFDC design means that the root cause can also be detected automatically without servicer intervention.

FFDC information, error data analysis, and fault isolation are necessary to implement the advanced serviceability techniques that enable efficient service of the systems and to help determine the failing items.

In the rare absence of FFDC and Error Data Analysis, diagnostics are required to re-create the failure and determine the failing items.

Diagnostics

General diagnostic objectives are to detect and identify problems so they can be resolved quickly. Elements of IBM's diagnostics strategy include:

  • Provide a common error code format equivalent to a system reference code with PowerVM, system reference number, checkpoint, or firmware error code.
  • Provide fault detection and problem isolation procedures. Support remote connection ability to be used by the IBM Remote Support Center or IBM Designated Service.
  • Provide interactive intelligence within the diagnostics with detailed online failure information while connected to IBM's backend system.

Automatic diagnostics

The processor and memory FFDC technology is designed to perform without the need for recreate diagnostics nor require user intervention. Solid and intermittent errors are designed to be correctly detected and isolated at the time the failure occurs. Runtime and boot-time diagnostics fall into this category.

Standalone diagnostics

As the name implies, standalone or user-initiated diagnostics requires user intervention. The user must perform manual steps, including:

  • Booting from the diagnostics CD, DVD, USB, or network
  • Interactively selecting steps from a list of choices

Concurrent maintenance

The determination of whether a firmware release can be updated concurrently is identified in the readme information file that is released with the firmware. An HMC is required for the concurrent firmware update with PowerVM. In addition, concurrent maintenance of PCIe adapters and NVMe drives are supported with PowerVM. Power supplies, fans are hot pluggable.

Service labels

Service providers use these labels to assist them in performing maintenance actions. Service labels are found in various formats and positions and are intended to transmit readily available information to the servicer during the repair process. Following are some of these service labels and their purpose:

  • Location diagrams: Location diagrams are located on the system hardware, relating information regarding the placement of hardware components. Location diagrams may include location codes, drawings of physical locations, concurrent maintenance status, or other data pertinent to a repair. Location diagrams are especially useful when multiple components such as DIMMs, processors, fans, adapter cards, and power supplies are installed.
  • Remove/replace procedures: Service labels that contain remove/replace procedures are often found on a cover of the system or in other spots accessible to the servicer. These labels provide systematic procedures, including diagrams detailing how to remove or replace certain serviceable hardware components.
  • Arrows: Numbered arrows are used to indicate the order of operation and the serviceability direction of components. Some serviceable parts such as latches, levers, and touch points need to be pulled or pushed in a certain direction and in a certain order for the mechanical mechanisms to engage or disengage. Arrows generally improve the ease of serviceability.

QR labels

QR labels are placed on the system to provide access to key service functions through a mobile device. When the QR label is scanned, it will go to a landing page for Power10 processor-based systems that contains each MTM service functions of interest while physically located at the server. These include things such as installation and repair instructions, reference code look up, and so on.

Packaging for service

The following service features are included in the physical packaging of the systems to facilitate service:

  • Color coding (touch points): Blue-colored touch points delineate touchpoints on service components where the component can be safely handled for service actions such as removal or installation.
  • Tool-less design: Selected IBM systems support tool-less or simple tool designs. These designs require no tools or simple tools such as flathead screw drivers to service the hardware components.
  • Positive retention: Positive retention mechanisms help to assure proper connections between hardware components such as cables to connectors, and between two cards that attach to each other. Without positive retention, hardware components run the risk of becoming loose during shipping or installation, preventing a good electrical connection. Positive retention mechanisms like latches, levers, thumbscrews, pop Nylatches (U-clips), and cables are included to help prevent loose connections and aid in installing (seating) parts correctly. These positive retention items do not require tools.

Error handling and reporting

In the event of system hardware or environmentally induced failure, the system runtime error capture capability systematically analyzes the hardware error signature to determine the cause of failure. The analysis result will be stored in system NVRAM. When the system can be successfully restarted either manually or automatically, or if the system continues to operate, the error will be reported to the operating system. Hardware and software failures are recorded in the system log filesystem. When an HMC is attached in the PowerVM environment, an ELA routine analyzes the error, forwards the event to the Service Focal Point (SFP) application running on the HMC, and notifies the system administrator that it has isolated a likely cause of the system problem. The service processor event log also records unrecoverable checkstop conditions, forwards them to the SFP application, and notifies the system administrator.

The system has the ability to call home through the operating system to report platform-recoverable errors and errors associated with PCI adapters/devices.

In the HMC-managed environment, a call home service request will be initiated from the HMC and the pertinent failure data with service parts information and part locations will be sent to an IBM service organization. Customer contact information and specific system- related data such as the machine type, model, and serial number, along with error log data related to the failure, are sent to IBM Service.

Live Partition Mobility

With PowerVM Live Partition Mobility (LPM), users can migrate an AIX, IBM I, or Linux VM partition running on one Power partition system to another Power system without disrupting services. The migration transfers the entire system environment, including processor state, memory, attached virtual devices, and connected users. It provides continuous operating system and application availability during planned partition outages for repair of hardware and firmware faults. The Power10 systems, using Power10 technology, support secure LPM, whereby the VM image is encrypted and compressed prior to transfer. Secure LPM uses on-chip encryption and compression capabilities of the Power10 processor for optimal performance.

Call home

Call home refers to an automatic or manual call from a client location to the IBM support structure with error log data, server status, or other service-related information. Call home invokes the service organization in order for the appropriate service action to begin. Call home can be done through the Electronic Service Agent (ESA) imbedded in the HMC or through a version of ESA imbedded in the operating systems for non-HMC-managed or A version of ESA that runs as a standalone call home application. While configuring call home is optional, clients are encouraged to implement this feature in order to obtain service enhancements such as reduced problem determination and faster and potentially more accurate transmittal of error information. In general, using the call home feature can result in increased system availability. See the next section for specific details on this application.

IBM Electronic Services

Electronic Service Agent and Client Support Portal (CSP) comprise the IBM Electronic Services solution, which is dedicated to providing fast, exceptional support to IBM clients. IBM Electronic Service Agent is a no-charge tool that proactively monitors and reports hardware events such as system errors and collects hardware and software inventory. Electronic Service Agent can help focus on the client's company business initiatives, save time, and spend less effort managing day-to-day IT maintenance issues. In addition, Call Home Connect Cloud web and mobile capability extends the common solution and offers IBM Systems-related support information applicable to servers and storage.

Details are available here: https://clientvantage.ibm.com/channel/ibm-call-home-connect.

System configuration and inventory information collected by Electronic Service Agent also can be used to improve problem determination and resolution between the client and the IBM support team. As part of an increased focus to provide even better service to IBM clients, Electronic Service Agent tool configuration and activation comes standard with the system. In support of this effort, a HMC External Connectivity security whitepaper has been published, which describes data exchanges between the HMC and the IBM Service Delivery Center (SDC) and the methods and protocols for this exchange. To read the whitepaper and prepare for Electronic Service Agent installation, see the "Security" section at the IBM Electronic Service Agent.

Benefits: increased uptime

Electronic Service Agent is designed to enhance the warranty and maintenance service by potentially providing faster hardware error reporting and uploading system information to IBM Support. This can optimize the time monitoring the symptoms, diagnosing the error, and manually calling IBM Support to open a problem record. And 24x7 monitoring and reporting means no more dependency on human intervention or off-hours client personnel when errors are encountered in the middle of the night.

Security: The Electronic Service Agent tool is designed to help secure the monitoring, reporting, and storing of the data at IBM. The Electronic Service Agent tool is designed to help securely transmit through the internet (HTTPS) to provide clients a single point of exit from their site. Initiation of communication is one way. Activating Electronic Service Agent does not enable IBM to call into a client's system.

For additional information, see the IBM Electronic Service Agent website.

More accurate reporting

Because system information and error logs are automatically uploaded to the IBM Support Center in conjunction with the service request, clients are not required to find and send system information, decreasing the risk of misreported or misdiagnosed errors. Once inside IBM, problem error data is run through a data knowledge management system, and knowledge articles are appended to the problem record.

Client Support Portal

Client Support Portal is a single internet entry point that replaces the multiple entry points traditionally used to access IBM Internet services and support. This web portal enables you to gain easier access to IBM resources for assistance in resolving technical problems.

This web portal provides valuable reports of installed hardware and software using information collected from the systems by IBM Electronic Service Agent. Reports are available for any system associated with the client's IBM ID.

For more information on how to utilize client support portal, visit the following website or contact an IBM Systems Services Representative:

  • https://www.ibm.com/mysupport


Back to topBack to top

Models

Top rule

Model summary matrix

Model Processor Speed Memory Hard Drive CD-ROM
MRX 48 cores 3.60 GHz to 4.0 GHz (MAX) 256 GB to 16 TB Up to 10 NVMe drives No
72 cores 3.20 GHz to 4.0 GHz (MAX)
96 cores 2.95 GHz to 3.90 GHz

Customer setup (CSU)

Yes.

Devices supported

N/A

Model conversions

Not available.

Feature conversions

The existing components being replaced during a model or feature conversion become the property of IBM and must be returned.

Feature conversions are always implemented on a "quantity of one for quantity of one" basis. Multiple existing features may not be converted to a single new feature. Single existing features may not be converted to multiple new features.

The following conversions are available to clients:

The following conversions are available to customers:

Feature conversions for 9043-MRX memory features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EHCB - 512GB Base Memory     ERQT - 512GB Base Memory     No
activation for MRX #EHC8     Activation for Pools2.0
                             (convert Healthcare)

Feature conversions for 9043-MRX processor features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EHCA - Processor Activation  ERQQ - 1 Base Processor      No
for Healthcare Solution      Activation (PEP 2.0
(#EHC8)                      Healthcare) for #EPGW - any
                             O/S (Conv from HSE)

Feature conversions for 9043-MRX adapters features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EJ20 - PCIe x 16 to CXP      EJ2A -PCIe3 x 16 to CXP      No
Optical or CU converter      Converter Adapter (support)
Adapter for PCIe3 Expansion  AOC)
Drawer
EJ35 - PCIe3 Crypto          EJ37 - PCIe3 Crypto          No
Coprocessor no BSC 4769      Coprocessor BSC-Gen3 4769

Feature conversions for 9043-MRX cable features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
ECC7 - 3M Optical Cable      ECCX - 3M Active Optical     No
Pair for PCIe3 Expansion     Cable Pair for PCIe3
Drawer                       Expansion Drawer
ECC8 - 10M Optical Cable     ECCY - 10M Active Optical    No
Pair for PCIe3 Expansion     Cable Pair for PCIe3
Drawer                       Expansion Drawer

Feature conversions for 9043-MRX global resource activation features:

                                                           RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EP2X - Lab Services Private  EP20 - Power Enterprise      No
Cloud Capacity Assessment    Pools 2.0 Enablement

Feature conversions for 9043-MRX memory features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EMCP - 1GB Memory            EPSR - 1GB Base Memory       No
Activations for MRX          Activation for Pools 2.0
                             (From Static)
EMCQ - 100GB Memory          EPSS - 100GB Base Memory     No
Activations for MRX          Activation for Pools 2.0
                             (From Static)
EMCE - 512 of #EMCP          EPSQ - 512GB Base Memory     No
1GB Memory                   Activation for Pools 2.0
Activations for MRX          (From Static)
EMCG - 512 of #EMCP          EPST - 512GB Base Memory     No
1GB Linux Memory             Activation for Pools 2.0
Activations for MRX          (From Linux)

Feature conversions for 9043-MRX processor features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EPUR - 1 core Processor      EPSA - 1 core Base           No
Activation for #EPEU         Processor Activation (Pools
                             2.0) for #EPEU (From Static)
EPUS - 1 core Processor      EPSB - 1 core Base           No
Activation for #EPEV         Processor Activation (Pools
                             2.0) for #EPEV (From Static)
EPYT - 1 core Processor      EPSD - 1 core Base           No
Activation for #EPGW         Processor Activation (Pools
                             2.0) for #EPGW (From Static)
ELBW - 1 core Processor      EPSE - 1 core Base           No
Activation for #EPEU Linux   Processor Activation (Pools
only                         2.0) for #EPEU (From
                             Static) Linux only
ELBX - 1 core Processor      EPSF - 1 core Base           No
Activation for #EPEV Linux   Processor Activation (Pools
only                         2.0) for #EPEV (From
                             Static) Linux only
ELBY - 1 core Processor      EPSH - 1 core Base           No
Activation for #EPGW Linux   Processor Activation (Pools
only                         2.0) for #EPGW (From
                             Static) Linux only

Feature conversions for 9043-MRX rack-related features:

                                                          RETURN
From FC:                     To FC:                        PARTS
---------------------------- ---------------------------- ------
EMXG - PCIe3 6-Slot Fanout   EMXH - PCIe3 6-Slot Fanout   No
Module for PCIe3 Expansion   Module for PCIe3 Expansion
Drawer                       Drawer


Back to topBack to top

Technical description

Top rule

Physical specifications Physical specifications Hardware requirements Hardware requirements
Operating environment Operating environment Software requirements Software requirements
Limitations Limitations


Not Applicable

Physical specifications

Power E1050 (9043-MRX)

System node

  • Width: 448 mm (17.6 in.)
  • Depth: 902 mm (35.5 in.)
  • Height: 175 mm (6.9 in.), 4 EIA units
  • Weight: 69 kg (153 lb)

Note: The EMX0 remote I/O drawer connection in the T42 and S42 racks will stop the rear door from closing, thus requiring the mandatory 8-inch rack extensions.

PCIe I/O expansion drawer

  • Width: 448 mm (17.5 in.)
  • Depth: 736.6 mm (29 in.)
  • Height: 177.8 mm (7.0 in.), 4 EIA units
  • Weight: 54.4 kg (120 lb)

To assure installability and serviceability in non-IBM industry- standard racks, review the installation planning information for any product-specific installation requirements.

Operating environment

  • Temperature:
    • 5°C--45°C (41°F--113°F) nonoperating
    • 18°C--27°C (64.4°F--80.6°F) recommended operating
    • 5°C--40°C (41°F--104°F) allowable operating
    • Derate maximum allowable dry-bulb temperature 1°C (1.8°F) per 175 m (574 ft) above 900 m (2,953 ft) up to a maximum allowable elevation of 3050 m (10,000 ft).
  • Relative humidity (noncondensing):
    • 5%--85% RH nonoperating
    • 8%--80% operating
  • Maximum dew point:
    • 27°C (80°F) nonoperating
    • 24°C (75°F) operating
  • Operating voltage: 200--240 V AC
    • ASHRAE class: A3 (fourth edition)
    • Operating frequency: 50--60 Hz +/-3 Hz
    • Maximum Power consumption: 4,950 watts (per system node)
    • Power source loading: 5.1 kVA maximum (per system node)
    • Thermal output: 16,889 Btu/hr maximum (per system node)
    • Maximum altitude: 3,050 m (10,000 ft)
      • To calculate the amperage, multiply the kVA by 1000 and divide that number by the operating voltage.
      • Model 9043-MRX use four power supply units.
  • Noise level: (Acoustics A-weighted Upper-Limit Sound Power Levels)
    • One typically configured Four processors, 2 TB memory:
      • 7.2 bels (operating/idle: 25 C, 500 m)
    • One maximum configured Four processor, 2 TB memory:
      • 8.2 bels (heavy workload, 25 C, 500 m)

The Power E1050 server must be installed in a rack with a rear door and side panels for EMC compliance. The native HMC Ethernet ports must use shielded Ethernet cables.

Note: Government regulations, such as those prescribed by OSHA or European Community Directives, may govern noise level exposure in the workplace and may apply to you and your server installation. This IBM system is available with an optional acoustical door feature that can help reduce the noise emitted from this system. The actual sound pressure levels in your installation depend upon a variety of factors, including the number of racks in the installation; the size, materials, and configuration of the room where you designate the racks to be installed; the noise levels from other equipment; the room ambient temperature, and employees' location in relation to the equipment. Further, compliance with such government regulations also depends upon a variety of additional factors, including the duration of employees' exposure and whether employees wear hearing protection. IBM recommends that you consult with qualified experts in this field to determine whether you are in compliance with the applicable regulations.

EMC conformance classification

This equipment is subject to Electromagnetic Compatibility (EMC) regulations and shall comply with the appropriate country EMC regulations before final delivery to the buyer or centers of distribution.

  • US: FCC CFR, Title 47, Part 15, EMI Class A
  • EEA, Turkey: EU Council Directive 2014/30/EU, EMI Class A
  • Japan: VCCI Council, EMI Class A
  • Korea: RRA, EMI Class A
  • China (PRC): CPCS, EMI Class A
  • Taiwan R.O.C.: BSMI CNS 13438, EMI Class A
  • Australia\New Zealand: ACMA, EMI Class A
  • Canada: ICES-003, EMI Class A
  • Eurasian Economic Area (EAEU), EMI Class A
  • Saudi Arabia: MoCI, EMI Class A
  • Vietnam: MIC, EMI Class A
  • Morocco EMC Order, EMC Class A

Homologation 2-- Telecom type approval

Homologation approval for specific countries has been initiated with the IBM Homologation and Type Approval (HT&A) organization in Nice, France.

The IBM Power E1050 server nodes or system control unit or PCIe Expansion units are not certified for connection to interfaces of public telecommunications networks. Certification may be required by law prior to making any such connection. Contact an IBM representative or reseller for any questions and for information on PCIe adapters that can be used in the system and which are certified.

Product safety/country testing/certification

  • UL 60950-1:2007 Underwriters Laboratory
  • CAN/CSA22.2 No. 60950-1-07
  • EN60950-1:2006 European Norm
  • IEC 60950-1 2nd Edition + all National Differences

Limitations

Not applicable.

Hardware requirements

Not applicable.

Software requirements

If installing the AIX operating system LPAR with any I/O configuration (one of these):

  • AIX Version 7.3 with the 7300-00 Technology Level and Service Pack 7300-00-02-2220, or later
  • AIX Version 7.2 with the 7200-05 Technology Level and Service Pack 7200-05-04-2220, or later
  • AIX Version 7.2 with the 7200-04 Technology Level and Service Pack 7200-04-06-2220, or later (planned availability September 16, 2022)

If installing the AIX operating system Virtual I/O only LPAR (one of these):

  • AIX Version 7.3 with the 7300-00 Technology Level and service pack 7300-00-01-2148, or later
  • AIX Version 7.2 with the 7200-05 Technology Level and service pack 7200-05-01-2038, or later
  • AIX Version 7.2 with the 7200-04 Technology Level and Service Pack 7200-04-02-2016, or later
  • AIX Version 7.1 with the 7100-05 Technology Level and Service Pack 7100-05-06-2016, or later

See the IBM Prerequisite website for compatibility information for hardware features and the corresponding AIX Technology Levels.

If installing the Linux operating system (one of these):

  • Red Hat Enterprise Linux 8.4, for Power LE, or later
  • Red Hat Enterprise Linux 9.0, for Power LE, or later
  • SUSE Linux Enterprise Server 15 Service Pack 3, or later
  • SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise Server 15 Service Pack 3, or later
  • Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 8.4 for Power LE, or later
  • Red Hat OpenShift Container Platform 4.9, or later

Please review the Linux alert page for any known Linux issues or limitations.
Note: The above list applies to the installation of the Linux operating system LPAR in non-production SAP HANA implementations. Reference "IBM Power E1050 (9040-MRX) for SAP HANA Production Use" Statement of Direction for production support.

If installing VIOS:

  • VIOS 3.1.3.21, or later

Java is supported on Power10 servers. For best use of the performance capabilities and the most recent improvements of Power10 technology, IBM recommends upgrading Java-based applications to Java 7, Java 8, or later, whenever possible. For those clients who want to run Java in AIX environments, see the AIX Download and service information website.

For Linux (including PowerLinux), see the Linux Download information website.

Recommendation: Clients are strongly encouraged to move to a more current supported version: Java 7, Java 7.1, Java 8, or later.



Back to topBack to top

Publications

Top rule

No publications are shipped with the announced product.

To access the IBM Publications Center Portal, go to the IBM Publications Center website.

The Publications Center is a worldwide central repository for IBM product publications and marketing material with a catalog of 70,000 items. Extensive search facilities are provided. A large number of publications are available online in various file formats, which can currently be downloaded.



Back to topBack to top

Features

Top rule

Features - No charge Features - No charge Feature descriptions Feature descriptions
Features - Chargeable Features - Chargeable Feature exchanges Feature exchanges
Feature availability matrix Feature availability matrix


Features - No charge

  • NONE

Features - Chargeable

Special Features - Initial Orders
  • Administrative
    • (#B0PR) -SP Hard Drive/Media Retention - Power 5 years
    • (#B0VH) -SP HDR/MR POWER 3Y
    • (#ESC7) -S&H
    • (#ESWK) -AIX Update Access Key (UAK)
    • (#SVPC) -5000 Power to Cloud Reward points
  • Editions
    • (#ELG4) -IBM Power Private Cloud Rack for OracleDB Solution Indicator
  • Languages
    • (#9300) -Language Group Specify - US English
    • (#9700) -Language Group Specify - Dutch
    • (#9703) -Language Group Specify - French
    • (#9704) -Language Group Specify - German
    • (#9705) -Language Group Specify - Polish
    • (#9706) -Language Group Specify - Norwegian
    • (#9707) -Language Group Specify - Portuguese
    • (#9708) -Language Group Specify - Spanish
    • (#9711) -Language Group Specify - Italian
    • (#9712) -Language Group Specify - Canadian French
    • (#9714) -Language Group Specify - Japanese
    • (#9715) -Language Group Specify - Traditional Chinese (Taiwan)
    • (#9716) -Language Group Specify - Korean
    • (#9718) -Language Group Specify - Turkish
    • (#9719) -Language Group Specify - Hungarian
    • (#9720) -Language Group Specify - Slovakian
    • (#9721) -Language Group Specify - Russian
    • (#9722) -Language Group Specify - Simplified Chinese (PRC)
    • (#9724) -Language Group Specify - Czech
    • (#9725) -Language Group Specify - Romanian
    • (#9726) -Language Group Specify - Croatian
    • (#9727) -Language Group Specify - Slovenian
    • (#9728) -Language Group Specify - Brazilian Portuguese
    • (#9729) -Language Group Specify - Thai
  • Linecords
    • (#6577) -Power Cable - Drawer to IBM PDU, 200-240V/10A
    • (#END3) -Power Cable - Drawer to IBM PDU, 200-240V/10A for India
    • (#END7) -Power Cable - Drawer to IBM PDU (250V/10A) for India
  • Memory
    • (#EMBM) -Power Active Memory Expansion
  • Miscellaneous
    • (#5000) -Software Preload Required
    • (#9461) -Month Indicator
    • (#9462) -Day Indicator
    • (#9463) -Hour Indicator
    • (#9464) -Minute Indicator
    • (#9465) -Qty Indicator
    • (#9466) -Countable Member Indicator
  • Services
    • (#0456) -Customer Specified Placement
    • (#B0VP) -SP Machine Setup Support for Power
  • Specify Codes
    • (#4650) -Rack Indicator-Not Factory Integrated
    • (#4651) -Rack Indicator, Rack #1
    • (#4652) -Rack Indicator, Rack #2
    • (#4653) -Rack Indicator, Rack #3
    • (#4654) -Rack Indicator, Rack #4
    • (#4655) -Rack Indicator, Rack #5
    • (#4656) -Rack Indicator, Rack #6
    • (#4657) -Rack Indicator, Rack #7
    • (#4658) -Rack Indicator, Rack #8
    • (#4659) -Rack Indicator, Rack #9
    • (#4660) -Rack Indicator, Rack #10
    • (#4661) -Rack Indicator, Rack #11
    • (#4662) -Rack Indicator, Rack #12
    • (#4663) -Rack Indicator, Rack #13
    • (#4664) -Rack Indicator, Rack #14
    • (#4665) -Rack Indicator, Rack #15
    • (#4666) -Rack Indicator, Rack #16
    • (#9169) -Order Routing Indicator-System Plant
    • (#9440) -New AIX License Core Counter
    • (#9442) -New Red Hat License Core Counter
    • (#9443) -New SUSE License Core Counter
    • (#9444) -Other AIX License Core Counter
    • (#9445) -Other Linux License Core Counter
    • (#9446) -3rd Party Linux License Core Counter
    • (#9447) -VIOS Core Counter
    • (#9449) -Other License Core Counter
    • (#9450) -Ubuntu Linux License Core Counter
    • (#ESCZ) -iSCSI SAN Load Source Specify for AIX
  • Standard Factory Services
    • (#4649) -Rack Integration Services
Special Features - Plant and/or Field Installable
  • Adapters
    • (#5899) -PCIe2 4-port 1GbE Adapter
    • (#EC2S) -PCIe3 2-Port 10Gb NIC&ROCE SR/Cu Adapter
    • (#EC2T) -PCIe3 LP 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter
    • (#EC2U) -PCIe3 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter
    • (#EC5B) -PCIe3 x8 1.6 TB NVMe Flash Adapter for AIX/Linux
    • (#EC5D) -PCIe3 x8 3.2 TB NVMe Flash Adapter for AIX/Linux
    • (#EC5F) -PCIe3 x8 6.4 TB NVMe Flash Adapter for AIX/Linux
    • (#EC66) -PCIe4 2-port 100Gb ROCE EN adapter
    • (#EC6K) -PCIe2 2-Port USB 3.0 Adapter
    • (#EC76) -PCIe4 2-port 100Gb No Crypto Connectx-6 DX QFSP56
    • (#EC7B) -PCIe4 1.6TB NVMe Flash Adapter x8 for AIX/Linux
    • (#EC7D) -PCIe4 3.2TB NVMe Flash Adapter x8 for AIX/Linux
    • (#EC7F) -PCIe4 6.4TB NVMe Flash Adapter x8 for AIX/Linux
    • (#EJ0J) -PCIe3 RAID SAS Adapter Quad-port 6Gb x8
    • (#EJ0L) -PCIe3 12GB Cache RAID SAS Adapter Quad-port 6Gb x8
    • (#EJ10) PCIe3 SAS Tape/DVD Adapter Quad-port 6Gb x8
    • (#EJ14) -PCIe3 12GB Cache RAID PLUS SAS Adapter Quad-port 6Gb x8
    • (#EJ2A) -PCIe3 x16 to CXP Converter Adapter (support AOC)
    • (#EJ32) -PCIe3 Crypto Coprocessor no BSC 4767
    • (#EJ33) -PCIe3 Crypto Coprocessor BSC-Gen3 4767
    • (#EJ35) -PCIe3 Crypto Coprocessor no BSC 4769
    • (#EJ37) -PCIe3 Crypto Coprocessor BSC-Gen3 4769
    • (#EN0A) -PCIe3 16Gb 2-port Fibre Channel Adapter
    • (#EN0S) -PCIe2 4-Port (10Gb+1GbE) SR+RJ45 Adapter
    • (#EN0U) -PCIe2 4-port (10Gb+1GbE) Copper SFP+RJ45 Adapter
    • (#EN0W) -PCIe2 2-port 10/1GbE BaseT RJ45 Adapter
    • (#EN1A) -PCIe3 32Gb 2-port Fibre Channel Adapter
    • (#EN1C) -PCIe3 16Gb 4-port Fibre Channel Adapter
    • (#EN1E) -PCIe3 16Gb 4-port Fibre Channel Adapter
    • (#EN1G) -PCIe3 2-Port 16Gb Fibre Channel Adapter
    • (#EN1J) -PCIe4 32Gb 2-port Optical Fibre Channel Adapter
    • (#EN1L) -PCIe4 32Gb 4-port Optical Fibre Channel Adapter
    • (#EN1N) -PCIe4 64Gb 2-port Optical Fibre Channel Adapter
    • (#EN2A) -PCIe3 16Gb 2-port Fibre Channel Adapter
    • (#EN2W) -PCIe3 4-port 10GbE BaseT RJ45 Adapter
  • Administrative
    • (#0719) -Load Source Not in CEC
    • (#EHS2) -SSD Placement Indicator - #ESLS/#ELLS
    • (#ESC0) -S&H - No Charge
    • (#ESCT) -Virtual Capacity Expedited Shipment
  • Cable
    • (#7802) -Ethernet Cable, 15m, Hardware Management Console to System Unit
    • (#EB2J) -10m (30.3-ft) - IBM MTP 12 strand cable for 40/100G transceivers
    • (#EB2K) -30m (90.3-ft) - IBM MTP 12 strand cable for 40/100G transceivers
    • (#EB46) -10GbE Optical Transceiver SFP+ SR
    • (#EB47) -25GbE Optical Transceiver SFP28
    • (#EB48) -1GbE Base-T Transceiver RJ45
    • (#EB49) -QSFP28 to SFP28 Connector
    • (#EB4J) -0.5m SFP28/25GbE copper Cable
    • (#EB4K) -1.0m SFP28/25GbE copper Cable
    • (#EB4M) -2.0m SFP28/25GbE copper Cable
    • (#EB4P) -2.0m QSFP28/100GbE copper split Cable to SFP28 4x25GbE
    • (#EB57) -QSFP+ 40GbE Base-SR4 Transceiver
    • (#EB59) -100GbE Optical Transceiver QSFP28
    • (#EB5K) -1.0M 100GbE Copper Cable QSFP28
    • (#EB5L) -1.5M 100GbE Copper Cable QSFP28
    • (#EB5M) -2.0M 100GbE Copper Cable QSFP28
    • (#EB5R) -3M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5S) -5M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5T) -10M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5U) -15M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5V) -20M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5W) -30M 100GbE Optical Cable QSFP28 (AOC)
    • (#EB5X) -50M 100GbE Optical Cable QSFP28 (AOC)
    • (#ECB2) -1.5m (4.9-ft), Blue CAT5 Ethernet Cable
    • (#ECBJ) -SAS X Cable 3m - HD Narrow 6Gb 2-Adapters to Enclosure
    • (#ECBK) -SAS X Cable 6m - HD Narrow 6Gb 2-Adapters to Enclosure
    • (#ECBM) -SAS X Cable 15m - HD Narrow 3Gb 2-Adapters to Enclosure
    • (#ECBT) -SAS YO Cable 1.5m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECBU) -SAS YO Cable 3m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECBV) -SAS YO Cable 6m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECBW) -SAS YO Cable 10m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECBY) -SAS AE1 Cable 4m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECBZ) -SAS YE1 Cable 3m - HD Narrow 6Gb Adapter to Enclosure
    • (#ECCF) -System Port Converter Cable for UPS
    • (#ECCS) -3M Copper CXP Cable Pair for PCIe3 Expansion Drawer
    • (#ECCX) -3M Active Optical Cable Pair for PCIe3 Expansion Drawer
    • (#ECCY) -10M Active Optical Cable Pair for PCIe3 Expansion Drawer
    • (#ECDJ) -3.0M SAS X12 Cable (Two Adapter to Enclosure)
    • (#ECDK) -4.5M SAS X12 Active Optical Cable (Two Adapter to Enclosure)
    • (#ECDL) -10M SAS X12 Active Optical Cable (Two Adapter to Enclosure)
    • (#ECDT) -1.5M SAS YO12 Cable (Adapter to Enclosure)
    • (#ECDU) -3.0M SAS YO12 Cable (Adapter to Enclosure)
    • (#ECDV) -4.5M SAS YO12 Active Optical Cable (Adapter to Enclosure)
    • (#ECDW) -10M SAS YO12 Active Optical Cable (Adapter to Enclosure)
    • (#ECE0) -0.6M SAS AA12 Cable (Adapter to Adapter)
    • (#ECE3) -3.0M SAS AA12 Cable
    • (#ECE4) -4.5M SAS AA12 Active Optical Cable (Adapter to Adapter)
    • (#ECW0) -Optical Wrap Plug
    • (#EN01) -1m (3.3-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
    • (#EN02) -3m (9.8-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
    • (#EN03) -5m (16.4-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
  • Disk
    • (#1953) -300GB 15k RPM SAS SFF-2 Disk Drive (AIX/Linux)
    • (#1964) -600GB 10k RPM SAS SFF-2 HDD for AIX/Linux
    • (#ESEV) -600GB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
    • (#ESF3) -1.2TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
    • (#ESFT) -1.8TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
    • (#ESNM) -300GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/ Linux)
    • (#ESNR) -600GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/ Linux)
  • Global Resource Activation
    • (#EP2X) -Lab Services Private Cloud Capacity Assessment
    • (#EP20) -Power Enterprise Pools 2.0 Enablement
  • Linecords
    • (#4558) -Power Cord To PDU/UPS, (100-240V/16A)
    • (#6458) -Power Cord 4.3m (14-ft), Drawer to IBM PDU (250V/10A)
    • (#6460) -Power Cord 4.3m (14-ft), Drawer To OEM PDU (125V, 15A)
    • (#6469) -Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (250V/ 15A) U. S.
    • (#6470) -Power Cord 1.8m (6-ft), Drawer to Wall (125V/15A)
    • (#6471) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/ 10A)
    • (#6472) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/ 16A)
    • (#6473) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/ 10A)
    • (#6474) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 13A)
    • (#6475) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 16A)
    • (#6476) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 10A)
    • (#6477) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 16A)
    • (#6478) -Power Cord 2.7 M(9-foot), To Wall/OEM PDU, (250V, 16A)
    • (#6488) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (125V/ 15A or 250V/10A )
    • (#6489) -4.3m (14-Ft) 3PH/32A 380-415V Power Cord
    • (#6491) -4.3m (14-Ft) 1PH/63A 200-240V Power Cord
    • (#6492) -4.3m (14-Ft) 1PH/60A (48A derated) 200-240V Power Cord
    • (#6493) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 10A)
    • (#6494) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 10A)
    • (#6496) -Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 10A)
    • (#6651) -Power Cord 2.7M (9-foot), To Wall/OEM PDU, (125V, 15A)
    • (#6653) -4.3m (14-Ft) 3PH/16A 380-415V Power Cord
    • (#6654) -4.3m (14-Ft) 1PH/30A (24A derated) Power Cord
    • (#6655) -4.3m (14-Ft) 1PH/30A (24A derated) WR Power Cord
    • (#6656) -4.3m (14-Ft) 1PH/32A Power Cord
    • (#6657) -4.3m (14-Ft) 1PH/32A Power Cord-Australia
    • (#6658) -4.3m (14-Ft) 1PH/30A (24A derated) Power Cord-Korea
    • (#6659) -Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 15A)
    • (#6660) -Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (125V/ 15A)
    • (#6665) -Power Cord 2.8m (9.2-ft), Drawer to IBM PDU, (250V/10A)
    • (#6667) -4.3m (14-Ft) 3PH/32A 380-415V Power Cord-Australia
    • (#6669) -Power Cord 4.3M (14-foot), Drawer to OEM PDU, (250V, 15A)
    • (#6671) -Power Cord 2.7M (9-foot), Drawer to IBM PDU, 250V/10A
    • (#6672) -Power Cord 2M (6.5-foot), Drawer to IBM PDU, 250V/10A
    • (#6680) -Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/ 10A)
    • (#ECJ5) -4.3m (14-Ft) PDU to Wall 3PH/24A 200-240V Delta-wired Power Cord
    • (#ECJ6) -4.3m (14-Ft) PDU to Wall 3PH/40A 200-240V Power Cord
    • (#ECJ7) -4.3m (14-Ft) PDU to Wall 3PH/48A 200-240V Delta-wired Power Cord
    • (#ELC0) -PDU Access Cord 0.38m
    • (#ELC1) -4.3m (14-Ft) PDU to Wall 24A 200-240V Power Cord North America
    • (#ELC2) -4.3m (14-Ft) PDU to Wall 3PH/24A 415V Power Cord North America
    • (#ELC5) -Power Cable - Drawer to IBM PDU (250V/10A)
    • (#END0) -Power Cord 2M (6.5-foot), Drawer to IBM PDU, 250V/10A for India
    • (#END1) -Power Cord 2.7M (9-foot), Drawer to IBM PDU, 250V/10A for India
    • (#END2) -Power Cord 4.3m (14-ft), Drawer to IBM PDU (250V/10A) for India
    • (#END5) -Power Cord 2.8m (9.2-ft), Drawer to IBM PDU, (250V/10A) for India
    • (#END8) -Power Cord To PDU/UPS, (100-240V/16A) for India
  • Manufacturing Instruction
    • (#0373) -UPS Factory Integration Specify
    • (#0374) -HMC Factory Integration Specify
    • (#0375) -Display Factory Integration Specify
    • (#0376) -Reserve Rack Space for UPS
    • (#0377) -Reserve Rack Space for HMC
    • (#0378) -Reserve Rack Space for Display
    • (#EJRL) -Non-paired Indicator EJ14 PCIe SAS RAID+ Adapter
    • (#EJRU) -Non-paired Indicator EJ0L PCIe SAS RAID Adapter
    • (#EJW1) -Specify Mode-1 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for EXP24SX #ESLS/ELLS
    • (#EJW2) -Specify Mode-1 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS
    • (#EJW3) -Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS
    • (#EJW4) -Specify Mode-2 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS
    • (#EJW5) -Specify Mode-4 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS
    • (#EJW6) -Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS
    • (#EJW7) -Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS
    • (#EJWA) -Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for EXP24SX #ESLS/ELLS
    • (#EJWB) -Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS
    • (#EJWC) -Specify Mode-4 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS
    • (#EJWD) -Specify Mode-4 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS
    • (#EJWE) -Specify Mode-4 & (3)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS
    • (#EJWF) -Specify Mode-1 & (2)EJ14 & (2)YO12 for EXP24SX #ESLS/ ELLS
    • (#EJWG) -Specify Mode-2 & (2)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS
    • (#EJWH) -Specify Mode-2 & (2)EJ14 & (1)X12 for EXP24SX #ESLS/ELLS
    • (#EJWJ) -Specify Mode-2 & (4)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS
  • Media Devices
    • (#EUA5) -Standalone USB DVD drive w/cable
  • Memory
    • (#EHCB) -512GB Base Memory activation for MRX #EHC8
    • (#EM75) -64GB (2 x 32GB) DDR4 Memory Dimm
    • (#EM76) -128GB (2 x 64GB) DDR4 Memory Dimm
    • (#EM77) -256GB (2 x 128GB) DDR4 Memory Dimm
    • (#EM7J) -512GB (2 x 256GB) DDR4 Memory Dimm
    • (#EM81) -Active Memory Mirroring
    • (#EMCE) -512 of #EMCP 1GB Memory Activations for MRX
    • (#EMCG) -512 of #EMCP 1GB Linux Memory Activations for MRX
    • (#EMCP) -1GB Memory Activations for MRX
    • (#EMCQ) -100GB Memory Activations for MRX
    • (#EPSJ) -1GB Base Memory activation (Pools 2.0)
    • (#EPSP) -100GB Base Memory activation (Pools 2.0)
    • (#EPSQ) -512GB Base Memory Activation for Pools 2.0 (From Static)
    • (#EPSR) -1GB Base Memory Activation for Pools 2.0 (From Static)
    • (#EPSS) -100GB Base Memory Activation for Pools 2.0 (From Static)
    • (#EPST) -512GB Base Memory Activation for Pools 2.0 (From Linux)
    • (#EPSU) -256GB Base Memory Activation for Pools 2.0 - Linux only
    • (#EPSW) -256GB Base Memory Activation for Pools 2.0
    • (#ERQM) -256GB Base Memory Activation (Pools 2.0) (from Prev)
    • (#ERQN) -256GB Base Linux only Memory Activation (Pools 2.0) (from Prev)
    • (#ERQR) -512GB Base Memory Activation for Pools2.0
    • (#ERQS) -512GB Base Memory Activation for Pools2.0 Healthcare
    • (#ERQT) -512GB Base Memory Activation for Pools2.0 (convert Healthcare)
  • Miscellaneous
    • (#0983) -US TAA Compliance Indicator
    • (#0984) -Product assembled in USA manufacturing plant
    • (#1140) -Custom Service Specify, Rochester Minn, USA
    • (#2146) -Primary OS - AIX
    • (#2147) -Primary OS - Linux
    • (#ECSM) -Custom Service Specify, Mexico
    • (#ECSP) -Custom Service Specify, Poughkeepsie, USA
    • (#EHB1) -1x HW Subscription Increment
    • (#EHB2) -10x HW Subscription Increment
    • (#EHB3) -100x HW Subscription Increment
    • (#EHKV) -SAP HANA TRACKING FEATURE
    • (#EJ0Q) -Storage Backplane with Zero DASD 8 SAS 2.5" HDD/SDD Controllers
    • (#EU29) -Order Placed Indicator
    • (#SVBP) -BP Post-Sale Services: 1 Day
    • (#SVCS) -IBM Systems Lab Services Post-Sale Services: 1 Day
    • (#SVNN) -Other IBM Post-Sale Services: 1 Day
  • Power
    • (#EB39) -Power Supply - 2300W for Server (200-240 VAC)
    • (#ECJJ) -High Function 9xC19 Single-Phase or Three-Phase Wye PDU plus
    • (#ECJL) -High Function 9xC19 PDU plus 3-Phase Delta
    • (#ECJN) -High Function 12xC13 Single-Phase or Three-Phase Wye PDU plus
    • (#ECJQ) -High Function 12xC13 PDU plus 3-Phase Delta
    • (#EMXA) -AC Power Supply Conduit for PCIe3 Expansion Drawer
    • (#EPTJ) -High Function 9xC19 PDU: Switched, Monitoring
    • (#EPTL) -High Function 9xC19 PDU 3-Phase: Switched, Monitoring
    • (#EPTN) -High Function 12xC13 PDU: Switched, Monitoring
    • (#EPTQ) -High Function 12xC13 PDU 3-Phase: Switched, Monitoring
    • (#ESLA) -Specify AC Power Supply for EXP24SX Storage Enclosure
  • Processor
    • (#EHC8) -Solution Edition for Healthcare typical 2.95 to 3.9, 24-core processor module
    • (#EHCA) -Processor Activation for Healthcare Solution (#EHC8)
    • (#ELBW) -1-core Linux Processor Activation for #EPEU
    • (#ELBX) -1-core Linux Processor Activation for #EPEV
    • (#ELBY) -1-core Linux Processor Activation for #EPGW
    • (#EPEU) -12-core Typical 3.35 to 4.0 GHZ (max) processor
    • (#EPEV) -18-core Typical 3.20 to 4.0 GHZ (max) processor
    • (#EPGW) -24-core Typical 2.95 to 3.90 GHZ (max) processor
    • (#EPLU) -Front Heatsink + TIM PAD (For MRX)
    • (#EPLV) -Rear Heatsink + TIM PAD (For MRX)
    • (#EPRS) -1 core Base Processor Activation (Pools 2.0) for EPEU
    • (#EPRT) -1 core Base Processor Activation (Pools 2.0) for EPEV
    • (#EPRV) -1 core Base Processor Activation (Pools 2.0) for EPGW
    • (#EPRW) -1 core Base Linux Processor Activation (Pools 2.0) for EPEU
    • (#EPRX) -1 core Base Linux Processor Activation (Pools 2.0) for EPEV
    • (#EPRZ) -1 core Base Linux Processor Activation (Pools 2.0) for EPGW
    • (#EPSA) -1 core Base Processor Activation (Pools 2.0) for #EPEU (From Static)
    • (#EPSB) -1 core Base Processor Activation (Pools 2.0) for #EPEV (From Static)
    • (#EPSD) -1 core Base Processor Activation (Pools 2.0) for #EPGW (From Static)
    • (#EPSE) -1 core Base Processor Activation (Pools 2.0) for #EPEU (From Static) Linux only
    • (#EPSF) -1 core Base Processor Activation (Pools 2.0) for #EPEV (From Static) Linux only
    • (#EPSH) -1 core Base Processor Activation (Pools 2.0) for #EPGW (From Static) Linux only
    • (#EPUR) -1 core Processor Activation for #EPEU
    • (#EPUS) -1 core Processor Activation for #EPEV
    • (#EPYT) -1 core Processor Activation for #EPGW
    • (#ERQ0) -1 core Base Processor Activation (Pools 2.0) for EPEU (from Prev)
    • (#ERQ1) -1 core Base Processor Activation (Pools 2.0) for EPEV (from Prev)
    • (#ERQ2) -1 core Base Processor Activation (Pools 2.0) for EPGW (from Prev)
    • (#ERQ4) -1 core Base Linux only Processor Activation (Pools 2.0) for EPEU (from Prev)
    • (#ERQ5) -1 core Base Linux only Processor Activation (Pools 2.0) for EPEV (from Prev)
    • (#ERQ6) -1 core Base Linux only Processor Activation (Pools 2.0) for EPGW (from Prev)
    • (#ERQP) -1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW - any O/S
    • (#ERQQ) -1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW - any O/S (Conv from HSE)
  • Rack Related
    • (#EB2Z) -Lift Tool
    • (#EB3Z) -Lift tool based on GenieLift GL-8 (standard)
    • (#EB4Z) -Service wedge shelf tool kit for EB3Z
    • (#EMX0) -PCIe Gen3 I/O Expansion Drawer
    • (#EMXH) -PCIe3 6-Slot Fanout Module for PCIe3 Expansion Drawer
    • (#EPTH) -Horizontal PDU Mounting Hardware
    • (#ESLS) -EXP24SX SAS Storage Enclosure
  • Services
    • (#0010) -One CSC Billing Unit
    • (#0011) -Ten CSC Billing Units
  • Solid State Drive
    • (#EC5J) -Mainstream 800 GB SSD NVMe U.2 module
    • (#EC5K) -Mainstream 1.6 TB SSD NVMe U.2 module
    • (#EC5L) -Mainstream 3.2 TB SSD NVMe U.2 module
    • (#EC5V) -Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#EC5X) -Mainstream 800 GB SSD PCIe3 NVMe U.2 module for AIX/ Linux
    • (#EC7Q) -800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux
    • (#EC7T) -800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux
    • (#EC7X) -Carrier Conversion Kit for 7mm to 15mm NVMe Devices
    • (#EKF3) -Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#EKF5) -Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#EKF7) -Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES1E) -Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES1G) -Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES3B) -Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES3D) -Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES3F) -Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/ Linux
    • (#ES3H) -Enterprise 800GB SSD PCIe4 NVMe U.2 module for AIX/Linux
    • (#ES94) -387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESB2) -387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESB6) -775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESBA) -387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESBG) -775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESBL) -1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESGV) -387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESGZ) -775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESJ0) -931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJ2) -1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJ4) -3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJ6) -7.45TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJJ) -931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJL) -1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJN) -3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESJQ) -7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESK1) -387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESK3) -775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ESK8) -387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKC) -775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKG) -1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKK) -931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKP) -1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKT) -3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESKX) -7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESMB) -931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESMF) -1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESMK) -3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESMV) -7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESNA) -775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ESNE) -1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ETK1) -387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ETK3) -775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
    • (#ETK8) -387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ETKC) -775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
    • (#ETKG) -1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
  • Specify Codes
    • (#0265) -AIX Partition Specify
    • (#0266) -Linux Partition Specify
    • (#0837) -Fiber Channel SAN Load Source Specify
    • (#EHR2) -Boot Drive / Load Source in EXP24SX Specify (in #ESLS or #ELLS)
  • System Unit Base
    • (#ENSH) -IBM eBMC Indicator node 9043-MRX for China
  • Virtualization Engine
    • (#ELBV) -PowerVM for Linux indicator
    • (#EPA0) -Deactivation of LPM (Live Partition Mobility)
    • (#EPVV) -PowerVM - Enterprise Edition

Feature availability matrix

The following feature availability matrix for MT 9043 uses the letter "A" to indicate features that are available and orderable on the specified models. "S" indicates a feature that is supported on the new model during a model conversion; these features will work on the new model, but additional quantities of these features cannot be ordered on the new model; they can only be removed. "N" indicates that the feature is not supported on the new model and must be removed during the model conversion. As additional features are announced, supported, or withdrawn, this list will be updated. Please check with your Marketing Representative for additional information.

        |M| A = AVAILABLE  S = SUPPORTED
        |R| N = NOT SUPPORTED, MUST BE REMOVED
        |X|
        | |
FEAT/PN | |        DESCRIPTION
--------|-|----------------------------------------------------------

0010    |A| One CSC Billing Unit
0011    |A| Ten CSC Billing Units
0265    |A| AIX Partition Specify
0266    |A| Linux Partition Specify
0373    |A| UPS Factory Integration Specify
0374    |A| HMC Factory Integration Specify
0375    |A| Display Factory Integration Specify
0376    |A| Reserve Rack Space for UPS
0377    |A| Reserve Rack Space for HMC
0378    |A| Reserve Rack Space for Display
0456    |A| Customer Specified Placement
0719    |A| Load Source Not in CEC
0837    |A| Fiber Channel SAN Load Source Specify
0983    |A| US TAA Compliance Indicator
0984    |A| Product assembled in USA manufacturing plant
1140    |A| Custom Service Specify, Rochester Minn, USA
1953    |S| 300GB 15k RPM SAS SFF-2 Disk Drive (AIX/Linux)
1964    |S| 600GB 10k RPM SAS SFF-2 HDD for AIX/Linux
2146    |A| Primary OS - AIX
2147    |A| Primary OS - Linux
4558    |A| Power Cord To PDU/UPS, (100-240V/16A)
4649    |A| Rack Integration Services
4650    |A| Rack Indicator- Not Factory Integrated
4651    |A| Rack Indicator, Rack #1
4652    |A| Rack Indicator, Rack #2
4653    |A| Rack Indicator, Rack #3
4654    |A| Rack Indicator, Rack #4
4655    |A| Rack Indicator, Rack #5
4656    |A| Rack Indicator, Rack #6
4657    |A| Rack Indicator, Rack #7
4658    |A| Rack Indicator, Rack #8
4659    |A| Rack Indicator, Rack #9
4660    |A| Rack Indicator, Rack #10
4661    |A| Rack Indicator, Rack #11
4662    |A| Rack Indicator, Rack #12
4663    |A| Rack Indicator, Rack #13
4664    |A| Rack Indicator, Rack #14
4665    |A| Rack Indicator, Rack #15
4666    |A| Rack Indicator, Rack #16
5000    |A| Software Preload Required
5899    |S| PCIe2 4-port 1GbE Adapter
6458    |A| Power Cord 4.3m (14-ft), Drawer to IBM PDU (250V/10A)
6460    |A| Power Cord 4.3m (14-ft), Drawer To OEM PDU (125V, 15A)
6469    |A| Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (250V/15A)
        | |U. S.
6470    |S| Power Cord 1.8m (6-ft), Drawer to Wall (125V/15A)
6471    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/10A)
6472    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/16A)
6473    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/10A)
6474    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/13A)
6475    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/16A)
6476    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)
6477    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/16A)
6478    |A| Power Cord 2.7 M(9-foot), To Wall/OEM PDU, (250V, 16A)
6488    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (125V/15A
        | |or 250V/10A )
6489    |A| 4.3m (14-Ft) 3PH/32A 380-415V Power Cord
6491    |A| 4.3m (14-Ft) 1PH/63A 200-240V Power Cord
6492    |A| 4.3m (14-Ft) 1PH/60A (48A derated) 200-240V Power Cord
6493    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)
6494    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)
6496    |A| Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 10A)
6577    |A| Power Cable - Drawer to IBM PDU, 200-240V/10A
6651    |A| Power Cord 2.7M (9-foot), To Wall/OEM PDU, (125V, 15A)
6653    |A| 4.3m (14-Ft) 3PH/16A 380-415V Power Cord
6654    |A| 4.3m (14-Ft) 1PH/30A (24A derated) Power Cord
6655    |A| 4.3m (14-Ft) 1PH/30A (24A derated) WR Power Cord
6656    |A| 4.3m (14-Ft) 1PH/32A Power Cord
6657    |A| 4.3m (14-Ft) 1PH/32A Power Cord-Australia
6658    |A| 4.3m (14-Ft) 1PH/30A (24A derated) Power Cord-Korea
6659    |A| Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 15A)
6660    |A| Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (125V/15A)
6665    |A| Power Cord 2.8m (9.2-ft), Drawer to IBM PDU, (250V/10A)
6667    |A| 4.3m (14-Ft) 3PH/32A 380-415V Power Cord-Australia
6669    |A| Power Cord 4.3M (14-foot), Drawer to OEM PDU, (250V, 15A)
6671    |A| Power Cord 2.7M (9-foot), Drawer to IBM PDU, 250V/10A
6672    |A| Power Cord 2M (6.5-foot), Drawer to IBM PDU, 250V/10A
6680    |A| Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)
7802    |S| Ethernet Cable, 15m, Hardware Management Console to System
        | |Unit
9169    |A| Order Routing Indicator- System Plant
9300    |A| Language Group Specify - US English
9440    |A| New AIX License Core Counter
9442    |A| New Red Hat License Core Counter
9443    |A| New SUSE License Core Counter
9444    |A| Other AIX License Core Counter
9445    |A| Other Linux License Core Counter
9446    |A| 3rd Party Linux License Core Counter
9447    |A| VIOS Core Counter
9449    |A| Other License Core Counter
9450    |S| Ubuntu Linux License Core Counter
9461    |A| Month Indicator
9462    |A| Day Indicator
9463    |A| Hour Indicator
9464    |A| Minute Indicator
9465    |A| Qty Indicator
9466    |A| Countable Member Indicator
9700    |A| Language Group Specify - Dutch
9703    |A| Language Group Specify - French
9704    |A| Language Group Specify - German
9705    |A| Language Group Specify - Polish
9706    |A| Language Group Specify - Norwegian
9707    |A| Language Group Specify - Portuguese
9708    |A| Language Group Specify - Spanish
9711    |A| Language Group Specify - Italian
9712    |A| Language Group Specify - Canadian French
9714    |A| Language Group Specify - Japanese
9715    |A| Language Group Specify - Traditional Chinese (Taiwan)
9716    |A| Language Group Specify - Korean
9718    |A| Language Group Specify - Turkish
9719    |A| Language Group Specify - Hungarian
9720    |A| Language Group Specify - Slovakian
9721    |A| Language Group Specify - Russian
9722    |A| Language Group Specify - Simplified Chinese (PRC)
9724    |A| Language Group Specify - Czech
9725    |A| Language Group Specify - Romanian
9726    |A| Language Group Specify - Croatian
9727    |A| Language Group Specify - Slovenian
9728    |A| Language Group Specify - Brazilian Portuguese
9729    |A| Language Group Specify - Thai
ALH0    |A| Expert Care Indicator
B0PR    |A| SP Hard Drive/Media Retention - Power 5 years
B0VH    |A| SP HDR/MR POWER 3Y
B0VP    |A| SP Machine Setup Support for Power
EB2J    |A| 10m (30.3-ft) - IBM MTP 12 strand cable for 40/100G
        | |transceivers
EB2K    |A| 30m (90.3-ft) - IBM MTP 12 strand cable for 40/100G
        | |transceivers
EB2Z    |A| Lift Tool
EB39    |A| Power Supply - 2300W for Server (200-240 VAC)
EB3Z    |A| Lift tool based on GenieLift GL-8 (standard)
EB46    |A| 10GbE Optical Transceiver SFP+ SR
EB47    |A| 25GbE Optical Transceiver SFP28
EB48    |A| 1GbE Base-T Transceiver RJ45
EB49    |A| QSFP28 to SFP28 Connector
EB4J    |A| 0.5m SFP28/25GbE copper Cable
EB4K    |A| 1.0m SFP28/25GbE copper Cable
EB4M    |A| 2.0m SFP28/25GbE copper Cable
EB4P    |A| 2.0m QSFP28/100GbE copper split Cable to SFP28 4x25GbE
EB4Z    |A| Service wedge shelf tool kit for EB3Z
EB57    |A| QSFP+ 40GbE Base-SR4 Transceiver
EB59    |A| 100GbE Optical Transceiver QSFP28
EB5K    |A| 1.0M 100GbE Copper Cable QSFP28
EB5L    |A| 1.5M 100GbE Copper Cable QSFP28
EB5M    |A| 2.0M 100GbE Copper Cable QSFP28
EB5R    |A| 3M 100GbE Optical Cable QSFP28 (AOC)
EB5S    |A| 5M 100GbE Optical Cable QSFP28 (AOC)
EB5T    |A| 10M 100GbE Optical Cable QSFP28 (AOC)
EB5U    |A| 15M 100GbE Optical Cable QSFP28 (AOC)
EB5V    |A| 20M 100GbE Optical Cable QSFP28 (AOC)
EB5W    |A| 30M 100GbE Optical Cable QSFP28 (AOC)
EB5X    |A| 50M 100GbE Optical Cable QSFP28 (AOC)
EC2S    |S| PCIe3 2-Port 10Gb NIC&ROCE SR/Cu Adapter
EC2T    |S| PCIe3 LP 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter
EC2U    |A| PCIe3 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter
EC5B    |S| PCIe3 x8 1.6 TB NVMe Flash Adapter for AIX/Linux
EC5D    |S| PCIe3 x8 3.2 TB NVMe Flash Adapter for AIX/Linux
EC5F    |S| PCIe3 x8 6.4 TB NVMe Flash Adapter for AIX/Linux
EC5J    |S| Mainstream 800 GB SSD NVMe U.2 module
EC5K    |S| Mainstream 1.6 TB SSD NVMe U.2 module
EC5L    |S| Mainstream 3.2 TB SSD NVMe U.2 module
EC5V    |A| Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
EC5X    |A| Mainstream 800 GB SSD PCIe3 NVMe U.2 module for AIX/Linux
EC66    |A| PCIe4 2-port 100Gb ROCE EN adapter
EC6K    |A| PCIe2 2-Port USB 3.0 Adapter
EC76    |A| PCIe4 2-port 100Gb No Crypto Connectx-6 DX QFSP56
EC7B    |A| PCIe4 1.6TB NVMe Flash Adapter x8 for AIX/Linux
EC7D    |A| PCIe4 3.2TB NVMe Flash Adapter x8 for AIX/Linux
EC7F    |A| PCIe4 6.4TB NVMe Flash Adapter x8 for AIX/Linux
EC7Q    |A| 800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux
EC7T    |A| 800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux
EC7X    |A| Carrier Conversion Kit for 7mm to 15mm NVMe Devices
ECB2    |A| 1.5m (4.9-ft), Blue CAT5 Ethernet Cable
ECBJ    |A| SAS X Cable 3m - HD Narrow 6Gb 2-Adapters to Enclosure
ECBK    |A| SAS X Cable 6m - HD Narrow 6Gb 2-Adapters to Enclosure
ECBM    |S| SAS X Cable 15m - HD Narrow 3Gb 2-Adapters to Enclosure
ECBT    |A| SAS YO Cable 1.5m - HD Narrow 6Gb Adapter to Enclosure
ECBU    |A| SAS YO Cable 3m - HD Narrow 6Gb Adapter to Enclosure
ECBV    |A| SAS YO Cable 6m - HD Narrow 6Gb Adapter to Enclosure
ECBW    |A| SAS YO Cable 10m - HD Narrow 6Gb Adapter to Enclosure
ECBY    |A| SAS AE1 Cable 4m - HD Narrow 6Gb Adapter to Enclosure
ECBZ    |A| SAS YE1 Cable 3m - HD Narrow 6Gb Adapter to Enclosure
ECCF    |A| System Port Converter Cable for UPS
ECCS    |A| 3M Copper CXP Cable Pair for PCIe3 Expansion Drawer
ECCX    |A| 3M Active Optical Cable Pair for PCIe3 Expansion Drawer
ECCY    |A| 10M Active Optical Cable Pair for PCIe3 Expansion Drawer
ECDJ    |A| 3.0M SAS X12 Cable (Two Adapter to Enclosure)
ECDK    |A| 4.5M SAS X12 Active Optical Cable (Two Adapter to
        | |Enclosure)
ECDL    |A| 10M SAS X12 Active Optical Cable (Two Adapter to Enclosure)
ECDT    |A| 1.5M SAS YO12 Cable (Adapter to Enclosure)
ECDU    |A| 3.0M SAS YO12 Cable (Adapter to Enclosure)
ECDV    |A| 4.5M SAS YO12 Active Optical Cable (Adapter to Enclosure)
ECDW    |A| 10M SAS YO12 Active Optical Cable (Adapter to Enclosure)
ECE0    |A| 0.6M SAS AA12 Cable (Adapter to Adapter)
ECE3    |A| 3.0M SAS AA12 Cable
ECE4    |A| 4.5M SAS AA12 Active Optical Cable (Adapter to Adapter)
ECJ5    |A| 4.3m (14-Ft) PDU to Wall 3PH/24A 200-240V Delta-wired
        | |Power Cord
ECJ6    |A| 4.3m (14-Ft) PDU to Wall 3PH/40A 200-240V Power Cord
ECJ7    |A| 4.3m (14-Ft) PDU to Wall 3PH/48A 200-240V Delta-wired
        | |Power Cord
ECJJ    |A| High Function 9xC19 Single-Phase or Three-Phase Wye PDU
        | |plus
ECJL    |A| High Function 9xC19 PDU plus 3-Phase Delta
ECJN    |A| High Function 12xC13 Single-Phase or Three-Phase Wye PDU
        | |plus
ECJQ    |A| High Function 12xC13 PDU plus 3-Phase Delta
ECSM    |A| Custom Service Specify, Mexico
ECSP    |A| Custom Service Specify, Poughkeepsie, USA
ECW0    |A| Optical Wrap Plug
EHB1    |A| 1x HW Subscription Increment
EHB2    |A| 10x HW Subscription Increment
EHB3    |A| 100x HW Subscription Increment
EHC8    |A| Solution Edition for Healthcare typical 2.95 to 3.9,
        | |24-core processor module
EHCA    |A| Processor Activation for Healthcare Solution (#EHC8)
EHCB    |A| 512GB Base Memory activation for MRX #EHC8
EHKV    |A| SAP HANA TRACKING FEATURE
EHR2    |A| Boot Drive / Load Source in EXP24SX Specify (in #ESLS or
        | |#ELLS)
EHS2    |A| SSD Placement Indicator - #ESLS/#ELLS
EJ0J    |A| PCIe3 RAID SAS Adapter Quad-port 6Gb x8
EJ0L    |S| PCIe3 12GB Cache RAID SAS Adapter Quad-port 6Gb x8
EJ0Q    |A| Storage Backplane with Zero DASD 8 SAS 2.5" HDD/SDD
        | | Controllers
EJ10    |A| PCIe3 SAS Tape/DVD Adapter Quad-port 6Gb x8
EJ14    |A| PCIe3 12GB Cache RAID PLUS SAS Adapter Quad-port 6Gb x8
EJ2A    |A| PCIe3 x16 to CXP Converter Adapter (support AOC)
EJ32    |S| PCIe3 Crypto Coprocessor no BSC 4767
EJ33    |S| PCIe3 Crypto Coprocessor BSC-Gen3 4767
EJ35    |A| PCIe3 Crypto Coprocessor no BSC 4769
EJ37    |A| PCIe3 Crypto Coprocessor BSC-Gen3 4769
EJRL    |A| Non-paired Indicator EJ14 PCIe SAS RAID+ Adapter
EJRU    |S| Non-paired Indicator EJ0L PCIe SAS RAID Adapter
EJW1    |A| Specify Mode-1 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for
        | |EXP24SX #ESLS/ELLS
EJW2    |A| Specify Mode-1 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for
        | |EXP24SX #ESLS/ELLS
EJW3    |A| Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for
        | |EXP24SX #ESLS/ELLS
EJW4    |A| Specify Mode-2 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for
        | |EXP24SX #ESLS/ELLS
EJW5    |A| Specify Mode-4 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for
        | |EXP24SX #ESLS/ELLS
EJW6    |A| Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for
        | |EXP24SX #ESLS/ELLS
EJW7    |A| Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for
        | |EXP24SX #ESLS/ELLS
EJWA    |A| Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for
        | |EXP24SX #ESLS/ELLS
EJWB    |A| Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for
        | |EXP24SX #ESLS/ELLS
EJWC    |A| Specify Mode-4 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for
        | |EXP24SX #ESLS/ELLS
EJWD    |A| Specify Mode-4 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for
        | |EXP24SX #ESLS/ELLS
EJWE    |A| Specify Mode-4 & (3)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for
        | |EXP24SX #ESLS/ELLS
EJWF    |A| Specify Mode-1 & (2)EJ14 & (2)YO12 for EXP24SX #ESLS/ELLS
EJWG    |A| Specify Mode-2 & (2)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS
EJWH    |A| Specify Mode-2 & (2)EJ14 & (1)X12 for EXP24SX #ESLS/ELLS
EJWJ    |A| Specify Mode-2 & (4)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS
EKF3    |A| Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
EKF5    |A| Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
EKF7    |A| Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ELBV    |A| PowerVM for Linux indicator
ELBW    |A| 1-core Linux Processor Activation for #EPEU
ELBX    |A| 1-core Linux Processor Activation for #EPEV
ELBY    |A| 1-core Linux Processor Activation for #EPGW
ELC0    |A| PDU Access Cord 0.38m
ELC1    |A| 4.3m (14-Ft) PDU to Wall 24A 200-240V Power Cord North
        | |America
ELC2    |A| 4.3m (14-Ft) PDU to Wall 3PH/24A 415V Power Cord North
        | |America
ELC5    |A| Power Cable - Drawer to IBM PDU (250V/10A)
ELG4    |A| IBM Power Private Cloud Rack for OracleDB Solution
        | |Indicator
EM75    |A| 64GB (2 x 32GB) DDR4 Memory Dimm
EM76    |A| 128GB (2 x 64GB) DDR4 Memory Dimm
EM77    |A| 256GB (2 x 128GB) DDR4 Memory Dimm
EM7J    |A| 512GB (2 x 256GB) DDR4 Memory Dimm
EM81    |A| Active Memory Mirroring
EMBM    |A| Power Active Memory Expansion
EMCE    |A| 512 of #EMCP 1GB Memory Activations for MRX
EMCG    |A| 512 of #EMCP 1GB Linux Memory Activations for MRX
EMCP    |A| 1GB Memory Activations for MRX
EMCQ    |A| 100GB Memory Activations for MRX
EMX0    |A| PCIe Gen3 I/O Expansion Drawer
EMXA    |A| AC Power Supply Conduit for PCIe3 Expansion Drawer
EMXH    |A| PCIe3 6-Slot Fanout Module for PCIe3 Expansion Drawer
EN01    |A| 1m (3.3-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
EN02    |A| 3m (9.8-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
EN03    |A| 5m (16.4-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper
EN0A    |S| PCIe3 16Gb 2-port Fibre Channel Adapter
EN0S    |S| PCIe2 4-Port (10Gb+1GbE) SR+RJ45 Adapter
EN0U    |S| PCIe2 4-port (10Gb+1GbE) Copper SFP+RJ45 Adapter
EN0W    |A| PCIe2 2-port 10/1GbE BaseT RJ45 Adapter
EN1A    |A| PCIe3 32Gb 2-port Fibre Channel Adapter
EN1C    |A| PCIe3 16Gb 4-port Fibre Channel Adapter
EN1E    |A| PCIe3 16Gb 4-port Fibre Channel Adapter
EN1G    |A| PCIe3 2-Port 16Gb Fibre Channel Adapter
EN1J    |A| PCIe4 32Gb 2-port Optical Fibre Channel Adapter
EN1L    |A| PCIe4 32Gb 4-port Optical Fibre Channel Adapter
EN1N    |A| PCIe4 64Gb 2-port Optical Fibre Channel Adapter
EN2A    |A| PCIe3 16Gb 2-port Fibre Channel Adapter
EN2W    |A| PCIe3 4-port 10GbE BaseT RJ45 Adapter
ENSH    |A| IBM eBMC Indicator node 9043-MRX for China
EP20    |A| Power Enterprise Pools 2.0 Enablement
EP2X    |A| Lab Services Private Cloud Capacity Assessment
EPA0    |A| Deactivation of LPM (Live Partition Mobility)
EPEU    |A| 12-core Typical 3.35 to 4.0 GHZ (max) processor
EPEV    |A| 18-core Typical 3.20 to 4.0 GHZ (max) processor
EPGW    |A| 24-core Typical 2.95 to 3.90 GHZ (max) processor
EPLU    |A| Front Heatsink + TIM PAD (For MRX)
EPLV    |A| Rear Heatsink + TIM PAD (For MRX)
EPRS    |A| 1 core Base Processor Activation (Pools 2.0) for EPEU
EPRT    |A| 1 core Base Processor Activation (Pools 2.0) for EPEV
EPRV    |A| 1 core Base Processor Activation (Pools 2.0) for EPGW
EPRW    |A| 1 core Base Linux Processor Activation (Pools 2.0) for EPEU
EPRX    |A| 1 core Base Linux Processor Activation (Pools 2.0) for EPEV
EPRZ    |A| 1 core Base Linux Processor Activation (Pools 2.0) for EPGW
EPSA    |A| 1 core Base Processor Activation (Pools 2.0) for #EPEU
        | |(From Static)
EPSB    |A| 1 core Base Processor Activation (Pools 2.0) for #EPEV
        | |(From Static)
EPSD    |A| 1 core Base Processor Activation (Pools 2.0) for #EPGW
        | |(From Static)
EPSE    |A| 1 core Base Processor Activation (Pools 2.0) for #EPEU
        | |(From Static) Linux only
EPSF    |A| 1 core Base Processor Activation (Pools 2.0) for #EPEV
        | |(From Static) Linux only
EPSH    |A| 1 core Base Processor Activation (Pools 2.0) for #EPGW
        | |(From Static) Linux only
EPSJ    |A| 1GB Base Memory activation (Pools 2.0)
EPSP    |A| 100GB Base Memory activation (Pools 2.0)
EPSQ    |A| 512GB Base Memory Activation for Pools 2.0 (From Static)
EPSR    |A| 1GB Base Memory Activation for Pools 2.0 (From Static)
EPSS    |A| 100GB Base Memory Activation for Pools 2.0 (From Static)
EPST    |A| 512GB Base Memory Activation for Pools 2.0 (From Linux)
EPSU    |A| 256GB Base Memory Activation for Pools 2.0 - Linux only
EPSW    |A| 256GB Base Memory Activation for Pools 2.0
EPTH    |A| Horizontal PDU Mounting Hardware
EPTJ    |S| High Function 9xC19 PDU: Switched, Monitoring
EPTL    |S| High Function 9xC19 PDU 3-Phase: Switched, Monitoring
EPTN    |S| High Function 12xC13 PDU: Switched, Monitoring
EPTQ    |S| High Function 12xC13 PDU 3-Phase: Switched, Monitoring
EPUR    |A| 1 core Processor Activation for #EPEU
EPUS    |A| 1 core Processor Activation for #EPEV
EPVV    |A| PowerVM - Enterprise Edition
EPYT    |A| 1 core Processor Activation for #EPGW
ERQ0    |A| 1 core Base Processor Activation (Pools 2.0) for EPEU
        | |(from Prev)
ERQ1    |A| 1 core Base Processor Activation (Pools 2.0) for EPEV
        | |(from Prev)
ERQ2    |A| 1 core Base Processor Activation (Pools 2.0) for EPGW
        | |(from Prev)
ERQ4    |A| 1 core Base Linux only Processor Activation (Pools 2.0)
        | |for EPEU (from Prev)
ERQ5    |A| 1 core Base Linux only Processor Activation (Pools 2.0)
        | |for EPEV (from Prev)
ERQ6    |A| 1 core Base Linux only Processor Activation (Pools 2.0)
        | |for EPGW (from Prev)
ERQM    |A| 256GB Base Memory Activation (Pools 2.0) (from Prev)
ERQN    |A| 256GB Base Linux only Memory Activation (Pools 2.0) (from
        | |Prev)
ERQP    |A| 1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW
        | |- any O/S
ERQQ    |A| 1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW
        | |- any O/S (Conv from HSE)
ERQR    |A| 512GB Base Memory Activation for Pools2.0
ERQS    |A| 512GB Base Memory Activation for Pools2.0 Healthcare
ERQT    |A| 512GB Base Memory Activation for Pools2.0 (convert
        | |Healthcare)
ES1E    |A| Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES1G    |A| Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES3B    |A| Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES3D    |A| Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES3F    |A| Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES3H    |A| Enterprise 800GB SSD PCIe4 NVMe U.2 module for AIX/Linux
ES94    |S| 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESB2    |S| 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESB6    |S| 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESBA    |S| 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESBG    |S| 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESBL    |S| 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESC0    |A| S&H - No Charge
ESC7    |A| S&H
ESCT    |A| Virtual Capacity Expedited Shipment
ESCZ    |A| iSCSI SAN Load Source Specify for AIX
ESEV    |A| 600GB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
ESF3    |A| 1.2TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
ESFT    |A| 1.8TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux
ESGV    |S| 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESGZ    |S| 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESJ0    |S| 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJ2    |S| 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJ4    |S| 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJ6    |S| 7.45TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJJ    |S| 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJL    |S| 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJN    |S| 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESJQ    |S| 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESK1    |A| 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESK3    |A| 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ESK8    |A| 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESKC    |A| 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESKG    |A| 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESKK    |A| 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESKP    |A| 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESKT    |A| 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESKX    |A| 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESLA    |A| Specify AC Power Supply for EXP24SX Storage
        | |Enclosure
ESLS    |A| EXP24SX SAS Storage Enclosure
ESMB    |A| 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESMF    |A| 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESMK    |A| 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESMV    |A| 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux
ESNA    |S| 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESNE    |S| 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ESNM    |A| 300GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/
        | |Linux)
ESNR    |A| 600GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/
        | |Linux)
ESWK    |A| AIX Update Access Key (UAK)
ETK1    |A| 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ETK3    |A| 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux
ETK8    |A| 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ETKC    |A| 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
ETKG    |A| 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux
EU29    |A| Order Placed Indicator
EUA5    |A| Standalone USB DVD drive w/cable
EXA3    |A| 3 YEAR, ADVANCED EXPERT CARE
EXA4    |A| 4 YEAR, ADVANCED EXPERT CARE
EXA5    |A| 5 YEAR, ADVANCED EXPERT CARE
EXP3    |A| 3 YEAR, PREMIUM EXPERT CARE
EXP4    |A| 4 YEAR, PREMIUM EXPERT CARE
EXP5    |A| 5 YEAR, PREMIUM EXPERT CARE
SVBP    |A| BP Post-Sale Services: 1 Day
SVCS    |A| IBM Systems Lab Services Post-Sale Services: 1 Day
SVNN    |A| Other IBM Post-Sale Services: 1 Day
SVPC    |A| 5000 Power to Cloud Reward points

Feature descriptions


Note: Not all of the following features are available in all countries. Check with your country representative for specific feature availability.

The following is a list of all feature codes in numeric order for the IBM Power Systems 9043 machine type.

Attributes, as defined in the following feature descriptions, state the interaction of requirements among features.

Minimums and maximums are the absolute limits for a single feature without regard to interaction with other features. The maximum valid quantity for MES orders may be different than for initial orders. The maximums listed below refer to the largest quantity of these two possibilities.

The order type defines if a feature is orderable only on initial orders, only on MES orders, on both initial and MES orders, or if a feature is supported on a model due to a model conversion. Supported features cannot be ordered on the converted model, only left on or removed from the converted model.

(#0010) - One CSC Billing Unit

One Billing Unit used by the Customer Solution Center.

  • Attributes provided: One CSC Billing Unit
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#0011) - Ten CSC Billing Units

Ten Billing Units used by the Customer Solutions Center.

  • Attributes provided: Ten CSC Billing Units
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#0265) - AIX Partition Specify

This feature indicates customers intend to create a partition on the system that will use the AIX operating system. This feature should be included once for each intended AIX partition. This feature is an indicator and does not deliver parts, software, or services.

  • Attributes provided: None
  • Attributes required: Customers intend to create a partition on the system that will run the AIX operating system.
  • Minimum required: 0
  • Maximum allowed: 960 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#0266) - Linux Partition Specify

This feature indicates customers intend to create a partition on the system that will use the Linux operating system. This feature should be included once for each intended Linux partition. This feature is an indicator and does not deliver parts, software, or services.

  • Attributes provided: None
  • Attributes required: Customers intend to create a partition on the system that will run the Linux operating system.
  • Minimum required: 0
  • Maximum allowed: 960 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#0373) - UPS Factory Integration Specify

Used in manufacturing to ensure that a UPS ordered from IBM under a separate machine type/model, is associated with the system order, and is shipped concurrently.

  • Attributes provided: N/A
  • Attributes required: Ordered machine type-model UPS.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0374) - HMC Factory Integration Specify

Used in manufacturing to ensure that an HMC ordered from IBM under a separate machine type/model is associated with the system order and is shipped concurrently.

  • Attributes provided: N/A
  • Attributes required: Ordered machine type-model HMC.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0375) - Display Factory Integration Specify

Used in manufacturing to ensure that a display ordered from IBM under a separate machine type/model, is associated with the system order, and is shipped concurrently.

  • Attributes provided: N/A
  • Attributes required: Ordered machine type-model display.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0376) - Reserve Rack Space for UPS

Used in manufacturing to reserve 1 EIA of rack space in the bottom of the rack for later client installation of a UPS.

  • Attributes provided: 1 EIA rack space reserved.
  • Attributes required: Ordered rack feature.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0377) - Reserve Rack Space for HMC

Used in manufacturing to reserve 1 EIA of rack space in the middle of the rack for later client installation of a rack-mounted HMC.

  • Attributes provided: 1 EIA rack space reserved.
  • Attributes required: Ordered rack feature.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0378) - Reserve Rack Space for Display

Used in manufacturing to reserve 1 EIA of rack space in the middle of the rack for later client installation of an HMC rack-mounted display such as the 7316.

  • Attributes provided: 1 EIA rack space reserved.
  • Attributes required: Ordered rack feature.
  • Minimum required: 0
  • Maximum allowed: 42 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: Available only when ordered with 19 inch feature code rack on an MES order. Max. is 36 with rack feature 0551.
(#0456) - Customer Specified Placement
  1. Requests that IBM deliver the system to the customer according to the slot in drawer hardware placement defined by the account team.
  2. Eliminates the need to have these parts relocated in the customers environment as may happen if the order is placed without this feature code.
  3. Client placement specifications are collected using the System Planning Tool (SPT) and processed through the marketing configurator. (Use of the SPT is not required).
  4. Requires account team to submit the output of the marketing configurator into IBM manufacturing via the CSP Web site http://www.ibm.com/eserver/power/csp (US Business Partners and Distributors can bypass this step.)
  5. Requires account team to assure that the marketing configurator output submitted reflects the actual order placed.
  • Attributes provided: I/O component placement
  • Attributes required: Marketing Configurator output submitted to the CSP Web site. (US Business Partners and Distributors can bypass this step.)
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:
    • Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#0719) - Load Source Not in CEC

This specify feature indicates to the IBM Marketing configurator tools and IBM manufacturing that disk drives will not be placed in the system unit, but will be placed in I/O drawers or in external SAN attached disk.

  • Attributes provided: System unit(s) are shipped with no disk units placed inside.
  • Attributes required: Alternate load source specified
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#0837) - Fiber Channel SAN Load Source Specify

Indicates that a SAN drive is being used as the Load Source for the operating system.

  • Attributes provided: SAN load source placement specify
  • Attributes required: Fiber Channel adapter
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#0983) - US TAA Compliance Indicator

This feature indicates that the product was assembled in a manufacturing plant in the USA or in a country approved under the US Trade Agreement Act. Only valid on U.S. orders.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: N/A
  • Return parts MES: No
(#0984) - Product assembled in USA manufacturing plant

This feature indicates that the product was assembled in a manufacturing plant in the USA.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#1140) - Custom Service Specify, Rochester Minn, USA

Having #1140 on the order, will cause the order to be routed to Rochester and the machine to be internally routed to the CSC build area in building 114 (Rochester).

  • Attributes provided: Customization
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#1953) - 300GB 15k RPM SAS SFF-2 Disk Drive (AIX/Linux)

300 GB SFF 15k RPM SAS disk drive mounted in a Gen-2 carrier and supported in SFF SAS bay such as used in the #5887 EXP24S I/O drawer or #ESLS EXP24SX I/O drawer. Disk can be formatted for either 512 bytes or 528 byte sectors and is thus called having 5xx drive sectors. 528 byte sectors provide additional protection. IBM Manufacturing will ship pre-formatted with 528 or with 512 byte sectors. Selection of the formatting is selected by IBM Manufacturing based on manufacturing rules, but the client may change at their location. In the EPX24SX IBM Manufacturing will ship using 528 byte sectors. Capacity is 300GB with 512 byte formatting and is 283GB with 528 byte sector. CCIN is 19B1.

Limitations: physical difference in carriers prevent this drive from being used in SFF-1 bays such as used in the #5802/5803 I/O drawer or in SFF-3 bays such as used in Power9/Power10 system units.

  • Attributes provided: 300GB/283GB of SFF (2.5-inch) SAS disk storage mounted in Gen-2 carrier.
  • Attributes required: one SFF-2 drive bay.
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#1964) - 600GB 10k RPM SAS SFF-2 HDD for AIX/Linux

600 GB SFF 10k RPM SAS disk drive mounted in a Gen-2 carrier and supported in SFF SAS bay such as used in the #5887 EXP24S I/O drawer or #ESLS EXP24SX I/O drawer. Disk can be formatted for either 512 bytes or 528 byte sectors and is thus called having 5xx drive sectors. 528 byte sectors provide additional protection. IBM Manufacturing will ship pre-formatted with 528 or with 512 byte sectors. Selection of the formatting is selected by IBM Manufacturing based on manufacturing rules, but the client may change at their location. In the EPX24SX IBM Manufacturing will ship using 528 byte sectors. Capacity is 600GB with 512 byte formatting and is 571GB with 528 byte sector.

Features #1962 and #1964 are physically identical drives with the same 19B3 CCIN. Different feature codes help the IBM configuration tools understand how the HDD is used. #1964 indicates usage by AIX, Linux or VIOS. #1962 indicates usage by IBM i.

Limitation: physical difference in carriers prevent this drive from being used in SFF-1 bays such as used in the #5802/5803 I/O drawer or in SFF-3 bays such as used in Power9/Power10 system units.

  • Attributes provided: 600GB/571GB of SFF (2.5-inch) SAS disk storage mounted in Gen-2 carrier.
  • Attributes required: one SFF-2 drive bay.
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#2146) - Primary OS - AIX

Indicates clients intend to use the AIX operating system on the primary system partition. This feature is used as a Manufacturing Routing indicator and does not deliver parts, software or services.

  • Attributes provided: None
  • Attributes required: Indicates clients intend to use the AIX operating system on the primary system partition.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 1)
  • OS level required:
    • AIX - supported

    Refer to the Software Requirements section to find the supported O/S levels for AIX.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Only one of features 2146 or 2147 may exist on a system Configuration report.
(#2147) - Primary OS - Linux

Indicates clients intend to use the Linux operating system on the primary system partition. This feature is used as a Manufacturing Routing indicator and does not deliver parts, software or services.

  • Attributes provided: None
  • Attributes required: Indicates clients intend to use the Linux operating system on the primary system partition.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 1)
  • OS level required:
    • Linux - supported

    Refer to the Software Requirements section to find the supported O/S levels for Linux.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Only one of features 2146 or 2147 may exist on a system Configuration report.
(#4558) - Power Cord To PDU/UPS, (100-240V/16A)

Standard IBM power jumper cord that goes from the system or chassis to the rack power distribution unit (PDU) Cable has C19 on one end (for C20 power supply connector on system or chassis) and C20 on the other end (for IBM PDU or a UPS with C19 receptacle).

If ordered with a server with factory integration specify, then IBM Manufacturing will select from the optimum cable length (1m, 1.5m, 2.5m, or 4.3m). If ordered without factory integration, then the 2.5m (8 foot) is shipped.

  • Attributes provided: Power jumper cord (1m, 1.5m, 2.5m, or 4.3m)
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#4649) - Rack Integration Services

#4649 is a prerequisite for #4651-4666.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4650) - Rack Indicator- Not Factory Integrated

This indicator is used to specify that the rack mountable device in this initial order should not be merged into a rack within IBM Manufacturing. If a device with 4650 is ordered with a rack, the device will not be factory integrated in the ordered rack and will ship uninstalled in the rack.
Note: This "no additional charge" feature will be placed on an initial order for a rack mountable device by the Configuration Tool when the order does not ship from IBM Manufacturing in a Rack. This server is not designed to be rack shippable.

  • Attributes provided: System will not be shipped in a rack.
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4651) - Rack Indicator, Rack #1

When added to an initial rack order, this indicator is used to specify the first rack for a multi rack order, or the only rack for a single rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #1.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack Integration/ Rack Specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4652) - Rack Indicator, Rack #2

When added to an initial rack order, this indicator is used to specify the second rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #2 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack Integration/Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4653) - Rack Indicator, Rack #3

When added to an initial rack order, this indicator is used to specify the third rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #3 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4654) - Rack Indicator, Rack #4

When added to an initial rack order, this indicator is used to specify the fourth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #4 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4655) - Rack Indicator, Rack #5

When added to an initial rack order, this indicator is used to specify the fifth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #5 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4656) - Rack Indicator, Rack #6

When added to an initial rack order, this indicator is used to specify the sixth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #6 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4657) - Rack Indicator, Rack #7

When added to an initial rack order, this indicator is used to specify the seventh rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #7 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4658) - Rack Indicator, Rack #8

When added to an initial rack order, this indicator is used to specify the eighth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #8 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4659) - Rack Indicator, Rack #9

When added to an initial rack order, this indicator is used to specify the ninth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #9 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4660) - Rack Indicator, Rack #10

When added to an initial rack order, this indicator is used to specify the tenth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #10 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4661) - Rack Indicator, Rack #11

When added to an initial rack order, this indicator is used to specify the eleventh rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #11 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4662) - Rack Indicator, Rack #12

When added to an initial rack order, this indicator is used to specify the twelfth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #12 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4663) - Rack Indicator, Rack #13

When added to an initial rack order, this indicator is used to specify the thirteenth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #13 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4664) - Rack Indicator, Rack #14

When added to an initial rack order, this indicator is used to specify the fourteenth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #14 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4665) - Rack Indicator, Rack #15

When added to an initial rack order, this indicator is used to specify the fifteenth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #15 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#4666) - Rack Indicator, Rack #16

When added to an initial rack order, this indicator is used to specify the sixteenth rack for a multi rack order.

When added to an initial rack mountable device order, this indicator is used to specify that the rack mountable device (such as a system or I/O drawer) is to be mounted in rack #16 of a multi rack order.
Note: For 19" rack mountable device orders: One feature code from the group 4650 to 4666 must be listed on the order. More than one feature code from this group is not allowed.

For 19" rack orders: If IBM Mfg. is to assemble a rack mountable device into the rack, one feature code selection from the group 4651 to 4666 must be listed on the order. More than one feature code selection from this group is not allowed. The quantity of this selected feature code on the 19" rack order must equal the number of rack mountable devices to be installed in the rack by IBM Mfg.

  • Attributes provided: Rack specify
  • Attributes required: Rack
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#5000) - Software Preload Required

Indicates that preloaded software and/or consolidated I/O is shipped with the initial order. A maximum of one (#5000) is supported. This feature has country-specific usage.
Note: Not supported in Brazil and India.

  • Attributes provided: Software Pre-load
  • Attributes required: N/A
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#5899) - PCIe2 4-port 1GbE Adapter

(No Longer Available as of September 13, 2022)

This short PCIe Gen2 adapter provides four 1Gb Ethernet ports that can be configured to run at 1000, 100 or 10 Mbps. 4-pair CAT-5 Unshielded Twisted Pair (UTP) cables up to 100 meters in length are attached to the copper RJ45 connectors. Each port is independent of one another and supports full-duplex or half-duplex. 1000 Mbps speed is not supported in Half Duplex (HDX) mode.

Feature #5260 and #5899 are electronically identical and have the same CCIN of 576F. #5260 indicates a low profile tail stock while #5899 indicates a full high tail stock.

Details for the ports include: for 5260 & 5899

  • AIX NIM support
  • IEEE 802.3ab (1 GbE), 802.1p priority, 802.1Q VLAN tagging, 802.3x flow control, 802.3ad load-balancing and failover,
  • Link aggregation, IEEE 802.3ad 802.3
  • Multiple MAC addresses per interface
  • MSI-X, MSI and support of legacy pin interrupts
  • Ether II and IEEE 802.3 encapsulated frames
  • Jumbo frames up to 9.6 Kbytes
  • TCP checksum offload for IPv4 and IPv6
  • TCP segmentation Offload (TSO) for IPv4 and IPv6
  • UDP checksum offload for IPv4 and IPv6
  • AIX, IBM i and Linux provide software iSCSI support through the adapter. Linux can also leverage adapter hardware support including initiator and header & data digest (CRC) generation and checking
  • Attributes provided: Four-port 1 Gb Ethernet
  • Attributes required: 1 Full High Profile PCIe slot (Gen1 or Gen2)
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#6458) - Power Cord 4.3m (14-ft), Drawer to IBM PDU (250V/10A)

Standard IBM rack power cable that goes from the system or I/O drawer to the rack power distribution unit (PDU). Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C14 on the other end (for IBM PDU C13 receptacle). Note for different length C13/C14 cables see #6671 (2.7M) or #6672 (2.0M).

  • Attributes provided: Power jumper cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6460) - Power Cord 4.3m (14-ft), Drawer To OEM PDU (125V, 15A)

This power cord goes from the system or I/O drawer to the rack OEM power distribution unit or wall socket outlet. Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and plug type #4 (NEMA 5-15) on the other end.

The following countries/regions use the #6460 power cord to power the system and/or peripheral features requiring a power cord: United States, Antigua & Barbuda, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Bonaire, Calicos Islands, Canada, Cayman Islands, Colombia, Costa Rica, Cuba, Curacao, Dominican Republic, Ecuador, El Salvador, Guam, Guatemala, Guyana, Haiti, Honduras, Jamaica, Japan, Mexico, Micronesia, Montserrat, Netherlands Antilles, Nicaragua, Panama, Peru, Philippines, St. Kitts/Nevis, St. Martin, Taiwan, Tortola (BVI), Trinidad/Tobago, Venezuela.

  • Attributes provided: Power cord.
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6469) - Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (250V/15A) U. S.

This power cord goes from the system or I/O drawer to the wall or rack OEM power distribution unit. Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and plug type #5 (NEMA 6-15) on the other end for wall or OEM PDU.

The following countries/regions use the #6469 power cord to power the system and/or peripheral features requiring a power cord:

United States, Anguilla, Antigua & Barbuda, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Bonaire, Caicos Is., Canada, Cayman Islands, Colombia, Costa Rica, Cuba, Curacao, Dominican Republic, Ecuador, El Salvador, Guam, Guatemala, Haiti, Honduras, Jamaica, Japan, Micronesia, Montserrat, Netherlands Antilles, Nicaragua, Panama, Peru, Philippines, St. Marten NA, Taiwan, Tortola (BVI), Thailand, Venezuela.

  • Attributes provided: Power cord.
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6470) - Power Cord 1.8m (6-ft), Drawer to Wall (125V/15A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #4 (NEMA 5-15). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. 6-foot length.

The following countries/regions use the #6470 power cord to power the system and/or peripheral features requiring a power cord:

United States, Antigua and Barbuda, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Bonaire, Calicos Islands, Canada, Cayman Islands, Colombia, Costa Rica, Cuba, Curacao, Dominican Republic, Ecuador, El Salvador, Guam, Guatemala, Guyana, Haiti, Honduras, Jamaica, Japan, Mexico, Micronesia, Montserrat, Netherlands Antilles, Nicaragua, Panama, Peru, Philippines, St. Kitts/Nevis, St. Martin, Taiwan, Tortola (BVI), Trinidad/Tobago, Venezuela.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#6471) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #73 (InMetro NBR 14136). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6471 power cord to power the system and/or peripheral features requiring a power cord:

Brazil

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6472) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/16A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #18 (CEE 7 VII). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6472 power cord to power the system and/or peripheral features requiring a power cord:

Afghanistan, Albania, Algeria, Andorra, Angola, Armenia, Austria, Belarus, Belgium, Benin, Bosnia/Herzegovina, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Cape Verde, Central African Republic, Chad, Comoros, Congo, Croatia, Czech Republic, Dahomey, Djibouti, Egypt, Equatorial Guinea, Eritrea, Estonia, Ethiopia, Finland, France, French Polynesia, French Guyana, Gabon, Georgia, Germany, Greece, Guadeloupe, Guinea, Guinea-Bissau, Hungary, Iceland, Indonesia, Iran, Ivory Coast, Kazakhstan, Kyrgyzstan, Laos, Latvia, Lebanon, Lithuania, Luxembourg, Macau, Macedonia, Mali, Martinique, Mauritania, Mauritius, Mayotte, Moldova, Monaco, Mongolia, Morocco, Mozambique, Netherlands, New Caledonia, Niger, North Korea (C19 only), Norway, Poland, Portugal, Principe, Reunion, Romania, Russia, Rwanda, St. Thomas, Saudi Arabia, Senegal, Serbia, Slovenia, Somalia, South Korea (C19 only), Spain, Surinam, Sweden, Syria, Tahiti, Tajikistan, Togo, Tunisia, Turkey, Turkmenistan, Ukraine, Upper Volta, Uzbekistan, Vanuatu, Vietnam, Wallis & Futuna, Zaire, Zimbabwe.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6473) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU (250V/10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #19 (CEE). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6473 power cord to power the system and/or peripheral features requiring a power cord:

Denmark

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6474) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/13A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #23 (BS 1364A). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6474 power cord to power the system and/or peripheral features requiring a power cord:

Abu Dhabi, Bahrain, Botswana, Brunei, Channel Islands, Cyprus, Dominica, Gambia, Grenada, Grenadines, Guyana, Hong Kong, Iraq, Ireland, Jordan, Kenya, Kuwait, Liberia, Malawi, Malaysia, Malta, Myanmar, Nigeria, Oman, Qatar, Sierra Leone, Singapore, St. Kitts, St. Lucia, Seychelles, Sudan, Tanzania, Trinidad & Tobago, United Arab Emirates, United Kingdom, Yemen, Zambia

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6475) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/16A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #32 (SII 32-1971). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6475 power cord to power the system and/or peripheral features requiring a power cord:

Israel

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6476) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #24 (SEV 24507). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6476 power cord to power the system and/or peripheral features requiring a power cord:

Lichtenstein, Switzerland

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6477) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/16A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #22 (SABS 164). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6477 power cord to power the system and/or peripheral features requiring a power cord:

Bangladesh, LeSotho, Maceo, Maldives, Nambia, Pakistan, Samoa, South Africa, Sri Lanka, Swaziland, Uganda.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6478) - Power Cord 2.7 M(9-foot), To Wall/OEM PDU, (250V, 16A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #25 (CEI 23-16). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. The following countries/regions use the #6478 power cord to power the system and/or peripheral features requiring a power cord: Chile Italy Libya

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6488) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (125V/15A or 250V/10A )

This power cord goes from the system and/or peripheral features to a wall-type outlet. 125V, 15A or 250V, 10A, Plug Type #2. Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6488 power cord to power the system and/or peripheral features requiring a power cord:

Argentina, Paraguay, Uruguay.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6489) - 4.3m (14-Ft) 3PH/32A 380-415V Power Cord

#6489 is a 14-FT/4.3m 3PH/32A power cable with a Type 46 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6491) - 4.3m (14-Ft) 1PH/63A 200-240V Power Cord

#6491 is a 14-FT/4.3m 200-240V/63A power cord with a Type 46 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6492) - 4.3m (14-Ft) 1PH/60A (48A derated) 200-240V Power Cord

Feature #6492 is a 14-FT/4.3m 200-240V/48-60A power cord with a Type 46 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: Power Cord PDU to wall
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6493) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #62 (GB 1053). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6493 power cord to power the system and/or peripheral features requiring a power cord:

People's Republic of China.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6494) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #69 (IS 6538). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6494 power cord to power the system and/or peripheral features requiring a power cord:

India

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6496) - Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 10A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #66 (KETI). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. The following countries/regions use the #6496 power cord to power the system and/or peripheral features requiring a power cord: North Korea South Korea

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6577) - Power Cable - Drawer to IBM PDU, 200-240V/10A

This feature permits manufacturing to select the optimum PDU power jumper cord length (1.0M, 2.0M, 2.7M, or 4.3M) for rack integration. This feature is mandatory on initial order specifying factory integration with IBM racks (such as with 7965-S42 racks). Feature is not valid on initial order with non-factory integrated feature 4650. Power jumper cord has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C14 on the other end (for C13 PDU receptacle).
Note: This feature is not used for MES orders except for bulk orders by SDI clients only. See C13/C14 jumper cord features #6458 (4.3M), #6671 (2.7M), #6672 (2.0M) when not using factory integration.

  • Attributes provided: One power jumper cord.
  • Attributes required: At least one rack and the absence of #4650.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: Yes
  • Return parts MES: No
    Note: 1 or 2 per I/O drawer or CEC. MES orderable for SDI's only. The MES order will ship the 14 foot cable equivalent to feature number 6458.
(#6651) - Power Cord 2.7M (9-foot), To Wall/OEM PDU, (125V, 15A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #75 (KETI). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. The following countries/regions use the #6651 power cord to power the system and/or peripheral features requiring a power cord: Taiwan

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6653) - 4.3m (14-Ft) 3PH/16A 380-415V Power Cord

#6653 is a 14-FT/4.3m 3PH/16A power cord with a Type 46 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6654) - 4.3m (14-Ft) 1PH/30A (24A derated) Power Cord

Feature #6654 is a 14-FT/4.3m 200-240V/24A-30A locking power cord with a Type 12 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6655) - 4.3m (14-Ft) 1PH/30A (24A derated) WR Power Cord

Feature #6655 is a 14-FT/4.3m 200-240V/24A-30A water-resistant power cord with a Type 40 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: Power Cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6656) - 4.3m (14-Ft) 1PH/32A Power Cord

#6656 is a 14-FT/4.3m 200-240V/32A power cord with a Type 46 plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: PDU power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6657) - 4.3m (14-Ft) 1PH/32A Power Cord-Australia

This power cord provides power to a #5889, #7188 #9188, #7109, #EPTG, #EPTM, #EPTJ, #ECJM, #ECJG, #ECJJ, #ECJN, or #EPTN power distribution unit. It connects to a wall power outlet with a PDL plug.

  • Attributes provided: Power connection for a PDU
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6658) - 4.3m (14-Ft) 1PH/30A (24A derated) Power Cord-Korea

This power cord provides power to a #5889, #7188, #9188, #7109, #EPTG, #EPTM, #EPTJ, #ECJM, #ECJG, #ECJJ, #ECJN, or #EPTN power distribution unit. It connects to a wall power outlet with a Korean plug.

  • Attributes provided: PDU power cable
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6659) - Power Cord 2.7M (9-foot), To Wall/OEM PDU, (250V, 15A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #76 (KETI). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. The following countries/regions use the #6659 power cord to power the system and/or peripheral features requiring a power cord: Taiwan

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6660) - Power Cord 4.3m (14-ft), Drawer to Wall/OEM PDU (125V/15A)

This power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #59 (NEMA 5-15). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. 14-foot length.

This power cord meets the DENAN marking requirement in Japan.

  • Attributes provided: Power Cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6665) - Power Cord 2.8m (9.2-ft), Drawer to IBM PDU, (250V/10A)

Standard IBM rack power jumper cord that goes from the system or I/O drawer to the rack power distribution unit (PDU). Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C20 on the other end (for IBM PDU C19 receptacle).
Note: For power jumper cord which attach to PDUs with C13 receptacles, use features such as #6577, #6458, #6671, or #6672.

  • Attributes provided: Power jumper cord.
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6667) - 4.3m (14-Ft) 3PH/32A 380-415V Power Cord-Australia

#6667 is a 14-FT/4.3m 380-45V/32A power cord with a Type PDL plug which distributes power from a power source to a Power Distribution Unit.

  • Attributes provided: PDU power cable
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6669) - Power Cord 4.3M (14-foot), Drawer to OEM PDU, (250V, 15A)

This power cord goes from the system or I/O drawer to the rack power distribution unit. Plug type #57 (NEMA 6-15). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types. 14-foot length. This power cord meets the DENAN marking requirement in Japan.

  • Attributes provided: Power Cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6671) - Power Cord 2.7M (9-foot), Drawer to IBM PDU, 250V/10A

Standard IBM rack power cable that goes from the system or I/O drawer to the rack power distribution unit (PDU). Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C14 on the other end (for IBM PDU C13 receptacle). Note for different length C13/C14 cables see #6458 (4.3M) or #6672 (2.0M).

  • Attributes provided: Power jumper cord.
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6672) - Power Cord 2M (6.5-foot), Drawer to IBM PDU, 250V/10A

Standard rack power cable that goes from the system or I/O drawer to the rack power distribution unit (PDU). Cable has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C14 on the other end (for IBM PDU C13 receptacle). Note for different length C13/C14 cables see #6458 (4.3M) or #6671 (2.7M).

  • Attributes provided: Power jumper cord.
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#6680) - Power Cord 2.7m (9-ft), Drawer to Wall/OEM PDU, (250V/10A)

This insulated power cord goes from the system and/or peripheral features to a wall-type outlet. Plug type #6 (AS 3112-1964 NZS 198). Refer to Corporate Bulletin C-B-2-4700-009 for a description of plug types.

The following countries/regions use the #6680 power cord to power the system and/or peripheral features requiring a power cord:

Australia, Fiji Islands, Kiribati, Nauru, New Zealand, Papua New Guinea, W. Samoa.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#7802) - Ethernet Cable, 15m, Hardware Management Console to System Unit

This feature provides a fifteen meter long Ethernet cable for attachment of a Hardware Management Console to the system unit.

  • Attributes provided: 15M Ethernet Cable
  • Attributes required: Ethernet port on Hardware Management Console
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#9169) - Order Routing Indicator- System Plant

This feature will be auto-selected by the Configurator Tool when required. Use of this feature will affect the routing of the order. Selection of this indicator will direct the order to a system plant for fulfillment.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9300) - Language Group Specify - US English

English language group for nomenclature and standard publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9440) - New AIX License Core Counter

This feature is used to count the number of cores licensed to run AIX.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9442) - New Red Hat License Core Counter

This feature is used to count the number of cores licensed to run Red Hat Linux.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9443) - New SUSE License Core Counter

This feature is used to count the number of cores licensed to run SUSE Linux.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9444) - Other AIX License Core Counter

This feature is used to count the number of existing AIX licenses transferred from another server.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9445) - Other Linux License Core Counter

This feature is used to count the number of existing Linux licenses transferred from another server.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9446) - 3rd Party Linux License Core Counter

This feature is used to count the number of cores licensed to run 3rd party Linux.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9447) - VIOS Core Counter

This feature is used to count the number of cores licensed to run VIOS (Virtual I/O Server).

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9449) - Other License Core Counter

This feature is used to count the number of other cores licensed.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9450) - Ubuntu Linux License Core Counter

(No Longer Available as of September 13, 2022)

This feature is used to count the number of cores licensed to run Ubuntu Linux.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9461) - Month Indicator

This month indicator is used to create a date stamp to enable CFR splitting and rejoining in order to circumvent the AAS maximum limitation of 30 systems entered on any one order. The quantity ordered for this feature is generated by eConfig.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 12 (Initial order maximum: 12)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9462) - Day Indicator

This day indicator is used to create a date stamp to enable CFR splitting and rejoining in order to circumvent the AAS maximum limitation of 30 systems entered on any one order. The quantity ordered for this feature is generated by eConfig.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 31 (Initial order maximum: 31)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9463) - Hour Indicator

This hour indicator is used to create a time stamp to enable CFR splitting and rejoining in order to circumvent the AAS maximum limitation of 30 systems entered on any one order. The quantity ordered for this feature is generated by eConfig.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 24 (Initial order maximum: 24)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9464) - Minute Indicator

This hour indicator is used to create a time stamp to enable CFR splitting and rejoining in order to circumvent the AAS maximum limitation of 30 systems entered on any one order. The quantity ordered for this feature is generated by eConfig.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 60 (Initial order maximum: 60)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9465) - Qty Indicator

This quantity indicator is used to specify the remaining, or N-1 quantity of CFR entities that need to be accumulated for rejoining. The quantity ordered for this feature is generated by eConfig.and is equal to N-1, where 'N' equals the total quantity of CFRs being rejoined.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 250)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9466) - Countable Member Indicator

This administrative indicator used to identify each CFR associated with a date/time stamp that is eligible for splitting and rejoining. The quantity ordered for this feature is generated by eConfig.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9700) - Language Group Specify - Dutch

Dutch language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9703) - Language Group Specify - French

French language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9704) - Language Group Specify - German

German language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9705) - Language Group Specify - Polish

Polish language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9706) - Language Group Specify - Norwegian

Norwegian language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9707) - Language Group Specify - Portuguese

Portuguese language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9708) - Language Group Specify - Spanish

Spanish language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9711) - Language Group Specify - Italian

Italian language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9712) - Language Group Specify - Canadian French

Canadian French language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9714) - Language Group Specify - Japanese

Japanese language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9715) - Language Group Specify - Traditional Chinese (Taiwan)

Traditional Chinese language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9716) - Language Group Specify - Korean

Korean language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9718) - Language Group Specify - Turkish

Turkish language group for nomenclature and publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9719) - Language Group Specify - Hungarian

Hungarian language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9720) - Language Group Specify - Slovakian

Slovakian language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9721) - Language Group Specify - Russian

Russian language group for nomenclature and standard publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9722) - Language Group Specify - Simplified Chinese (PRC)

Simplified Chinese language group for nomenclature and standard publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9724) - Language Group Specify - Czech

Czech language group for nomenclature and standard publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9725) - Language Group Specify - Romanian

Romanian language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9726) - Language Group Specify - Croatian

Croatian language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9727) - Language Group Specify - Slovenian

Slovenian language group for Nomenclature and Standard Publications.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9728) - Language Group Specify - Brazilian Portuguese

Brazilian Portuguese language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#9729) - Language Group Specify - Thai

Thai language group for Nomenclature and Standard Publications.

  • Attributes provided: Language specify
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: n/a
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#ALH0) - Expert Care Indicator

This feature indicates the Expert Care Service and Support offering is included on the order. It is for administrative purposes only.

  • Minimum required: 0
  • Maximum allowed: 255 (Initial order maximum: 255)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#B0PR) - SP Hard Drive/Media Retention - Power 5 years

This feature indicates ServicePac Hard Drive/Media Retention - Power 5 years

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#B0VH) - SP HDR/MR POWER 3Y

ServicePac for Hard Drive or Media Retention for Power 3 years

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#B0VP) - SP Machine Setup Support for Power

This feature indicates SP Machine Setup Support for Power.

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EB2J) - 10m (30.3-ft) - IBM MTP 12 strand cable for 40/100G transceivers

QSFP+ cable is used for 40Gb-to-40Gb Ethernet connectivity. Clients can use this QSFP+ Direct Attach Cable for Ethernet connectivity.

  • Attributes provided: 10m QSFP+ to QSFP+ Cable
  • Attributes required: QSFP/QSFP+ ports with optical transceivers
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB2K) - 30m (90.3-ft) - IBM MTP 12 strand cable for 40/100G transceivers

QSFP+ cable is used for 40Gb-to-40Gb Ethernet connectivity. Clients can use this QSFP+ Direct Attach Cable for Ethernet connectivity.

  • Attributes provided: 30m QSFP+ to QSFP+ Cable
  • Attributes required: QSFP/QSFP+ ports with optical transceivers
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB2Z) - Lift Tool

A lift tool raises and lowers servers and I/O drawers so they can be placed into or removed from standard 19-inch racks. It allows heavier equipment to be handled more safely by fewer people. #EB27 has a hand crank to lift and position up to 350 pounds or 159 kg. The #EB2Z length and width are 44 inches x 24.5 inches or 1.12 meters x 0.62 meters. It has rollers which allow it to be moved to different racks in the data center.

  • Attributes provided: Lift Tool
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB39) - Power Supply - 2300W for Server (200-240 VAC)

One 200 - 400V, 2300 watt AC power supply. The power supply is configured in a one plus one or two plus two configuration to provide redundancy. Supported in rack models only. To be operational, a minimum power supply in the CEC base enclosure is required. If there is a power supply failure, any of the power supplies can be exchanged without interrupting the operation of the system.

  • Attributes provided: AC Power Supply.
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB3Z) - Lift tool based on GenieLift GL-8 (standard)

This feature delivers the Low-Cost Lift Tool (based on GenieLift GL-8 (standard)) for IBM servers.

Feature #EB3Z is a feature that is available on multiple Power8, Power9 and Power10 as well as the rack models 7965-S42, 7014-T00, and 7014-T42). Failure to have at least one Lift tool available in a location may result in delayed or prolonged maintenance times.

A lift tool raises and lowers servers and I/O drawers so they can be placed into or removed from standard 19-inch racks. It allows heavier equipment to be handled more safely by fewer people. Lift tool feature EB3Z has a hand crank to lift and position up to 181 kg (400 lbs). The lift tool feature EB3Z operating length and width are 88.3 cm x 62.9 cm (34 3/4 x 24 3/4 in). It has rollers which allow it to be moved to different racks in the data center.

The feature EB3Z is not orderable in the following countries/ regions: Saudi Arabia, Kuwait, UAE, Qatar, Bahrain, Oman, Egypt, Jordan, Morocco, Albania, Bulgaria, Croatia, Greece, Slovakia, Slovenia, Montenegro, Serbia, Ukraine, and Taiwan.

  • Attributes provided: Lift Tool
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB46) - 10GbE Optical Transceiver SFP+ SR

One optical transceiver for 10Gb Ethernet adapter such as #EC2S or #EC2R and also #EC2U or #EC2T using SFP+ SP. Does not include cable.

The 10 Gb optical transceiver is capable up to 300 M through the OM3 cable or 82 M through OM2 cable. Either one or both of the adapter's two SFP+ ports can be populated.

  • Attributes provided: Optical Transceiver SFP+ SR 10Gb
  • Attributes required: SFP+ socket
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB47) - 25GbE Optical Transceiver SFP28

One optical transceiver for 25Gb Ethernet adapter such as #EC2U or #EC2T using SFP28. Does not include cable.

The 25 Gb optical transceiver is capable up to 100 m through the OM4 cable or 70 M through OM3 cable. Either one or both of the adapters two SFP28 ports can be populated.
Note: The SFP28 25GbE transceiver only supports 25GbE speeds.

  • Attributes provided: SFP28 optical transceiver
  • Attributes required: SFP28 socket
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB48) - 1GbE Base-T Transceiver RJ45

One 1GbE Base-T RJ45 transceiver for 25/10Gb Ethernet adapter such as features EC2U or EC2T. Does not include cable. The 1GbE Base-T RJ45 transceiver uses CAT5E STP cable up to 100m.

The transceiver can be plugged into the SFP28 port of EC2U or EC2T in order to provide a 1GbE Base-T RJ45 connection. Either one or both of the adapter's two SFP ports can be populated.

Limitations:

  • SRIOV or RoCE capabilities are not supported on the EC2U or EC2T adapters using this feature EB48.
  • Feature EB48 cannot be used with Feature EB46 - 10GbE Optical Transceiver SFP+ SR or EB47 - 25GbE Optical Transceiver SFP28.
  • Attributes provided: 1Gb RJ45 transceiver
  • Attributes required: SFP socket
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB49) - QSFP28 to SFP28 Connector

This feature provides a QSFP28 to SFP28 connector which enables connections between a single lane transceiver/cable and a quad-lane port. The QSA28 provides the option to connect an SFP28 transceiver or cable to a QSFP28 port 100 Gb/s switch or network card.

The adapter has a QSFP28 form factor with a receptacle for an SFP28 transceiver/AOC/DAC connector. The QSA28 interoperates with all major optical modules and direct attached copper cable. Its design assures minimum loss on the conversion path between the QSFP28 cage and the SFP28 receptacle.

The QSFP28 to SFP28 connector is qualified for 10GbE SFP+ and 1GbE SFP transceivers meeting the Small Form Factor Pluggable (SFP) Transceiver Multi-source Agreement (MSA).
Note: This feature is only available through Offering Management approval, contact douglasg@ca.ibm.com or bbarnett@us.ibm.com for authorization.

  • Attributes provided: QSFP28 to SFP28 Adapter
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB4J) - 0.5m SFP28/25GbE copper Cable

Feature EB4J is a passive 0,5 meter copper cable that contains a single high-speed copper pair, operating at data rates of up to 25 Gb/s. This cable can be used for either 25Gb Ethernet adapters or switches. Built onto each end of the cable is a passive SFP28 copper cable transceiver. Cables are available in various lengths: 0.5M - #EB4J, 1.0M=#EB4K, 1.5M=#EB4L, 2.0M=#EB4M

  • Attributes provided: Copper cable with SFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB4K) - 1.0m SFP28/25GbE copper Cable

Feature EB4K is a passive 1.0 meter copper cable that contains a single high-speed copper pair, operating at data rates of up to 25 Gb/s. This cable can be used for either 25Gb Ethernet adapters or switches. Built onto each end of the cable is a passive SFP28 copper cable transceiver. Cables are available in various lengths: 0.5M - #EB4J, 1.0M=#EB4K, 1.5M=#EB4L, 2.0M=#EB4M

  • Attributes provided: Copper cable with SFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB4M) - 2.0m SFP28/25GbE copper Cable

Feature EB4M is a passive 2.0 meter copper cable that contains a single high-speed copper pair, operating at data rates of up to 25 Gb/s. This cable can be used for either 25Gb Ethernet adapters or switches. Built onto each end of the cable is a passive SFP28 copper cable transceiver. Cables are available in various lengths: 0.5M - #EB4J, 1.0M=#EB4K, 1.5M=#EB4L, 2.0M=#EB4M

  • Attributes provided: Copper cable with SFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB4P) - 2.0m QSFP28/100GbE copper split Cable to SFP28 4x25GbE

Feature EB4P is a 2.0 meter, active optical 100Gb E to 4x25Gb E splitter cable. It provides connectivity between system units with a QSFP28 port on one side and up to four different SFP28 ports on the other side, such as a switch and four servers.

  • Attributes provided: Copper splitter cable with QSFP28 and 4x SFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB4Z) - Service wedge shelf tool kit for EB3Z

This feature provides a separate tool kit to replace the flat shelf with a wedge/angle shelf at the client site.
Note: EB4Z wedge shelf is IBM SSR use only (due to safety labels/ instructions/certifications only for IBM and not filed for clients). A client can order feature EB4Z to ensure the tool is conveniently located on site in case an IBM SSR needed to use it and do not want to wait for the SSR to locate and bring in an EB4Z or to schedule additional personnel to manually handle server installation/removal from the rack.

Client is free to use EB3Z (without EB4Z) for their normal work.

The feature EB4Z is not orderable in the following countries/ regions: Saudi Arabia, Kuwait, UAE, Qatar, Bahrain, Oman, Egypt, Jordan, Morocco, Albania, Bulgaria, Croatia, Greece, Slovakia, Slovenia, Montenegro, Serbia, Ukraine, and Taiwan.

  • Attributes provided: Wedge/angle shelf
  • Attributes required: Feature EB3Z
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: No
  • Return parts MES: No
(#EB57) - QSFP+ 40GbE Base-SR4 Transceiver

IBM QSFP+ optical base-SR4 transceiver required for 40 Gbps ports which are not using copper QSFP+ transceiver.

The QSFP+ 40GbE Base-SR4 Transceiver is designed to deliver the following functions:

  • Hot-swappable input/output device that plugs into a 40 Gigabit Ethernet QSFP port
  • Interoperable with other IEEE-compliant 40GBASE interfaces where applicable
  • High-speed electrical interface compliant to the IEEE 802.3ba standard
  • QSFP Form factor, 2-wire I2C communication interface and other low-speed electrical interface compliant to SFF 8436 and QSFP Multisource Agreement (MSA)
  • Attributes provided: QSFP+ tranceiver for 40 Gbs ports
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB59) - 100GbE Optical Transceiver QSFP28

One optical transceiver for 100Gb Ethernet adapter such as #EC3L or #EC3M or #EC66 or #EC67 using QSFP28. Does not include cable.

See also AOC fiber cables which include QSFP28 transceivers EB5R - EB5Y.

  • Attributes provided: Optical Transceiver QSFP28 100Gb.
  • Attributes required: Port on adapter with QSFP28 socket.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5K) - 1.0M 100GbE Copper Cable QSFP28

1.0 meter length passive copper cable with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches. Copper cable is also called "copper twinax" or "DAC" (Direct Attach Copper).

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EB5M (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Copper cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5L) - 1.5M 100GbE Copper Cable QSFP28

1.5 meter length passive copper cable with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches. Copper cable is also called "copper twinax" or "DAC" (Direct Attach Copper).

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EB5M (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Copper cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5M) - 2.0M 100GbE Copper Cable QSFP28

2.0 meter length passive copper cable with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches. Copper cable is also called "copper twinax" or "DAC" (Direct Attach Copper).

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EB5M (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Copper cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5R) - 3M 100GbE Optical Cable QSFP28 (AOC)

3 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5S) - 5M 100GbE Optical Cable QSFP28 (AOC)

5 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5T) - 10M 100GbE Optical Cable QSFP28 (AOC)

10 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5U) - 15M 100GbE Optical Cable QSFP28 (AOC)

15 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5V) - 20M 100GbE Optical Cable QSFP28 (AOC)

20 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5W) - 30M 100GbE Optical Cable QSFP28 (AOC)

30 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EB5X) - 50M 100GbE Optical Cable QSFP28 (AOC)

50 meter length Active Optical fiber Cable (AOC) with QSFP28 transceivers on each end. The cable used for 100Gb Ethernet adapters or switches.

Cables are available in various lengths. See shorter passive copper cables #EB5J - #EJM (0.5M - 2.0M) or see active optical fiber cables #EJ5R - #EJ5Y (3M - 100M).

  • Attributes provided: Optical fiber cable with QSFP28 transceivers
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EC2S) - PCIe3 2-Port 10Gb NIC&ROCE SR/Cu Adapter

This PCIe Gen3 Ethernet adapter provides two 10 Gb SFP+ ports. The adapter supports both NIC and IBTA RoCE standards. RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet. Using RoCE, the adapter can support significantly greater bandwidth with low latency and minimize CPU overhead by more efficiently using memory access. This offloads the CPU from I/O networking tasks, improving performance and scalability.

Cables: For 10GbE, IBM offers Direct Attach (DAC) cables up to 5m. SFP-based transceivers are included on each end of the cables. See features EN01, EN02, EN03.

Transceivers: IBM qualifies and supports SFP+ optical transceiver (FC EB46) to install into the adapter. Customers can also use their own optical cabling and SFP+ optical transceiver for the other end. The 10 Gb optical transceiver is capable up to 300 M through the OM3 cable or 82 M through OM2 cable. Either one or both of the adapter's two SFP+ ports can be populated.

Feature code #EC2R and #EC2S have identical electronics and function and CCIN (58FA), but have different tail stock brackets. #EC2R is low profile and #EC2S is full high. The adapter is based on a Mellanox ConnectX-4 adapter which uses a ConnectX-4 Lx EN Network Controller.

Attributes:

  • PCI Express 3.0 (up to 8GT/s) x8
  • PCIe Gen 3.0 compliant, 1.1 and 2.0 compatible
  • RDMA over Converged Ethernet (RoCE)
  • NIC and RoCE are concurrently supported
  • RoCE supported on Linux and AIX (7.2 and later)
  • NIC supported on all OSes
  • IEEE 802.3ae (10Gb Ethernet), IEEE 802.3ad (Link Aggregation & Failover), IEEE 802.3az (Energy Efficient Ethernet), IEEE 802.1Q/P (VLAN Tagging), IEEE 802.10au (Congestion Notification), IEEE 802.1Qbg, IEEE 802.3Qaz D0.2 (ETS), IEEE 802.1Qbb D1.0 (PFC), IEEE 1588v2 (PTP)
  • Jumbo frame support up to 9.6KB
  • VXLAN and NVGRE Overlay Network offload support
  • TCP/UDP/IP stateless offload
  • TCP checksum offload
  • TCP segmentation offload
  • UDP checksum offload
  • MSI-X, MSI and support of legacy pin interrupt
  • NIM boot support
  • PowerVM SR-IOV support

For SR-IOV FAQs visit https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-a nd-hnv-information?CommunityKey=71e6bb8a-5b34-44da-be8b-277834a183b0&tab= librarydocuments

  • Attributes provided: 2-port 10Gb Ethernet Adapter
  • Attributes required: Full high PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Red Hat Enterprise Linux 9.0, for Power LE, or later
    • SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 8.4 for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat OpenShift Container Platform 4.9

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC2T) - PCIe3 LP 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter

(No Longer Available as of September 13, 2022)

This PCIe Gen3 Ethernet adapter provides two 25/10 Gb SFP28 ports. The adapter supports both NIC and IBTA RoCE standards. RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet. Using RoCE, the adapter can support significantly greater bandwidth with low latency and minimize CPU overhead by more efficiently using memory access. This offloads the CPU from I/O networking tasks, improving performance and scalability.

Cables: For 25GbE, IBM offers SFP28 Passive Copper 25Gb Ethernet cables up to 2m. SFP28 based transceivers are included on each end of these cables. See features EB4J, EB4K, EB4L, and EB4M for a 0.5M, 1.0M, 1.5M and 2.0M copper cable.

For 10GbE, IBM offers Direct Attach (DAC) cables up to 5m. SFP-based transceivers are included on each end of the cables. See features EN01, EN02, EN03.

Transceivers: For 25 GbE, IBM qualifies and supports SFP28 optical transceiver (FC EB47) to install into the adapter. Customers can also use their own optical cabling and SFP28 optical transceiver for the other end. The 25 Gb optical transceiver is capable up to 100 m through the OM4 cable or 70 M through OM3 cable. Either one or both of the adapter's two SFP28 ports can be populated.
Note: The (FC EB47) SFP28 25GbE transceiver only supports 25GbE speeds.

For 10 GbE, IBM qualifies and supports SFP+ optical transceiver (FC EB46) to install into the adapter. Customers can also use their own optical cabling and SFP+ optical transceiver for the other end. The 10 Gb optical transceiver is capable up to 300 M through the OM3 cable or 82 m through OM2 cable. Either one or both of the adapter's two SFP28 ports can be populated.

For 1GbE, IBM qualifies and supports the 1GbE Base-T Transceiver RJ45 (FC EB48) for 25/10Gb Ethernet adapter (features EC2U or EC2T). The 1GbE Base-T RJ45 transceiver uses CAT5E STP cable up to 100m (does not include cable). The transceiver can be plugged into the SFP28 port of the adapter in order to provide a 1GbE Base-T RJ45 connection.

Feature code #EC2T and #EC2U have identical electronics and function and CCIN (58FB), but have different tail stock brackets. #EC2T is low profile and #EC2U is full high. The adapter is based on a Mellanox ConnectX-4 adapter which uses a ConnectX-4 Lx EN Network Controller.

Attributes:

  • PCI Express 3.0 (up to 8GT/s) x8
  • PCIe Gen 3.0 compliant, 1.1 and 2.0 compatible
  • RDMA over Converged Ethernet (RoCE)
  • NIC and RoCE are concurrently supported
  • RoCE supported on Linux and AIX (7.2 and later)
  • NIC supported on all OSes
  • IEEE 802.3ae (25Gb or 10Gb Ethernet), IEEE 802.3ad (Link Aggregation & Failover), IEEE 802.3az (Energy Efficient Ethernet), IEEE 802.1Q/P (VLAN Tagging), IEEE 802.10au (Congestion Notification), IEEE 802.1Qbg, IEEE 802.3Qaz D0.2 (ETS), IEEE 802.1Qbb D1.0 (PFC), IEEE 1588v2 (PTP)
  • Jumbo frame support up to 9.6KB
  • VXLAN and NVGRE Overlay Network offload support
  • TCP/UDP/IP stateless offload
  • TCP checksum offload
  • TCP segmentation offload
  • UDP checksum offload
  • MSI-X, MSI and support of legacy pin interrupt
  • NIM boot support
  • PowerVM SR-IOV support

For SR-IOV FAQs visit https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-a nd-hnv-information?CommunityKey=71e6bb8a-5b34-44da-be8b-277834a183b0&tab= librarydocuments

  • Attributes provided: 2-port 25/10Gb Ethernet
  • Attributes required: Low profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Red Hat Enterprise Linux 8.4, for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux 9.0, for Power LE, or later
    • SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 8.4 for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat OpenShift Container Platform 4.9
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC2U) - PCIe3 2-Port 25/10Gb NIC&ROCE SR/Cu Adapter

This PCIe Gen3 Ethernet adapter provides two 25/10 Gb SFP28 ports. The adapter supports both NIC and IBTA RoCE standards. RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet. Using RoCE, the adapter can support significantly greater bandwidth with low latency and minimize CPU overhead by more efficiently using memory access. This offloads the CPU from I/O networking tasks, improving performance and scalability.

Cables: For 25GbE, IBM offers SFP28 Passive Copper 25Gb Ethernet cables up to 2m. SFP28 based transceivers are included on each end of these cables. See features EB4J, EB4K, EB4L, and EB4M for a 0.5M, 1.0M, 1.5M and 2.0M copper cable.

For 10GbE, IBM offers Direct Attach (DAC) cables up to 5m. SFP-based transceivers are included on each end of the cables. See features EN01, EN02, EN03.

Transceivers: For 25 GbE, IBM qualifies and supports SFP28 optical transceiver (FC EB47) to install into the adapter. Customers can also use their own optical cabling and SFP28 optical transceiver for the other end. The 25 Gb optical transceiver is capable up to 100 m through the OM4 cable or 70 M through OM3 cable. Either one or both of the adapter's two SFP28 ports can be populated.
Note: The (FC EB47) SFP28 25GbE transceiver only supports 25GbE speeds.

For 10 GbE, IBM qualifies and supports SFP+ optical transceiver (FC EB46) to install into the adapter. Customers can also use their own optical cabling and SFP+ optical transceiver for the other end. The 10 Gb optical transceiver is capable up to 300 M through the OM3 cable or 82 m through OM2 cable. Either one or both of the adapter's two SFP28 ports can be populated.

For 1GbE, IBM qualifies and supports the 1GbE Base-T Transceiver RJ45 (FC EB48) for 25/10Gb Ethernet adapter (features EC2U or EC2T). The 1GbE Base-T RJ45 transceiver uses CAT5E STP cable up to 100m (does not include cable). The transceiver can be plugged into the SFP28 port of the adapter in order to provide a 1GbE Base-T RJ45 connection.

Feature code #EC2T and #EC2U have identical electronics and function and CCIN (58FB), but have different tail stock brackets. #EC2T is low profile and #EC2U is full high. The adapter is based on a Mellanox ConnectX-4 adapter which uses a ConnectX-4 Lx EN Network Controller.

Attributes:

  • PCI Express 3.0 (up to 8GT/s) x8
  • PCIe Gen 3.0 compliant, 1.1 and 2.0 compatible
  • RDMA over Converged Ethernet (RoCE)
  • NIC and RoCE are concurrently supported
  • RoCE supported on Linux and AIX (7.2 and later)
  • NIC supported on all OSes
  • IEEE 802.3ae (25Gb or 10Gb Ethernet), IEEE 802.3ad (Link Aggregation & Failover), IEEE 802.3az (Energy Efficient Ethernet), IEEE 802.1Q/P (VLAN Tagging), IEEE 802.10au (Congestion Notification), IEEE 802.1Qbg, IEEE 802.3Qaz D0.2 (ETS), IEEE 802.1Qbb D1.0 (PFC), IEEE 1588v2 (PTP)
  • Jumbo frame support up to 9.6KB
  • VXLAN and NVGRE Overlay Network offload support
  • TCP/UDP/IP stateless offload
  • TCP checksum offload
  • TCP segmentation offload
  • UDP checksum offload
  • MSI-X, MSI and support of legacy pin interrupt
  • NIM boot support
  • PowerVM SR-IOV support

For SR-IOV FAQs visit https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-a nd-hnv-information?CommunityKey=71e6bb8a-5b34-44da-be8b-277834a183b0&tab= librarydocuments

  • Attributes provided: 2-port 25/10Gb Ethernet Adapter
  • Attributes required: Full high PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 51)
  • OS level required:
    • AIX - supported
    • Red Hat Enterprise Linux 8.4, for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux 9.0, for Power LE, or later
    • SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 8.4 for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat OpenShift Container Platform 4.9

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5B) - PCIe3 x8 1.6 TB NVMe Flash Adapter for AIX/Linux

The PCIe3 x8 1.6 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 3 (Gen3) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 58FC.

Feature #EC5G and #EC5B are identical cards except that the tailstock bracket is different. #EC5G fits a low profile PCIe slot. #EC5B fits a full high PCIe slot. See also #EC5D/EC5F for a card with more memory.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC5B can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 32 namespaces per device.

  • Attributes provided: 1.6 TB of low latency flash memory with boot capability
  • Attributes required: PCIe slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5D) - PCIe3 x8 3.2 TB NVMe Flash Adapter for AIX/Linux

The PCIe3 x8 3.2 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 3 (Gen3) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 58FD.

Feature #EC5C and #EC5D are identical cards except that the tailstock bracket is different. #EC5C fits a low profile PCIe slot. #EC5D fits a full high PCIe slot. See also #EC5F for a card with more memory.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC5D can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 32 namespaces per device.

  • Attributes provided: 3.2 TB of low latency flash memory with boot capability
  • Attributes required: PCIe slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5F) - PCIe3 x8 6.4 TB NVMe Flash Adapter for AIX/Linux

The PCIe3 x8 6.4 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 3 (Gen3) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 58FE.

Feature #EC5E and #EC5F are identical cards except that the tailstock bracket is different. #EC5E fits a low profile PCIe slot. #EC5F fits a full high PCIe slot. See also EC5D for a card with less memory.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC5F can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 32 namespaces per device.

  • Attributes provided: 6.4 TB of low latency flash memory with boot capability
  • Attributes required: PCIe slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5J) - Mainstream 800 GB SSD NVMe U.2 module

Mainstream 800 GB solid state drive (SSD) formatted in 4096 byte sectors (4K). The drive is U.2 2.5" 7mm form factor supporting NVMe PCIe Gen3 x 4 interface. Recommend to be used for boot support and non-write intensive workloads.

DWPD (Drive Write Per Day) rating is 2.4 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (PB)
800 GB 3.5
1.6 TB 7
3.2 TB 14

Depending on the nature of the workload, the lifetime TBW may be somewhat larger.

To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

  • Attributes provided: 800 GB low latency flash memory
  • Attributes required: PCIe Gen3 slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5K) - Mainstream 1.6 TB SSD NVMe U.2 module

Mainstream 1.6 TB solid state drive (SSD) formatted in 4096 byte sectors (4K). The drive is U.2 2.5" 7mm form factor supporting NVMe PCIe Gen3 x 4 interface. Recommend to be used for boot support and non-write intensive workloads.

DWPD (Drive Write Per Day) rating is 2.4 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (PB)
800 GB 3.5
1.6 TB 7
3.2 TB 14

Depending on the nature of the workload, the lifetime TBW may be somewhat larger.

To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

  • Attributes provided: 1.6 TB low latency flash memory
  • Attributes required: PCIe Gen3 slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5L) - Mainstream 3.2 TB SSD NVMe U.2 module

Mainstream 3.2 TB solid state drive (SSD) formatted in 4096 byte sectors (4K). The drive is U.2 2.5" 7mm form factor supporting NVMe PCIe Gen3 x 4 interface. Recommend to be used for boot support and non-write intensive workloads.

DWPD (Drive Write Per Day) rating is 2.4 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (PB)
800 GB 3.5
1.6 TB 7
3.2 TB 14

Depending on the nature of the workload, the lifetime TBW may be somewhat larger.

To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

  • Attributes provided: 3.2 TB low latency flash memory
  • Attributes required: PCIe Gen3 slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5V) - Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 6.4 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #EC5V and #EC5W are physically identical drives with the same CCIN of 59BA. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature EC5V indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature EC5W indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC5X) - Mainstream 800 GB SSD PCIe3 NVMe U.2 module for AIX/Linux

Mainstream 800 GB NVMe SFF U.2 7mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 3 (Gen3) drive. The SSD can be used in any U.2 7mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Feature #EC5X has CCIN of 59B7. Feature EC5X indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors.

This Mainstream solid-state drive is rated at 2.4 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

  • Attributes provided: 800 GB low latency flash memory
  • Attributes required: SFF U.2 15mm
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC66) - PCIe4 2-port 100Gb ROCE EN adapter

This PCIe Gen4 Ethernet x16 adapter provides two 100 GbE QSFP28 ports. The adapter supports both NIC and IBTA RoCE standards. RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet. Using RoCE, the adapter can support significantly greater bandwidth with low latency and minimize CPU overhead by more efficiently using memory access. This offloads the CPU from I/O networking tasks, improving performance and scalability.

For 100GbE network connectivity, IBM offers either passive copper twinax cables up to 2 meters in length or active optical cables up to 100 meters in length. See features #EB5J - #EB5M for a 0.5M, 1.0M, 1.5M and 2.0M copper cable. See features #EB5R - #EB5Y for a 3M, 5M, 10M, 15M, 20M, 30M, 50M or 100M active optical cable. Transceivers are included on each end of these QSFP28 cables. Alternatively to the above supported cables, you may choose to order an IBM qualified and supported QSFP28 optical transceiver (feature #EB59) to put into the adapter ports and MTP/MPO cable 10M or 30M in length (feature #EB2J or #EB2K) optical cabling to use with your own QSP28 optical transceiver for the other end.

For 40GbE network connectivity, IBM offers either passive copper twinax cables up to 3 meters in length. See features #EB2B and EB2H for a 1.0M and 3.0M copper cable. Transceivers are included on each end of these QSFP+ cables. Alternatively to the above supported cables, you may choose to order an IBM qualified and supported QSFP+ 40G BASE-SR optical transceiver (feature #EB27) to put into the adapter ports and MTP/MPO cable 10M or 30M in length (feature #EB2J or #EB2K) optical cabling to use with your own QSP28 optical transceiver for the other end.

Either one or both of the adapter's two QSP28 ports can be populated. When two ports are filled, both can have copper cables, both can have optical cables, or one can be copper and one can be optical.

Feature code #EC66 and #EC67 have identical electronics and function and CCIN (2CF3), but have different tail stock brackets. #EC66 is high profile and #EC67 is low profile. The adapter is based on a Mellanox ConnectX-5 adapter which uses a ConnectX-5 EN Network Controller.

Attributes:

  • PCI Express 4.0 (up to 16GT/s) x16
  • PCIe Gen 4.0 compliant, 1.1, 2.0 and 3.0 compatible
  • RDMA over Converged Ethernet (RoCE)
  • NIC and RoCE are concurrently supported
  • RoCE supported on Linux and AIX
  • NIC supported on all OSes
  • TCP/UDP/IP stateless offload
  • LSO, LRO, checksum offload
  • NIM boot support
  • Backward compatible with 40Gb Ethernet when using compatible cables/transceivers
  • PowerVM SR-IOV support

For SR-IOV FAQs visit https://community.ibm.com/community/user/power/viewdocument/sr-iov-vnic-a nd-hnv-information?CommunityKey=71e6bb8a-5b34-44da-be8b-277834a183b0&tab= librarydocuments

  • Attributes provided: Dual-port 100 GbE Adapter with RoCE capability
  • Attributes required: Available Gen4 PCIe Slot
  • Minimum required: 0
  • Maximum allowed: 6 (Initial order maximum: 6)
  • OS level required:
    • AIX - supported
    • Red Hat Enterprise Linux 8.4, for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux 9.0, for Power LE, or later
    • SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise Server 15 Service Pack 3, or later, with Mellanox OFED 5.5, or later
    • Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 8.4 for Power LE, or later, with Mellanox OFED 5.5, or later
    • Red Hat OpenShift Container Platform 4.9

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC6K) - PCIe2 2-Port USB 3.0 Adapter

The PCIe Gen2 x8 short 2-port USB 3.0 adapter provides support for USB devices. In applications that require the use of an USB extension cable for keyboards, use one #4256 per port. The #EC6J and #EC6K USB adapters are electronically identical with the same 590F CCIN. They differ physically in their tailstock. #EC6J is low profile and #EC6K is full high.

  • Attributes provided: Connectivity with USB 2.0 - 3.0 capable devices
  • Attributes required: One low profile available PCIe slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX supported
    • Linux supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC76) - PCIe4 2-port 100Gb No Crypto Connectx-6 DX QFSP56

This PCIe Gen4 Ethernet x16 adapter provides two 100 GbE QFSP56 ports. The adapter supports both NIC and IBTA RoCE standards. RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet. Using RoCE, the adapter can support significantly greater bandwidth with low latency and minimize CPU overhead by more efficiently using memory access. This offloads the CPU from I/O networking tasks, improving performance and scalability.

For 100GbE network connectivity, IBM offers either passive copper twinax cables up to 2 meters in length or active optical cables up to 100 meters in length. See features #EB5J - #EB5M for a 0.5M, 1.0M, 1.5M and 2.0M copper cable. See features #EB5R - #EB5Y for a 3M, 5M, 10M, 15M, 20M, 30M, 50M or 100M active optical cable. Transceivers are included on each end of these QFSP56 cables. Alternatively to the above supported cables, you may choose to order an IBM qualified and supported QFSP56 optical transceiver (feature #EB59) to put into the adapter ports and MTP/MPO cable 10M or 30M in length (feature #EB2J or #EB2K) optical cabling to use with your own QFSP56 optical transceiver for the other end.

For 40GbE network connectivity, IBM offers either passive copper twinax cables up to 3 meters in length. See features #EB2B and EB2H for a 1.0M and 3.0M copper cable. Transceivers are included on each end of these QSFP+ cables. Alternatively to the above supported cables, you may choose to order an IBM qualified and supported QSFP+ 40G BASE-SR optical transceiver to put into the adapter ports and MTP/MPO cable 30M in length (feature #EB2K) optical cabling to use with your own QFSP56 optical transceiver for the other end.

Either one or both of the adapter's two QFSP56 ports can be populated. When two ports are filled, both can have copper cables, both can have optical cables, or one can be copper and one can be optical.

Feature code #EC76 and #EC75 have identical electronics and function and CCIN (2CFB), but have different tail stock brackets. #EC76 is high profile and #EC75 is low profile. The adapter is based on a Mellanox ConnectX-6 adapter which uses a ConnectX-6 EN Network Controller.

Attributes:

  • PCI Express 4.0 (up to 16GT/s) x16
  • PCIe Gen 4.0 compliant, 1.1, 2.0 and 3.0 compatible
  • RDMA over Converged Ethernet (RoCE)
  • NIC and RoCE are concurrently supported
  • RoCE supported on Linux and AIX
  • NIC supported on all OSes
  • TCP/UDP/IP stateless offload
  • LSO, LRO, checksum offload
  • NIM boot support
  • Backward compatible with 40Gb Ethernet when using compatible cables/transceivers
  • PowerVM SR-IOV support

For SR-IOV FAQs visit https://community.ibm.com/community/user/power/ viewdocument/sr-iov-vnic-a nd-hnv- information?CommunityKey=71e6bb8a-5b34-44da-be8b-277834a183b0& tab= librarydocuments

  • Attributes provided: 2-port 100Gb Ethernet
  • Attributes required: Full-high x16 PCIe Gen4 slot
  • Minimum required: 0
  • Maximum allowed: 6 (Initial order maximum: 6)
  • OS level required:
    • AIX Version 7.3 with the 7300-01 Technology Level and Service Pack 7300-01-01-2246, or later
    • AIX Version 7.2 with the 7200-05 Technology Level and Service Pack 7200-05-05-2246, or later
    • AIX Version 7.3 with the 7300-00 Technology Level and Service Pack 7300-00-03-2246, or later (planned availability date March 17, 2023)
    • SUSE Linux Enterprise Server 15, Service Pack 4, or later, with Mellanox OFED 5.7, or later
    • Red Hat Enterprise Linux 8.6, for POWER LE, or later, with Mellanox OFED 5.7, or later
    • Red Hat OpenShift Container Platform, 4.11, or later

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS requires VIOS 3.1.4.10, or later
(#EC7B) - PCIe4 1.6TB NVMe Flash Adapter x8 for AIX/Linux

The PCIe4 x8 1.6 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 594A.

Feature #EC7A and #EC7B are identical cards except that the tailstock bracket is different. #EC7A fits a low profile PCIe slot. #EC7B fits a full high PCIe slot. See also #EC7C or #EC7D for a card with more memory.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC7A or #EC7B can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: NVMe Flash Adapter
  • Attributes required: one slot available
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX supported
    • Linux supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC7D) - PCIe4 3.2TB NVMe Flash Adapter x8 for AIX/Linux

The PCIe4 x8 3.2 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 594B.

Feature #EC7C and #EC7D are identical cards except that the tailstock bracket is different. #EC7C fits a low profile PCIe slot. #EC7D fits a full high PCIe slot. See also EC7E or EC7F for a card with more memory.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC7C or #EC7D can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: NVMe Flash Adapter
  • Attributes required: one slot available
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX supported
    • Linux supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC7F) - PCIe4 6.4TB NVMe Flash Adapter x8 for AIX/Linux

The PCIe4 x8 6.4 TB NVMe Adapter is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) x8 adapter. The adapter can be used in either a x8 or x16 PCIe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance software interface that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe Flash adapter provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

CCIN is 594C.

Feature #EC7E and #EC7F are identical cards except that the tailstock bracket is different. #EC7E fits a low profile PCIe slot. #EC7F fits a full high PCIe slot.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes are used instead of random writes, the maximum write capacity will be larger. To extend the life of the device, the application that is using the device must convert small random writes to larger sequential writes. Writes past the adapter's maximum write capacity will continue to work for some period of time, but much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the adapter if enabled by the system administrator. Customers are recommended to monitor the smart log via their operating system where fuel gauge shows the percentage used.

IBM NVMe adapter failures will be replaced during the standard warranty and maintenance period for adapters that have not reached the maximum number of write cycles. Adapters that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Data protection is not implemented in the card; protection is provided by OS mirroring or software RAID wherever applicable.

This adapter is not supported in the PCIe I/O drawer.
Note: NVMe Flash adapters #EC7E or #EC7F can be used to meet minimum AIX/ Linux SSD/HDD and backplane requirements.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: NVMe Flash Adapter
  • Attributes required: one slot available
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX supported
    • Linux supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC7Q) - 800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux

Mainstream 800 GB NVMe SFF U.2 7mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 7mm Non-Volatile Memory Express (NVMe) PCIe Gen4 x 4 interface in the system. NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Feature #EC7Q has the CCIN number of 59B4 and indicates usage by AIX, Linux, or VIOS in which the SSD is formatted in 4096 byte sectors.

Mainstream 800 GB solid state drive (SSD) formatted in 4096 byte sectors (4K). This Mainstream solid-state drive is rated at 2.4 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger. Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

  • Attributes provided: 800 GB low latency flash memory
  • Attributes required: PCIe Gen3 slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC7T) - 800GB Mainstream NVMe U.2 SSD 4k for AIX/Linux

Mainstream 800 GB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm Non-Volatile Memory Express (NVMe) PCIe Gen4 x 4 interface in the system. NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Feature #EC7T has the CCIN number of 59B7 and indicates usage by AIX, Linux, or VIOS in which the SSD is formatted in 4096 byte sectors.

Mainstream 800 GB solid state drive (SSD) formatted in 4096 byte sectors (4K). This Mainstream solid-state drive is rated at 2.4 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger. Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

  • Attributes provided: 800 GB low latency flash memory
  • Attributes required: PCIe Gen4 slot in system unit
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EC7X) - Carrier Conversion Kit for 7mm to 15mm NVMe Devices

This feature allows to migrate an existing 7mm NVMe devices to the 15mm NVMe devices in 9043-MRX platform.

  • Attributes provided: One 15mm NVMe carrier
  • Attributes required: an empty 15mm device carrier plus an empty 15mm device slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECB2) - 1.5m (4.9-ft), Blue CAT5 Ethernet Cable

This cable connects the Flex System Enterprise Chassis to managed PDUs and the IBM Storwize V7000 Disk System.

  • Attributes provided: 1.5m Cat5 Ethernet Cable
  • Attributes required: RJ45 ports/transceivers.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBJ) - SAS X Cable 3m - HD Narrow 6Gb 2-Adapters to Enclosure

This 3 meter SAS cable connects two PCIe2 SAS adapters or two PCIe3 SAS adapters to a SAS I/O enclosure. This X cable has four connectors, two Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connectors attach to two SAS adapters such as two #EJ0J or two #EJ0L or two #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

This cable is almost identical to the #3454 3m SAS X cable, except #ECBJ connectors for the SAS adapters are more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBK) - SAS X Cable 6m - HD Narrow 6Gb 2-Adapters to Enclosure

This 3 meter SAS cable connects two PCIe2 SAS adapters or two PCIe3 SAS adapters to a SAS I/O enclosure. This X cable has four connectors, two Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connectors attach to two SAS adapters such as two #EJ0J or two #EJ0L or two #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

This cable is almost identical to the #3454 3m SAS X cable, except #ECBJ connectors for the SAS adapters are more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

This 6 meter SAS cable connects two SAS adapters to a SAS I/O enclosure. This X cable has four connectors, two Mini-SAS HD (High Density) connector and two Mini SAS connectors. The Mini-SAS HD connectors attaches to two SAS adapters such as the #5913 1.8GB RAID SAS Adapter. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapters can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: When this cable is ordered with a system in a rack specifying IBM Plant integration, IBM Manufacturing will ship SAS cables longer than 3 meters in a separate box and not attempt to place the cable in the rack.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBM) - SAS X Cable 15m - HD Narrow 3Gb 2-Adapters to Enclosure

This 15 meter SAS cable connects two PCIe2 SAS adapters or two PCIe3 SAS adapters to a SAS I/O enclosure. This X cable has four connectors, two Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connectors attach to two SAS adapters such as two #EJ0J or two #EJ0L or two #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

This cable is almost identical to the #3458 15m SAS X cable, except #ECBM connectors for the SAS adapters are more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

Limitation: When this cable is ordered with a system in a rack specifying IBM Plant integration, IBM Manufacturing will ship SAS cables longer than 3 meters in a separate box and not attempt to place the cable in the rack.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#ECBT) - SAS YO Cable 1.5m - HD Narrow 6Gb Adapter to Enclosure

This 1.5 meter SAS cable connects a PCIe2 SAS adapter or a PCIe3 SAS adapter to a SAS I/O enclosure. This YO cable has three connectors, one Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0J or #EJ0L or #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable.

This cable is almost identical to the #3450 1.5m SAS YO cable, except the #ECBT connector for the SAS adapters is more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controller and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBU) - SAS YO Cable 3m - HD Narrow 6Gb Adapter to Enclosure

This 3 meter SAS cable connects a PCIe2 SAS adapter or a PCIe3 SAS adapter to a SAS I/O enclosure. This YO cable has three connectors, one Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0J or #EJ0L or #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable.

This cable is almost identical to the #3451 3m SAS YO cable, except the #ECBU connector for the SAS adapters is more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controller and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBV) - SAS YO Cable 6m - HD Narrow 6Gb Adapter to Enclosure

This 6 meter SAS cable connects a PCIe2 SAS adapter or a PCIe3 SAS adapter to a SAS I/O enclosure. This YO cable has three connectors, one Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0J or #EJ0L or #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable.

This cable is almost identical to the #3452 6m SAS YO cable, except the #ECBV connector for the SAS adapters is more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

Limitation: When this cable is ordered with a system in a rack specifying IBM Plant integration, IBM Manufacturing will ship SAS cables longer than 3 meters in a separate box and not attempt to place the cable in the rack.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controller and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBW) - SAS YO Cable 10m - HD Narrow 6Gb Adapter to Enclosure

This 10 meter SAS cable connects a PCIe2 SAS adapter or a PCIe3 SAS adapter to a SAS I/O enclosure. This YO cable has three connectors, one Mini-SAS HD (High Density) Narrow connector and two Mini SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0J or #EJ0L or #5913. Both Mini SAS connectors attach to the same I/O drawer (enclosure) such as a #5886 EXP12S or #5887 EXP24S SAS I/O drawer. This cable can support up to 6Gb throughput.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/O drawer. See SAS cabling documentation for the length of each leg of the cable.

This cable is almost identical to the #3453 10m SAS YO cable, except the #ECBW connector for the SAS adapters is more narrow allowing it to fit onto the newer PCIe3 SAS adapters.

Limitation: When this cable is ordered with a system in a rack specifying IBM Plant integration, IBM Manufacturing will ship SAS cables longer than 3 meters in a separate box and not attempt to place the cable in the rack.

  • Attributes provided: Connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS I/O drawer with Mini-SAS connectors or between PCIe2 SAS adapter with Mini-SAS HD connectors and a SAS I/O drawer with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controller and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBY) - SAS AE1 Cable 4m - HD Narrow 6Gb Adapter to Enclosure

This 4 meter SAS cable connects a PCIe3 SAS adapter to a SAS tape drive or DVD. The tape drive or DVD is probably in an I/O enclosure such as a bridge box or 1U media enclosure or tape library. This AE cable has two connectors, one Mini-SAS HD (High Density) Narrow connector and one Mini-SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0X. The Mini-SAS connector attaches to a SAS tape drive enclosure or DVD. This cable can support up to 6Gb throughput.

Use #ECBY when ordering the cable as a feature code on a Power System. Alternatively the same cable can be ordered using feature code #5507 of the IBM tape enclosure or DVD.

  • Attributes provided: connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and a SAS tape drive or DVD with Mini-SAS connectors
  • Attributes required: available connectors on SAS controller such as #EJ0X, #EJ10 or #EJ11 for use with an available SAS tape drive or DVD.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECBZ) - SAS YE1 Cable 3m - HD Narrow 6Gb Adapter to Enclosure

This 3 meter SAS cable connects a PCIe3 SAS adapter to one or two SAS tape drives. The tape drive(s) is probably in an I/O enclosure such as a bridge box or 1U media enclosure or tape library. This YO cable has three connectors, one Mini-SAS HD (High Density) Narrow connector and two Mini-SAS connectors. The Mini-SAS HD Narrow connector attaches to a SAS adapter such as the #EJ0X. Each Mini-SAS connector attaches to a different SAS tape drive enclosure. This cable can support up to 6Gb throughput.

Use #ECBZ when ordering the cable as a feature code on a Power System. Alternatively the same cable can be ordered using feature code #5509 of the IBM tape enclosure.

  • Attributes provided: connection between PCIe3 SAS adapter with Mini-SAS HD Narrow connectors and one or two SAS tape drives with Mini-SAS connectors.
  • Attributes required: available connectors on SAS controller such as #EJ0X, #EJ10 or #EJ11 for use with an available SAS tape drive.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECCF) - System Port Converter Cable for UPS

Converter cable allows a serial cable attached to a Uninterruptible Power Supply (UPS) to connect to a USB port on the server's service processor card. Cable's connectors are USB (Male) and 9 PIN D SHELL (Female) and the cable's length is about 1.6m (60 inches). The UPS can provide power status information over the cable to IBM i.

  • Attributes provided: Converter Cable
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECCS) - 3M Copper CXP Cable Pair for PCIe3 Expansion Drawer

This 3.0 meter cable pair connects a PCIe3 fan-out module in the PCIe Gen3 I/O Expansion Drawer to a PCIe3 Optical Converter Adapter in the system unit. There are two identical copper cables in the cable pair, each with two CXP connectors. One of the cables attaches to the top CXP port of the PCIe3 fan-out module and to the top CXP port of the PCIe3 Optical Converter Adapter. The other cable attaches to the bottom CXP ports.

"Optical" Converter Adapter features were named when only optical cables were announced and copper cables were not planned. The output of the adapter is a CXP interface which can also be used for this copper cable pair.

See also optical AOC cables features for cables which are much thinner and can be longer such as the feature #ECC8 (10 meter) cable, but are more costly.

Limitation: Cannot mix copper and optical cables on the same PCIe Gen3 I/O drawer. Both fan-out modules use copper cables or both use optical cables.

  • Attributes provided: Pair of 3 meter CXP copper cables
  • Attributes required:
    • CXP ports on a PCIe3 Optical Cable Adapter (#EJ05 or #EJ08) and on a PCIe3 module such as a #EMXF or EMXG/ELMF or ELMG in a PCIe Gen3 Expansion Drawer (#EMX0/ELMX).
    • Firmware level 8.40 or later.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECCX) - 3M Active Optical Cable Pair for PCIe3 Expansion Drawer

The 3.0 meter active optical cable (AOC) pair connects a PCIe3 module in the PCIe Gen3 I/O Expansion Drawer to a PCIe3 Optical Converter Adapter in the system unit. There are two identical cables in the cable pair, each with two CXP connectors. One of the cables attaches to the top CXP port of the PCIe3 module and to the top CXP port of the PCIe3 Optical Converter Adapter. The other cable attaches to the bottom CXP ports.

  • Attributes provided: Pair of 3 meter active optical cables
  • Attributes required: CXP ports on a PCIe3 Optical Cable Adapter and on a PCIe3 module iin a PCIe Gen3 Expansion Drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECCY) - 10M Active Optical Cable Pair for PCIe3 Expansion Drawer

The 10.0 meter active optical cable (AOC) pair connects a PCIe3 module in the PCIe Gen3 I/O Expansion Drawer to a PCIe3 Optical Converter Adapter in the system unit. There are two identical cables in the cable pair, each with two CXP connectors. One of the cables attaches to the top CXP port of the PCIe3 module and to the top CXP port of the PCIe3 Optical Converter Adapter. The other cable attaches to the bottom CXP ports.

  • Attributes provided: Pair of 10 meter active optical cables
  • Attributes required: CXP ports on a PCIe3 Optical Cable Adapter and on a PCIe3 module in a PCIe Gen3 Expansion Drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDJ) - 3.0M SAS X12 Cable (Two Adapter to Enclosure)

This 3 meter SAS cable connects two SAS adapters to a SAS I/O enclosure. This X cable has four Mini-SAS HD (High Density) connectors. Two of connectors attach to two SAS adapters such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/ O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.

  • Attributes provided: Connection between two SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDK) - 4.5M SAS X12 Active Optical Cable (Two Adapter to Enclosure)

This 4.5 meter SAS cable connects two SAS adapters to a SAS I/O enclosure. This X cable has four Mini-SAS HD (High Density) connectors. Two of connectors attach to two SAS adapters such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/ O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.
Note: AOC cables require minimum level of SAS Adapter firmware. Refer to the latest prerequisites at

https://www14.software.ibm.com/webapp/set2/iprt/home
  • Attributes provided: Connection between two SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDL) - 10M SAS X12 Active Optical Cable (Two Adapter to Enclosure)

This 10 meter SAS cable connects two SAS adapters to a SAS I/O enclosure. This X cable has four Mini-SAS HD (High Density) connectors. Two of connectors attach to two SAS adapters such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/ O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.
Note: AOC cables require minimum level of SAS Adapter firmware. Refer to the latest prerequisites at

https://www14.software.ibm.com/webapp/set2/iprt/home
  • Attributes provided: Connection between two SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDT) - 1.5M SAS YO12 Cable (Adapter to Enclosure)

This 1.5 meter SAS cable connects one SAS adapter to a SAS I/O enclosure. This YO cable has three Mini-SAS HD (High Density) connectors. One of connectors attach to a SAS adapter such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.

  • Attributes provided: Connection between a SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDU) - 3.0M SAS YO12 Cable (Adapter to Enclosure)

This 3 meter SAS cable connects one SAS adapter to a SAS I/O enclosure. This YO cable has three Mini-SAS HD (High Density) connectors. One of connectors attach to a SAS adapter such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.

  • Attributes provided: Connection between a SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDV) - 4.5M SAS YO12 Active Optical Cable (Adapter to Enclosure)

This 4.5 meter SAS cable connects one SAS adapter to a SAS I/O enclosure. This YO cable has three Mini-SAS HD (High Density) connectors. One of connectors attach to a SAS adapter such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.
Note: AOC cables require minimum level of SAS Adapter firmware. Refer to the latest prerequisites at

https://www14.software.ibm.com/webapp/set2/iprt/home
  • Attributes provided: Connection between a SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECDW) - 10M SAS YO12 Active Optical Cable (Adapter to Enclosure)

This 10 meter SAS cable connects one SAS adapter to a SAS I/O enclosure. This YO cable has three Mini-SAS HD (High Density) connectors. One of connectors attach to a SAS adapter such as in the PCIe3 SAS Adapter. The other two connectors attach to one SAS I/O Enclosure such as the EXP24SX (#ESLS/ #ELLS). This cable is designed for high speed (DHS) to support up to 12Gb throughput if the adapter has that capability.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the adapter and the I/ O drawer. See SAS cabling documentation for the length of each leg of the cable. The SAS adapters can be in the same or in different PCIe I/O drawers. Or one adapter can be in a supported Power System CEC and the other adapter can be in a PCIe I/O drawer. Or both adapters can be in a supported Power System CEC.

Limitation: This cable cannot be used with the EXP24S I/O drawer (#5887 or# EL1S) which uses Mini-SAS connectors which are not HD.
Note: AOC cables require minimum level of SAS Adapter firmware. Refer to the latest prerequisites at

https://www14.software.ibm.com/webapp/set2/iprt/home
  • Attributes provided: Connection between a SAS adapters with Mini-SAS HD connectors and a SAS I/O drawer with Mini SAS HD connectors
  • Attributes required: Available connectors on SAS controllers and SAS I/O drawer
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECE0) - 0.6M SAS AA12 Cable (Adapter to Adapter)

This 0.6 meter SAS cable connects a pair of SAS adapters to each other. This AA cable has two Mini-SAS HD (High Density) connectors which connect the top connectors of two PCIe3 SAS adapters with write cachce such as #EJ0L or #EJ14. The cable provides a high performance path of all the dual controller communication including mirroring the write cache and status awareness of each card. This cable is designed for high speed to support up to 12Gb throughput. Note EJ0L/EJ14 support 6Gb.

Two AA cables are always required between a pair of PCIe3 SAS adapters with write cache when just one or two I/O drawers are attached. One AA cable is required if three I/O drawers are attached. If four drawers are attached or if an AA cable fails or is disconnected, then the information it was carrying is then sent over the cables attached to the I/O drawers, sharing their bandwidth. AA cables are not used with SAS adapters with no write cache.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the two adapters.

The 6Gb version of this cable is feature #5918. #5918 and #ECE0 can be mixed on the same PCIe3 adapter pair.

  • Attributes provided: Connection between two SAS adapters with Mini-SAS HD connectors
  • Attributes required: Available connectors on SAS controllers
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECE3) - 3.0M SAS AA12 Cable

This 3.0 meter SAS cable has two Mini-SAS HD (High Density) connectors, and is designed for high speed to support up to 12Gb throughput. This is a straight cable (in contrast with X or YO cables) that has two distinct uses:

  1. For Elastic Storage Server (ESS) solutions that have a 5147-024 I/O drawer, this cable is used to attach the 5147-024 to its controller.
  2. For POWER Servers with #5887, #EL1S, #ESLS, #ESLL, #ELLS, or #ELLL I/O drawers driven by paired PCIe controllers with write cache such as #EJ0L or #EJ14, this cable is used to connect the top connectors of the paired controllers. The cable provides a high performance path of all the dual controller communication including mirroring the write cache and status awareness of each card.

Note that X or YO cables are always used to attach I/O drawers #5887, #EL1S, #ESLS, #ESLL, #ELLS, or #ELLL to controllers on POWER Servers. Straight cables (such as #ECE3) are not allowed to directly attach to I/O drawers on POWER Servers.

Two AA cables are always required between a pair of PCIe3 SAS adapters with write cache when just one or two I/O drawers are attached. One AA cable is required if three I/O drawers are attached. If four drawers are attached or if an AA cable fails or is disconnected, then the information it was carrying is then sent over the cables attached to the I/O drawers, sharing their bandwidth. On POWER Servers, AA cables are not used with SAS adapters with no write cache.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the two adapters.

The 6Gb version of this cable is feature #5915. #5915 and #ECE3 can be mixed on the same PCIe3 adapter pair.

  • Attributes provided: For ESS solutions, connection between a SAS controller and one 5174-024 I/O drawer. For POWER Systems, connection between two paired SAS controllers with write cache and Mini-SAS HD connectors.
  • Attributes required: For ESS solutions, a 5147-024 I/O drawer and appropriate controller. For POWER Systems, available connectors on SAS controllers.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECE4) - 4.5M SAS AA12 Active Optical Cable (Adapter to Adapter)

This 4.5 meter SAS cable connects a pair of SAS adapters to each other. This AA cable has two Mini-SAS HD (High Density) connectors which connect the top connectors of two PCIe3 SAS adapters with write cachce such as #EJ0L or #EJ14. The cable provides a high performance path of all the dual controller communication including mirroring the write cache and status awareness of each card. This cable is designed for high speed to support up to 12Gb throughput. Note EJ0L/EJ14 support 6Gb.

Two AA cables are always required between a pair of PCIe3 SAS adapters with write cache when just one or two I/O drawers are attached. One AA cable is required if three I/O drawers are attached. If four drawers are attached or if an AA cable fails or is disconnected, then the information it was carrying is then sent over the cables attached to the I/O drawers, sharing their bandwidth. AA cables are not used with SAS adapters with no write cache.

Multiple cable length feature codes are available. Choose the cable length that best matches the distance between the two adapters.
Note: AOC cables require minimum level of SAS Adapter firmware. Refer to the latest prerequisites at

https://www14.software.ibm.com/webapp/set2/iprt/home
  • Attributes provided: Connection between two SAS adapters with Mini-SAS HD connectors
  • Attributes required: Available connectors on SAS controllers
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJ5) - 4.3m (14-Ft) PDU to Wall 3PH/24A 200-240V Delta-wired Power Cord

This power cord feature ECJ5 contains an amphenol type of connector and only supported on PDUs ECJK or ECJL, and ECJP or ECJQ.

ECJ5 has a 4-pin IEC 60309 style plug, 430P9W. It contains three line conductors and a protective earth, but no neutral. ECJ5 is supported in countries that use a delta electrical distribution. ECJ5 is not supported in China, Hong Kong, and other countries that use a wye electrical distribution.

  • Attributes provided: Power cord
  • Attributes required: PDU features ECJK or ECJL, and ECJP or ECJQ.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJ6) - 4.3m (14-Ft) PDU to Wall 3PH/40A 200-240V Power Cord

This power cord goes from the chassis to a wall-type outlet. The line cord has a 200-240V, CS8365 50A Plug (de-rated to 40A) and Amphenol inlet compatible with PDU FCs ECJL and ECJQ. The following countries/regions use the #ECJ6 power cord to power the system: United States and Canada only.

  • Attributes provided: Power cord PDU to Wall
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJ7) - 4.3m (14-Ft) PDU to Wall 3PH/48A 200-240V Delta-wired Power Cord

This power cord feature ECJ7 contains an amphenol type of connector and only supported on PDUs ECJK or ECJL, and ECJP or ECJQ.

ECJ7 has a 4-pin IEC 60309 style plug, 460P9W. It contains three line conductors and a protective earth, but no neutral. ECJ7 is supported in countries that use a delta electrical distribution. ECJ7 is not supported in China, Hong Kong, and other countries that use a wye electrical distribution.

  • Attributes provided: Power cord
  • Attributes required: PDU features ECJK or ECJL, and ECJP or ECJQ.
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJJ) - High Function 9xC19 Single-Phase or Three-Phase Wye PDU plus

This is an intelligent, switched 200-240 volt single-phase or 380-415/220-240 volt three-phase wye AC Power Distribution Unit (PDU) plus with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the nine C19 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Depending on country wiring standards the PDU is single-phase or three-phase wye. Three-phase wye-wired connectors have 5-pins and use three line conductors, a neutral, and a protective earth. The input is 380-415 volt line-to-line and the output is 220-240 volt line-to-neutral for three-phase wye PDUs.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features #6489, #6491, #6492, #6653, #6654, #6655, #6656, #6657, #6658, #6667, #ELC1 or #ELC2.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

There are also three C13 receptacles on the rear of the PDU positioned toward the middle of the rack. These are generally not easily accessed and therefore IBM does not generally recommend their use.

#ECJG and #ECJJ are identical PDUs. Up to one lower price #ECJG can be ordered with a new 7965-S42 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #EPTJ PDU.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Nine C19 PDU plus - switched, power monitoring
  • Attributes required: PDU wall line cord and space in 19-inch rack
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJL) - High Function 9xC19 PDU plus 3-Phase Delta

This is an intelligent, switched 200-240 volt 3-phase delta AC Power Distribution Unit (PDU) plus with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the nine C19 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Three-phase delta-wired connectors have 4-pins and use three line conductors and a protective earth. The input is 200-240 volt line-to-line and the output is 200-240 volt line-to-line for three-phase delta PDUs.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One wall line cord is also ordered separately and attaches to the Amphenol inlet connector. Supported line cords include features #ECJ5, #ECJ6, and #ECJ7.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

There are also three C13 receptacles on the rear of the PDU positioned toward the middle of the rack. These are generally not easily accessed and therefore IBM does not generally recommend their use.

#ECJK and #ECJL are identical PDUs. Up to one lower price #ECJK can be ordered with a new 7014-T42/T00 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #EPTL PDU.

Not supported in China, Hong Kong, and other countries that use a wye electrical distribution.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Nine C19 PDU plus - switched, power monitoring
  • Attributes required: space in rack, 3-phase 208V AC delta electrical service
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJN) - High Function 12xC13 Single-Phase or Three-Phase Wye PDU plus

This is an intelligent, switched 200-240 volt single-phase or 380-415/220-240 volt three-phase wye AC Power Distribution Unit (PDU) plus with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the twelve C13 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Depending on country wiring standards the PDU is single-phase or three-phase wye. Three-phase wye-wired connectors have 5-pins and use three line conductors, a neutral, and a protective earth. The input is 380-415 volt line-to-line and the output is 220-240 volt line-to- neutral for three-phase wye PDUs.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C14 plug connect to C13 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features #6489, #6491, #6492, #6653, #6654, #6655, #6656, #6657, #6658, #6667, #ELC1 or #ELC2.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

Feature #ECJM and #ECJN are identical PDUs. Up to one lower price #ECJM can be ordered with a new 7014-T42/T00 rack in place of a no- charge #9188 PDU.

For comparison, this is most similar to the earlier generation #EPTN PDU.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Twelve C13 PDU plus - switched, power monitoring
  • Attributes required: PDU wall line cord and space in 19-inch rack
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECJQ) - High Function 12xC13 PDU plus 3-Phase Delta

This is an intelligent, switched 200-240 volt 3-phase delta AC Power Distribution Unit (PDU) plus with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the twelve C13 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Three-phase delta-wired connectors have 4-pins and use three line conductors and a protective earth. The input is 200-240 volt line-to-line and the output is 200-240 volt line-to-line for three-phase delta PDUs.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One wall line cord is also ordered separately and attaches to the Amphenol inlet connector. Supported line cords include features #ECJ5, #ECJ6, and #ECJ7.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

#ECJP and #ECJQ are identical PDUs. Up to one lower price #ECJP can be ordered with a new 7965-S42 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #EPTP PDU.

Not supported in China, Hong Kong, and other countries that use a wye electrical distribution.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Twelve C13 PDU plus - switched, power monitoring
  • Attributes required: space in rack, 3-phase 208V AC delta electrical service
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ECSM) - Custom Service Specify, Mexico

Having #ECSM on the order, will cause the order to be routed to Mexico and the machine to be internally routed to the CSC build area.

  • Attributes provided: Customization
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#ECSP) - Custom Service Specify, Poughkeepsie, USA

Having #ECSP on the order, will cause the order to be routed to Poughkeepsie, USA and the machine to be internally routed to the CSC build area.

  • Attributes provided: Customization
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#ECW0) - Optical Wrap Plug

A wrap plug is a small connector designed to perform a diagnostic test called a loopback test. This wrap plug is inserted into a SR optical port on a PCIe Fibre Channel adapter or a SR or LR optical port on a PCIe Ethernet adapter

This is a multi-mode LC fiber optic wrap plug with an inside/ outside optics diameter of 50/125. Its IBM part number as of early 2016 is 12R9314. An earlier equivalent function IBM part number which is no longer shipped is 11P3847.

It is strongly recommended that Fibre Channel adapters (HBAs) fill any empty adapter ports with a wrap plug. There is no technical issue leaving a port empty. However, filling all ports with a cable to a device/switch or with a wrap plug can speed the booting/IPLing of a partition and can avoid error messages uselessly pointing to a planned empty port.

There is no technical issue leaving an Ethernet port empty. Whether an Ethernet port is empty or contains a wrap plug should not impact boot/IPL time or impact empty-port messages.

  • Attributes provided: Wrap plug
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EHB1) - 1x HW Subscription Increment

This feature allows MES orders and create order for customer usage.

  • Attributes provided: None
  • Attributes required: RPQ 8A2544
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EHB2) - 10x HW Subscription Increment

This feature allows MES orders and create order for customer usage.

  • Attributes provided: None
  • Attributes required: RPQ 8A2544
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EHB3) - 100x HW Subscription Increment

This feature allows MES orders and create order for customer usage.

  • Attributes provided: None
  • Attributes required: RPQ 8A2544
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EHC8) - Solution Edition for Healthcare typical 2.95 to 3.9, 24-core processor module

Solution Edition for Healthcare 2.95 to 3.9 GHZ, 96-CORE Processor Hundred and twenty-four cores 2.95 to 3.9 GHz Power10 processor planar containing four twenty-four -core processor DCMs for the Power E1050 Solution Edition for Healthcare.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required:
    • Linux - supported
    • AIX - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EHCA) - Processor Activation for Healthcare Solution (#EHC8)

1 core Processor Activation for Healthcare Solution Edition (#EHC8)

  • Attributes provided: 1-core Processor Activation for #EHC8
  • Attributes required: Healthcare Solution Edition
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required:
    • See feature #EHC8 to find the supported OS levels .
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EHCB) - 512GB Base Memory activation for MRX #EHC8

512GB Memory Activation for Healthcare Solution Edition (#EHC8)

  • Attributes provided: 512GB Memory activation for #EHC8
  • Attributes required: Healthcare Solution Edition
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EHKV) - SAP HANA TRACKING FEATURE

SAP HANA tracking feature that defines manufacturing routing.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EHR2) - Boot Drive / Load Source in EXP24SX Specify (in #ESLS or #ELLS)

Indicates that boot drive or load source (disks or SSDs) are placed in an EXP24SX SAS Storage Enclosure

  • Attributes provided: Boot drive / load source location specify
  • Attributes required: Available SAS bay and supported disk/SSD
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: N/A
  • Return parts MES: No
(#EHS2) - SSD Placement Indicator - #ESLS/#ELLS

This is an IBM internal automatic generated SSD specify indicator for placement and it is not selectable.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJ0J) - PCIe3 RAID SAS Adapter Quad-port 6Gb x8

The PCIe3 RAID SAS Adapter is a high performance SSD/HDD controller using PCIe Gen3 x8 technology. The adapter does not have write cache and thus pairing with another PCIe3 RAID SAS Adapter (#EJ0J or #EJ0M) is optional. Pairing can provide controller redundancy and enhance performance. There are no batteries in the adapter to maintain.

The adapter provides four Mini-SAS HD (high density) narrow connectors for the attachment of SAS drives located in the EXP24S or EXP24SX storage enclosures or #5802/5803/EL36 12X PCIe I/ O drawers. X, YO or AT SAS cables with HD narrow connectors are used to attach to these drawers. A max of 4 EXP24S/EXP24SX can be attached. A maximum of 48 SSD can be attached and a maximum of 96 HDD can be attached per adapter or per adapter pair.

The adapter provides RAID 0, RAID 5, RAID 6 and RAID 10 for AIX and Linux and VIOS. The adapter provides RAID 5 and RAID 6 for all levels of IBM i and also provides RAID 10 for later levels of IBM i. IBM i provides both OS mirroring and data spreading. AIX/Linux/VIOS provide OS mirroring (LVM).

Features #EJ0J and #EJ0M are electronically identical with the same CCIN of 57B4. #EJ0J has a full-high tailstock bracket and air baffle. #EJ0M has a low profile tailstock bracket. #EJ10/#EJ11 are identical with #EJ0J/#EJ0M, but have different feature codes to identify their use as tape/DVD controllers to IBM configurator tools instead of disk/SSD controllers.

Both 5xx and 4k byte sector HDD/SSD are supported for Power9/Power10 servers. 5xx byte sector HDD/SSD are supported for earlier generation servers. 5xx and 4k drives cannot be mixed in the same array.

Limitations:

  • HDD/SSD workloads which are performance sensitive to WRITES should use the #EJ14 or #EJ0L controller which provides write cache.
  • HDD and SSD cannot be mixed on the same SAS port, but can be mixed on the same adapter.
  • #5886 3.5-inch SAS Storage Drawer is not supported.
  • 177GB SSD are not supported.
  • Running SAS bays for both a #5887 EXP24S I/O drawer and a 12X-attached #5802/5803 I/O drawer on the same adapter or adapter pair is not supported. Note mixing EXP24S or EXP24SX is supported.
  • If controlling drives in a #5802/5803/EL36 as a single controller, the #EJ0J must be located in that #5802/5803/EL36. If controlling drives in a #5802/5803/EL36 as a pair of controllers, at least one of the SAS adapter pairs must be located in that #5802/ 5803/EL36.
  • Tape/DVD cannot be mixed with disk/SSD on the same adapter.
  • Attributes provided: full high PCIe3 four port x8 SAS RAID adapter with no write cache and optional pairing
  • Attributes required: One PCIe slot per adapter and Mini-SAS HD narrow connector SAS cables such as #ECBJ-ECBL, #ECBT-ECBV, #ECCO-ECC4 or 12Gb cables such as #ECDJ, ECDT or #ECDU.
  • Minimum required: 0
  • Maximum allowed: 33 (Initial order maximum: 33)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EJ0L) - PCIe3 12GB Cache RAID SAS Adapter Quad-port 6Gb x8

The PCIe3 12GB Cache RAID SAS Adapter provides high performance HDD and/or SSD controller function using PCIe Gen3 technology. A pair of adapters are required to provide mirrored write cache data and adapter redundancy. Integrated flash memory provides protection of the write cache without batteries in case of power failure. Effectively up to 12GB of write cache is provided using compression of 4 GB of physical cache.

The adapter provides four Mini-SAS HD (high density) narrow connectors for the attachment of SAS drives located in the SAS EXP24S or EXP24SX storage enclosures or#5802/5803/EL36 12X PCIe I/O drawers. X, YO or AT SAS cables with HD narrow connectors are used to attach to these drawers. A max of 4 EXP24S/ EXP24SX can be attached with a maximum of 96 HDD or a maximum of 48 SSD. Two AA SAS cable with HD narrow connectors are attached to the #EJ0L pair to communicate status and cache content information and are required unless three or four ports are being used to attach HDD/SSD.

The #EJ0L provides RAID 0, RAID 5, RAID 6 and RAID 10 for AIX and Linux and VIOS. The adapter provides RAID 5 and RAID 6 for all levels of IBM i and also provides RAID 10 for later levels of IBM i. IBM i provides both OS mirroring and data spreading. AIX/Linux/VIOS provide OS mirroring (LVM). This adapter can also support the Easy Tier function (RAID 52T, 62T or 102T) for AIX and Linux. The adapter's CCIN is 57CE.

Both 5xx and 4k byte sector HDD/SSD are supported for POWER8 servers. 5xx byte sector HDD/SSD are supported for earlier generation servers. 5xx and 4k drives cannot be mixed in the same array.

Limitations:

  • HDD and SSD cannot be mixed on the same SAS port, but can be mixed on the same adapter.
  • #5886 3.5-inch SAS I/O Drawer is not supported.
  • 177GB SSD are not supported.
  • Running SAS bays for both a #5887 EXP24S I/O drawer and a 12X-attached #5802/5803 I/O drawer on the same adapter pair is not supported. Note: Mixing EXP24S or EXP24SX is supported.
  • If controlling drives in a #5802/5803/EL36 at least one of he #EJ0L pairs must be located in that #5802/5803/EL36
  • Attributes provided: Full high PCIe3 four port x8 adapter with up to 12GB write cache
  • Attributes required: One PCIe slot per adapter and Mini-SAS HD narrow connector SAS cables such as #ECBJ-ECBL, #ECBT-ECBV, #ECCO-ECC4 or 12Gb cables such as ECDT or #ECDU.
  • Minimum required: 0
  • Maximum allowed: 33 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EJ0Q) - Storage Backplane with Zero DASD 8 SAS 2.5" HDD/SDD Controllers
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJ10) - PCIe3 SAS Tape/DVD Adapter Quad-port 6Gb x8

The PCIe3 SAS Adapter is a high performance SAS tape controller using PCIe Gen3 x8 technology. The adapter supports external SAS tape drives such as the LTO-5, LTO-6, LTO-7, and LTO-8 found in the IBM 7226-1U3 Multimedia drawers, or tape units such as the TS2250, TS2260, TS2270, and TS2280 single External Tape Drive, TS2900, TS3100, TS3200, and TS3310. Other removable media devices supported include IBM SAS/SATA DVD RAM drive features available on the IBM 7226-1U3 Storage Enclosure. The adapter provides four Mini-SAS HD (high density) connectors to which AE1 SAS cables such as #ECBY and/ or YE1 SAS Cables such as #ECBZ with HD narrow connectors can be attached. A max of 4 tape drives per adapter can be attached using four AE1 cables. A max of 8 tape drives can be attached using four YE1 cables.#EJ10 (full high) and #EJ11 (low profile) are electronically the same adapter with the same 57B4 CCIN, but differ in that their tailstocks fit different size PCIe slots.#EJ0J and #EJ10 are the same adapter with the same 57B4 CCIN, but have different feature code numbers to indicate different usage to IBM configurator tools. #EJ10 runs SAS LTO-5 or later tape drives and DVD. Support of both tape/DVD and HDD/SSD on the same adapter is not supported.

Note: The original #EJ0X adapter does not support DVD but also has the same CCIN.

Note: Adapter uses a Mini-SAS HD narrow connector and AE1 #ECBZ or YE1 #ECBY SAS cable.

Limitation: LTO-4 or earlier drives are not supported.

  • Attributes provided: full high PCIe3 four port x8 SAS adapter
  • Attributes required: One PCIe slot per adapter
  • Minimum required: 0
  • Maximum allowed: 33 (Initial order maximum: 128)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Refer to the Software requirements section for specific O/S levels supported.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#EJ14) - PCIe3 12GB Cache RAID PLUS SAS Adapter Quad-port 6Gb x8

The PCIe3 12GB Cache RAID PLUS SAS Adapter provides high performance HDD and/or SSD controller function using PCIe Gen3 technology. A pair of #EJ14 adapters are required to provide mirrored write cache data and adapter redundancy. Integrated flash memory provides protection of the write cache without batteries in case of power failure. Effectively up to 12GB of write cache is provided using compression of 4 GB of physical cache. The #EJ14 provides four Mini-SAS HD (high density) narrow connectors for the attachment of SAS drives located in the SAS EXP24S or EXP24SX storage enclosures. X, YO or AT SAS cables with HD narrow connectors are used to attach to these drawers. A max of 4 EXP24S can be attached with a maximum of 96 HDD or a maximum of 72 SSD per pair of #EJ14. If more than 48 SSD are attached, no HDD can be attached. A mix of EXP24S or EXP24SX is supported on the same adapter pair. Two AA SAS cable with HD narrow connectors are attached to the #EJ14 pair to communicate status and cache content information and are required unless three or four ports are being used to attach HDD/SSD. Feature #EJ14 provides RAID 0, RAID 5, RAID 6, and RAID 10, RAID 5T2, RAID 6T2, and RAID 10T2 for AIX and Linux and VIOS. Two tier arrays (5T2, 6T2 and 10T2) combine both HDD and SSD into a single array with Easy Tier functionality. AIX/Linux/VIOScan also provide OS mirroring (LVM). On systems that support IBM i, the adapter provides RAID 5 and RAID 6 for IBM i. RAID 10 is supported by IBM i 7.2. IBM i provides both OS mirroring and data spreading. This adapter is very similar to the#EJ0L SAS adapter, but #EJ14 uses a second CPU chip in the card to provide more IOPS capacity and can attach more SSD. The #EJ14 adapter's CCIN is 57B1. Both 5xx and 4k byte sector HDD/SSD are supported. 5xx and 4k drives cannot be mixed in the same array. Limitations:

  • Not supported on POWER7/POWER7+ servers.
  • HDD and SSD cannot be mixed on the same SAS port, but can be mixed on the same adapter.
  • Attributes provided: Full high PCIe3 four port x8 adapter with up to 12 GB write cache
  • Attributes required: One PCIe slot per adapter and Mini-SAS HD narrow connector SAS cables such as #ECBJ-ECBL, #ECBT-ECBV, #ECCO-ECC4 or 12Gb cables such as ECDT or #ECDU.
  • Minimum required: 0
  • Maximum allowed: 33 (Initial order maximum: 33)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EJ2A) - PCIe3 x16 to CXP Converter Adapter (support AOC)

PCIe3 x16 adapter provides two optical CXP ports for the attachment of two active optical cables (AOC). One adapter supports the attachment of one PCIe3 module in a PCIe Gen3 I/O Expansion Drawer.

  • Attributes provided: PCIe3 adapter with two CXP ports to attach two active optical cables
  • Attributes required: PCIe3 x16 slot in system unit plus a pair of active optical cables (one optical pair feature such as #ECCS, #ECCX, or #ECCY)
  • Minimum required: 0
  • Maximum allowed: 8 (Initial order maximum: 8)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJ32) - PCIe3 Crypto Coprocessor no BSC 4767

Secure-key adapter provides both cryptographic coprocessor and cryptographic accelerator functions in a single PCIe card. The adapter is well suited to applications requiring high-speed, security- sensitive, RSA acceleration, cryptographic operations for data encryption and digital signing, secure management, and use of cryptographic keys, or custom cryptographic applications. It provides secure storage of cryptographic keys in a tamper-resistant hardware security module designed to meet FIPS 140-2 level 4 security requirements. The adapter is a PCIe Gen 3 x4 full height - short card. The adapter runs in dedicated mode only (no PowerVM virtualization).

#EJ32 and #EJ33 are both feature codes representing the same physical card with the same CCIN of 4767. Different feature codes are used to indicate if a blind swap cassette is used and its type. #EJ32 indicates no blind swap cassette. #EJ33 indicates a Gen 3 blind swap cassette.

IBM PCIe Cryptographic Coprocessor adapter highlights

  • Integrated Dual processors that operate in parallel for higher reliability, often 2x performance improvement over prior generation crypto cards
  • Uses newer level Power Processor (PPC) processor than previous generation cards
  • Supports IBM Common Cryptographic Architecture (CCA 5.3) and PKCS#11 standand
  • Ability to configure adapter as coprocessor or accelerator
  • Support for smart card applications using Europay, MasterCard and Visa
  • Cryptographic key generation and random number generation
  • PIN processing - generation, verification, translation
  • Encrypt/Dectrypt using AES and DES keys

Please refer to the following URL for the latest firmware and software updates http://www-03.ibm.com/security/cryptocards/

  • Attributes provided: Cryptographic Coprocessor and Accelerator Functions
  • Attributes required: One full-high PCIe Gen3 slot which doesn't use a blind swap cassette
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Linux software support can be downloaded from the following location: http://www-03.ibm.com/security/cryptocards/pciecc2/or dersoftware.shtml

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EJ33) - PCIe3 Crypto Coprocessor BSC-Gen3 4767

Secure-key adapter provides both cryptographic coprocessor and cryptographic accelerator functions in a single PCIe card. The adapter is well suited to applications requiring high-speed, security- sensitive, RSA acceleration, cryptographic operations for data encryption and digital signing, secure management, and use of cryptographic keys, or custom cryptographic applications. It provides secure storage of cryptographic keys in a tamper-resistant hardware security module designed to meet FIPS 140-2 level 4 security requirements. The adapter is a PCIe Gen 3 x4 full height - short card. The adapter runs in dedicated mode only (no PowerVM virtualization).

#EJ32 and #EJ33 are both feature codes representing the same physical card with the same CCIN of 4767. Different feature codes are used to indicate if a blind swap cassette is used and its type. #EJ32 indicates no blind swap cassette. #EJ33 indicates a Gen 3 blind swap cassette.

IBM PCIe Cryptographic Coprocessor adapter highlights

  • Integrated Dual processors that operate in parallel for higher reliability, often 2x performance improvement over prior generation crypto cards
  • Uses newer level Power Processor (PPC) processor than previous generation cards
  • Supports IBM Common Cryptographic Architecture (CCA 5.3) and PKCS#11 standand
  • Ability to configure adapter as coprocessor or accelerator
  • Support for smart card applications using Europay, MasterCard and Visa
  • Cryptographic key generation and random number generation
  • PIN processing - generation, verification, translation
  • Encrypt/Dectrypt using AES and DES keys

Linux software support can be downloaded from the following location: http://www-03.ibm.com/security/cryptocards/pciecc2/or dersoftware.shtml

Please refer to the following URL for the latest firmware and software updates http://www-03.ibm.com/security/cryptocards/

  • Attributes provided: Cryptographic Coprocessor and Accelerator Functions
  • Attributes required: One full-high PCIe Gen3 slot which uses a blind swap cassette
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the following URL for Linux device driver downloads and supported Linux versions: http:// www-03.ibm.com/security/cryptocards

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EJ35) - PCIe3 Crypto Coprocessor no BSC 4769

The 4769 PCIe Cryptographic Coprocessor has a PCIe local-bus- compatible interface. The coprocessor holds a security-enabled subsystem module and batteries for backup power. The hardened encapsulated subsystem contains two sets of two 32-bit PowerPC 476FP reduced instruction set computer (RISC) processors running in lockstep with cross-checking to detect soft errors in the hardware. It also contains a separate service processor used to manage self-test and firmware updates; RAM; flash memory and battery-powered memory; secure time-of-day; cryptographic quality random number generator; AES; DES; Triple DES; HMAC; CMAC; MD5; multiple SHA hashing methods; modular- exponentiation hardware, such as RSA and ECC; and full-duplex direct memory access (DMA) communications.

A security-enabled code-loading arrangement allows control program and application program loading and refreshes after coprocessor installation in your server. IBM offers an embedded subsystem control program and a cryptographic application programming interface (API) that implements the IBM CCA.

The IBM Common Cryptographic Architecture Support Program can be accessed from the internet at no charge to the user. See the IBM CCA Basic Services Reference and Guide, which can be found at the IBM Cryptocards Library for a full explanation of the CCA API https:// www.ibm.com/security/cryptocards/pciecc4/library.

For details on future updates to the versions of operating systems that are supported by the 4769 PCIe Cryptographic Coprocessor, see the IBM Cryptocards website https://www.ibm.com/security/cryptocards.

Feature #EJ35 and #EJ37 are both feature codes representing the same physical card with the same CCIN of C0AF. Different feature codes are used to indicate if a blind swap cassette is used and its type. #EJ35 indicates no blind swap cassette. #EJ37 indicates a Gen 3 blind swap cassette.

The 4769 PCIe Cryptographic Coprocessor is designed to deliver the following functions:

  • X.509 certificate services support
  • ANSI X9 TR34-2019 key exchange services that exploit the public key infrastructure (PKI)
  • ECDSA secp256k1
  • CRYSTALS-Dilithium, a quantum-safe algorithm for digital signature generation and verification
  • Rivest-Shamir-Adleman (RSA) algorithm for digital signature generation and verification with keys up to 4096 bits in length
  • High-throughput Secure Hash Algorithm (SHA), MD5 message digest algorithm, Hash-Based Message Authentication Code (HMAC), Cipher-based Message Authentication Code (CMAC), Data Encryption Standard (DES), Triple Data Encryption Standard (Triple DES), and Advanced Encryption Standard (AES)-based encryption for data integrity assurance and confidentiality, including AES Key Wrap (AESKW) that conforms to ANSI X9.102
  • Elliptic-curve cryptography (ECC) for digital signature and key agreement
  • Support for smart card applications and personal identification number (PIN) processing
  • Secure time-of-day
  • Visa Data Secure Platform (DSP) point-to-point encryption (P2PE) with standard Visa format-preserving encryption (FPE) and format- preserving, Feistel-based Format Preserving Encryption (FF1, FF2, FF2.1). Format Preserving Counter Mode (FPCM) as defined in x9.24 Part 2
  • Attributes provided: Cryptographic Coprocessor and Accelerator Functions
  • Attributes required: One full-high PCIe Gen3 slot which doesn't use a blind swap cassette
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Linux software support can be downloaded from the following location: http://www-03.ibm.com/security/cryptocards/pciecc2/or dersoftware.shtml

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJ37) - PCIe3 Crypto Coprocessor BSC-Gen3 4769

The 4769 PCIe Cryptographic Coprocessor has a PCIe local-bus- compatible interface. The coprocessor holds a security-enabled subsystem module and batteries for backup power. The hardened encapsulated subsystem contains two sets of two 32-bit PowerPC 476FP reduced instruction set computer (RISC) processors running in lockstep with cross-checking to detect soft errors in the hardware. It also contains a separate service processor used to manage self-test and firmware updates; RAM; flash memory and battery-powered memory; secure time-of-day; cryptographic quality random number generator; AES; DES; Triple DES; HMAC; CMAC; MD5; multiple SHA hashing methods; modular- exponentiation hardware, such as RSA and ECC; and full-duplex direct memory access (DMA) communications.

A security-enabled code-loading arrangement allows control program and application program loading and refreshes after coprocessor installation in your server. IBM offers an embedded subsystem control program and a cryptographic application programming interface (API) that implements the IBM CCA.

The IBM Common Cryptographic Architecture Support Program can be accessed from the internet at no charge to the user. See the IBM CCA Basic Services Reference and Guide, which can be found at the IBM Cryptocards Library for a full explanation of the CCA API.

For details on future updates to the versions of operating systems that are supported by the 4769 PCIe Cryptographic Coprocessor, see the IBM Cryptocards website https://www.ibm.com/security/cryptocards.

Feature #EJ35 and #EJ37 are both feature codes representing the same physical card with the same CCIN of C0AF. Different feature codes are used to indicate if a blind swap cassette is used and its type. #EJ35 indicates no blind swap cassette. #EJ37 indicates a Gen 3 blind swap cassette.

The 4769 PCIe Cryptographic Coprocessor is designed to deliver the following functions:

  • X.509 certificate services support
  • ANSI X9 TR34-2019 key exchange services that exploit the public key infrastructure (PKI)
  • ECDSA secp256k1
  • CRYSTALS-Dilithium, a quantum-safe algorithm for digital signature generation and verification
  • Rivest-Shamir-Adleman (RSA) algorithm for digital signature generation and verification with keys up to 4096 bits in length
  • High-throughput Secure Hash Algorithm (SHA), MD5 message digest algorithm, Hash-Based Message Authentication Code (HMAC), Cipher-based Message Authentication Code (CMAC), Data Encryption Standard (DES), Triple Data Encryption Standard (Triple DES), and Advanced Encryption Standard (AES)-based encryption for data integrity assurance and confidentiality, including AES Key Wrap (AESKW) that conforms to ANSI X9.102
  • Elliptic-curve cryptography (ECC) for digital signature and key agreement
  • Support for smart card applications and personal identification number (PIN) processing
  • Secure time-of-day
  • Visa Data Secure Platform (DSP) point-to-point encryption (P2PE) with standard Visa format-preserving encryption (FPE) and format- preserving, Feistel-based Format Preserving Encryption (FF1, FF2, FF2.1). Format Preserving Counter Mode (FPCM) as defined in x9.24 Part 2
  • Attributes provided: Cryptographic Coprocessor and Accelerator Functions
  • Attributes required: One full-high PCIe Gen3 slot which uses a blind swap cassette
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 6)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Linux software support can be downloaded from the following location: http://www-03.ibm.com/security/cryptocards/pciecc2/or dersoftware.shtml

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJRL) - Non-paired Indicator EJ14 PCIe SAS RAID+ Adapter

Feature EJRL must be added for every instance of a non-paired SAS RAID adapter #EJ14. It identifies a specific high availability configuration supported by AIX or Linux which has one #EJ14 on one system and the paired #EJ14 located on a second system. IBM i does not support paired adapter on different servers.

SAS RAID adapter firmware disables write cache until a second SAS RAID adapter is recognized as its pair. This specify indicates the pairing will not be on just one server.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: Only one #EJ14 on a server and its pair on a different server.
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EJRU) - Non-paired Indicator EJ0L PCIe SAS RAID Adapter

(No Longer Available as of November 08, 2022)

Feature EJRU must be added for every instance of a non-paired SAS RAID adapter #EJ0L. It identifies a specific high availability configuration supported by AIX or Linux which has one #EJ0L on one system and the paired #EJ0L located on a second system. IBM i does not support paired adapter on different servers.

  • Attributes provided: SAS RAID adapter firmware disables write cache until a second SAS RAID adapter is recognized.
  • Attributes required: Every #EJ0L requires a 6Gb/s SAS RAID adapter (#EJ0L) on both this server and on another server that will pair up the SAS RAID adapter and enable the onboard caches to function.
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.

  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EJW1) - Specify Mode-1 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 1 (one group of 24 drive bays). It will be connected to one #EJ0J/#EL59/#EJ0M/ #EL36 PCIe3 RAID SAS adapter.

One YO12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECDT, #ECDU, #ECDV or #ECDW.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW2) - Specify Mode-1 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 1 (one group of 24 drive bays). It will be connected to two (one pair) #EJ0J/ #EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two YO12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECDT, #ECDU, #ECDV or #ECDW.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW3) - Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to two (one pair) #EJ0J/ #EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two X12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW4) - Specify Mode-2 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to four (two pair) #EJ0J/ #EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two X12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW5) - Specify Mode-4 & (4)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 4 (four groups of 6 drive bays). It will be connected to four (unpaired) #EJ0J/#EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two X12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW6) - Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to one #EJ0J/#EL59/#EJ0M/ #EL36 PCIe3 RAID SAS adapter.

Two YO12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECDT, #ECDU, #ECDV or #ECDW.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJW7) - Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (2)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to two (nonpaired) #EJ0J/ #EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two YO12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBT, #ECBU, #ECBV or #ECBW.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWA) - Specify Mode-2 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to one #EJ0J/#EL59/#EJ0M/ #EL36 PCIe3 RAID SAS adapter.

One YO12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBT, #ECBU, #ECBV or #ECBW.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW7.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWB) - Specify Mode-2 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to two (one pair) #EJ0J/ #EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

One X12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or#ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW4.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWC) - Specify Mode-4 & (1)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 4 (four groups of 6 drive bays). It will be connected to one #EJ0J/#EL59/ #EJ0M/#EL36 PCIe3 RAID SAS adapter.

One X12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL. One leg of the X12 cable is left unattached at the adapter end.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW5, #EJWD or #EJWE. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing that in this configuration one EXP24SX Drawer (#ESLS/ELLS) should be configured in Mode 4 and be using one PCIe3 RAID SAS adapter (#EJ0J/EL59/EJ0M/ EL3B) and one X12 SAS Cables. One leg of the X cable is left unattached at the adapter end.

This indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the EXP24SX. If adapters/ cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW5, #EJWD or #EJWE.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWD) - Specify Mode-4 & (2)EJ0J/EJ0M/EL3B/EL59 & (1)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 4 (four groups of 6 drive bays). It will be connected to Two (nonpaired) #EJ0J/#EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

One X12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW5 or #EJWE.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWE) - Specify Mode-4 & (3)EJ0J/EJ0M/EL3B/EL59 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 4 (four groups of 6 drive bays). It will be connected to Three (nonpaired) #EJ0J/#EL59/#EJ0M/#EL36 PCIe3 RAID SAS adapters.

Two X12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL. One leg of one of the two X12 cables is left unattached at the adapter end.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJW5.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #ESLS or #ELLS to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWF) - Specify Mode-1 & (2)EJ14 & (2)YO12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 1 (one group of 24 drive bays). It will be connected to two #EJ14 PCIe3 RAID SAS adapters.

Two YO12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECDT, #ECDU, #ECDV or #ECDW.

One specify feature should be ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #EJ14 and #ESLS or #ESLL to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWG) - Specify Mode-2 & (2)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to two #EJ14 PCIe3 RAID SAS adapters.

Two X12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #EJ14 and #ESLS or #ESLL to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWH) - Specify Mode-2 & (2)EJ14 & (1)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to two #EJ14 PCIe3 RAID SAS adapters.

One X12 cable connects the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or#ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This indicates a "partial" configuration where there are not enough adapters/cables to run all the SAS bays in the SAS Storage Enclosure. If adapters/cables are MES added later to support the rest of the SAS bays, then this specify code should be removed and the appropriate specify feature added to help IBM config tools understand the expanded usage, probably specify feature #EJWG.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #EJ14 and #ESLS or #ESLL to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EJWJ) - Specify Mode-2 & (4)EJ14 & (2)X12 for EXP24SX #ESLS/ELLS

Feature indicates that EXP24SX SAS Storage Enclosure (#ESLS or #ELLS) will be configured by IBM Manufacturing in Mode 2 (two groups of 12 drive bays). It will be connected to four #EJ14 PCIe3 RAID SAS adapters.

Two X12 cables connect the SAS Storage Enclosure to the SAS adapter ports. Use the cable length appropriate to the configuration and select from features such as #ECBJ, #ECBK or #ECBL.

One specify feature should ordered with each SAS Storage Enclosure. This feature does not order or ship any hardware, but indicates to IBM config tools and to IBM Manufacturing the combination of enclosure mode, SAS adapter and SAS cable type which will be used.

This specify feature indicates a full set of adapters plus SAS cables is used for the enclosure. A different specify feature code is used to indicate a "partial" configuration when a subset of adapters and cables are used.

  • Attributes provided: Communicate configuration information to IBM Manufacturing
  • Attributes required: SAS Storage Enclosure, PCIe3 RAID SAS adapter(s) and SAS cable(s) as indicated in description
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: Refer to #EJ14 and #ESLS or #ESLL to find the supported O/S levels.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EKF3) - Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 1.6 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #EKF3 and #EKF4 are physically identical drives with the same CCIN of 5B52. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature EKF3 indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature EKF4 indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 1.6 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EKF5) - Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 3.2 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #EKF5 and #EKF6 are physically identical drives with the same CCIN of 5B51. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature EKF5 indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature EKF6 indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 3.2 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EKF7) - Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 6.4 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #EKF7 and #EKF8 are physically identical drives with the same CCIN of 5B50. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature EKF7 indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature EKF8 indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 6.4 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELBV) - PowerVM for Linux indicator
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELBW) - 1-core Linux Processor Activation for #EPEU
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required:
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELBX) - 1-core Linux Processor Activation for #EPEV
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required:
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELBY) - 1-core Linux Processor Activation for #EPGW
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required:
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELC0) - PDU Access Cord 0.38m

This 0.38 meter (14 inch) cord is used with a vertically mounted PDU (Power Distribution Unit) such as a#ECJJ, #ECJN, #EPTJ, #EPTN, #7188 or #7109 when the PDU is located in a 7965-S42, 7965-94Y, or #ER05 Slim Rack. One end of this power cord connects to the PDU. The other end of this cord connects to the power cord running to the wall outlet or electrical power source. #ELC0 is not supported on ECJL, ECJQ, EPTL or EPTQ PDUs.

One PDU Access Cord is required per vertically mounted PDU. Without a PDU Access Cord, inserting and removing the wall outlet power cord into the PDU can be very difficult in the narrow side pockets of the Slim Rack. A PDU Access Cord is not required for PDUs in wider racks such as the 7014-S42.

  • Attributes provided: Power cord
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#ELC1) - 4.3m (14-Ft) PDU to Wall 24A 200-240V Power Cord North America

This power cord goes from the chassis to a wall-type outlet. The line cord has a 200-240V, IEC309 30A P+N+G Plug (de-rated to 24A) and Souriau inlet compatible with PDU FCs ECJJ and ECJN. The following countries/regions use the #ELC1 power cord to power the system: United States, Canada, Mexico.

  • Attributes provided: Power cord PDU to Wall
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELC2) - 4.3m (14-Ft) PDU to Wall 3PH/24A 415V Power Cord North America

This power cord goes from the chassis to a wall-type outlet. The line cord has a 3-phase wye-wired 415/240V, IEC309 30A 3P+N+G Plug (de-rated to 24A per phase) and Souriau inlet compatible with PDU FCs ECJJ and ECJN. The following countries/regions use the #ELC2 power cord to power the system: United States, Canada, Mexico.

  • Attributes provided: Power Cord PDU to Wall
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELC5) - Power Cable - Drawer to IBM PDU (250V/10A)

This feature permits manufacturing to select the optimum PDU power jumper cord length (2.8M or 4.3M) for rack integration. This feature is mandatory for servers that use power supplies with C14 inlets that are going to be factory integrated with IBM racks (such as with 7014-T00 or T42 racks) that contains C19 PDU types.

Feature is not valid on initial order with non-factory integrated feature 4650. Power jumper cord has C13 on one end (for C14 power supply connector on system unit or I/O drawer) and C20 on the other end (for IBM PDU C19 receptacle). MES orders of FC #ELC5 will ship 4.3m length. If MES customers want 2.8m length should order #6665.

  • Attributes provided: Power jumper cord (2.8m or 4.3m)
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ELG4) - IBM Power Private Cloud Rack for OracleDB Solution Indicator
  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EM75) - 64GB (2 x 32GB) DDR4 Memory Dimm

Provides 64GB (2 x 32GB) running at 3200Mhz 16Gbit DDR4 system memory.

  • Attributes provided: 64GB Memory Dimm
  • Attributes required: Available memory slot
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EM76) - 128GB (2 x 64GB) DDR4 Memory Dimm

Provides 128GB (2 x 64GB) running at 3200Mhz 16Gbit DDR4 system memory.

  • Attributes provided: 128GB Memory Dimm
  • Attributes required: Available memory slot
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EM77) - 256GB (2 x 128GB) DDR4 Memory Dimm

Provides 256GB (2 x 128GB) running at 2666Mhz 16Gbit DDR4 system memory.

  • Attributes provided: 256GB Memory Dimm
  • Attributes required: Available memory slot
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EM7J) - 512GB (2 x 256GB) DDR4 Memory Dimm

Provides 512GB (2 x 256GB) running at 2666Mhz 16Gbit DDR4 system memory.

  • Attributes provided: 512GB Memory Dimm
  • Attributes required: Available memory slot
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EM81) - Active Memory Mirroring

Active Memory Mirroring for Hypervisor is an option which mirrors the main memory used by the firmware. With this option, an uncorrectable error resulting from failure of main memory used by system firmware will not cause a system-wide outage. This option efficiently guards against system-wide outages due to any such uncorrectable error associated with firmware. With this option, uncorrectable errors in data owned by a partition or application will be handled by the existing Special Uncorrectable Error Handling methods in the hardware, firmware and OS.

  • Attributes provided: Enables Main memory mirroring used by system firmware
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: Does not apply
(#EMBM) - Power Active Memory Expansion

Feature number EMBM instructs manufacturing to enable memory expansion on the system.

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:
    • IBM i - not supported
  • Initial Order/MES/Both/Supported: Initial
  • CSU: Yes
  • Return parts MES: No
(#EMCE) - 512 of #EMCP 1GB Memory Activations for MRX

Feature #EMCE provides 512 of #EMCP 1GB Memory Activations for MRX

  • Attributes provided: 512GB Memory Activation, only in the system serial number for which they are purchased.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EMCG) - 512 of #EMCP 1GB Linux Memory Activations for MRX

Feature #EMCG provides 512 of #EMCP 1GB Memory Activations for MRX -Linux only

  • Attributes provided: 512GB Memory Activation for Linux only
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EMCP) - 1GB Memory Activations for MRX

Feature #EMCP provides 1GB Memory Activations for MRX

  • Attributes provided: 1GB Memory Activation, only in the system serial number for which they are purchased.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 16384 (Initial order maximum: 16384)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EMCQ) - 100GB Memory Activations for MRX

Feature #EMCQ provides 100 of #EMCP 1GB Memory Activations for MRX

  • Attributes provided: 100GB Memory Activation, only in the system serial number for which they are purchased.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 163 (Initial order maximum: 163)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EMX0) - PCIe Gen3 I/O Expansion Drawer

This 19-inch, 4U (4 EIA) enclosure provides PCIe Gen3 slots outside of the system unit. It has two module bays. One 6-Slot Fanout Module (#EMXH) can be placed in each module bay. Two 6-slot modules provide a total of 12 PCIe Gen3 slots. Each fanout module is connected to a PCIe3 Optical Cable Adapter located in the system unit over an active optical CXP cable (AOC) pair or CXP copper cable pair.

The PCIe Gen3 I/O Expansion Drawer has two redundant, hotplug power supplies. Each power supply has its own separately ordered power cord. The two power cords plug into a Power supply conduit which connects to the power supply. The single-phase AC power supply is rated at 1030 Watt and can use 100-120V or 200-240V. If using 100-120V, then the maximum is 950 Watt. It's recommended the power supply connect to a PDU in the rack. Power Systems PDUs are designed for 200-240V electrical source.

The drawer has fixed rails which can accommodate racks with depths from 27.5 inches to 30.5 inches.

Limitations:

  • #EMX0 has a cable management bracket located at the rear of the drawer which swings up to provide service access to the PCIe adapters. 2U (2 EIA) of space is required to swing up the bracket. Thus the drawer cannot be placed in the very top 2U of a rack.
  • There is a power cord access consideration with vertically mounted PDUs on the right hand side of the rack when viewed from the rear of the rack. The #EMX0 cable management bracket makes accessing some of the PDU outlets located at the same rack height as the #EMX0 drawer more challenging. Using a horizontally mounted PDU or locating the PDU or #EMX0 at a different vertical location is recommended.
  • Attributes provided: 19-inch 4U (4 EIA) PCIe Gen3 I/O Expansion Drawer
  • Attributes required:
    • For Scale-up servers - One or two PCIe x16 to CXP Converter Card Adapter (#EJ24), one or two PCIe3 fanout modules (#EMXH), one or two Active Optical Cable CXP cable pairs (such as #ECCR or #ECCY), one power supply conduit (such as #EMXA).
    • For Scale-out servers - see requirements in Rack-integrated system with I/O expansion drawer section.
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to the Software requirements section for specific O/S levels supported.

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    • When the operating system is Linux, PowerVM is required for support of the I/O Expansion Drawer.
    • Assignment to the VIOS supported
(#EMXA) - AC Power Supply Conduit for PCIe3 Expansion Drawer

Provides two 320-C14 inlet electrical connections for two separately ordered AC power cords with C13 connector plugs. Conduit provides electrical power connection between two power supplies located in the front of a PCIe Gen3 I/O Expansion Drawer (#EMX0) and two power cords which connect on the rear of the PCIe Gen3 I/O Expansion Drawer.

  • Attributes provided: Two AC Power Supply connections
  • Attributes required: PCIe Gen3 I/O Expansion Drawer and two AC power cords
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EMXH) - PCIe3 6-Slot Fanout Module for PCIe3 Expansion Drawer

PCIe3 fanout module for PCIe Gen3 I/O Expansion Drawer. Provides six PCIe Gen3 full high, full length slots (two x16 and four x8). The PCIe slots are hot plug.

The module has two CXP ports which are connected two CXP ports on a PCIe Optical Cable Adapter (only allowed to connect to #EJ24 Optical Cable Adapter). A pair of active optical CXP cables (AOC) or a pair of CXP copper cables are used for this connection. The top CXP port of the fanout module is cabled to the top CXP port of the PCIe3 Optical Cable Adapter. The bottom CXP port of the fanout module is cabled to the bottom CXP port of the same PCIe3 Optical Cable Adapter.

Limitations:

  • Mixing of prior PCIe3 fanout modules (#EMXF, #EMXG, #ELMF, #ELMG) with PCIe3 fanout module (feature #EMXH) in the same I/O Expansion Drawer is not allowed
  • For Scale-up servers - PCIe3 Optical Cable Adapters (#EJ24) requires to use Optical Cables (#ECCR, ECCY, or #ECCZ)
  • For Scale-out servers - see requirements in Rack-integrated system with I/O expansion drawer section.
  • Attributes provided: PCIe3 6-slot fanout module for PCIe Gen3 I/O Expansion Drawer
  • Attributes required: Available bay in PCIe Gen3 I/O Expansion Drawer.
  • Minimum required: 0
  • Maximum allowed: 8 (Initial order maximum: 8)
  • OS level required:
    • AIX supported
    • Linux supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    • Assignment to the VIOS supported
(#EN01) - 1m (3.3-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper

1m (3.3-ft) copper active twinax Ethernet cable which supports Ethernet data transfer rates up to 10 Gb/s. The cable has a copper twinax transceiver on each end which is placed in an SFP+ port of an adapter and/or a switch. This cabling option can be a cost effective alternative to optical cable for short reach link high-speed connection.

  • Attributes provided: 10Gb/s copper active twinax Ethernet cable
  • Attributes required: One available SFP+ 10Gb/s Ethernet Port
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EN02) - 3m (9.8-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper

3m (9.8-ft) copper active twinax Ethernet cable which supports Ethernet data transfer rates up to 10 Gb/s. The cable has a copper twinax transceiver on each end which is placed in an SFP+ port of an adapter and/or a switch. This cabling option can be a cost effective alternative to optical cable for short reach link high-speed connection.

  • Attributes provided: 10Gb/s copper active twinax Ethernet cable
  • Attributes required: One available SFP+ 10Gb/s Ethernet Port
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EN03) - 5m (16.4-ft), 10Gb E'Net Cable SFP+ Act Twinax Copper

5m (16.4-ft) copper active twinax Ethernet cable which supports Ethernet data transfer rates up to 10 Gb/s. The cable has a copper twinax transceiver on each end which is placed in an SFP+ port of an adapter and/or a switch. This cabling option can be a cost effective alternative to optical cable for short reach link high-speed connection.

  • Attributes provided: 10Gb/s copper active twinax Ethernet cable
  • Attributes required: One available SFP+ 10Gb/s Ethernet Port
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EN0A) - PCIe3 16Gb 2-port Fibre Channel Adapter

(No Longer Available as of September 13, 2022)

PCIe Gen3 16 Gigabit dual-port Fibre Channel (FC) Adapter is a high-performance 8x short form adapter based on the Emulex LPe16002B PCIe Host Bus Adapter (HBA). The adapter provides two ports of 16Gb Fibre Channel capability using SR optics. Each port can provide up to 16Gb Fibre Channel functions simultaneously. The adapter was initially announced as PCIe Gen2, but upgrades to the adapter firmware and introduction of Power9/Power10 servers have enabled PCIe Gen3.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The ports are SFP+ and include an optical SR transceiver. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 4, 8 and 16 Gbps and will automatically negotiate to the highest speed possible. LEDs on each port provide information on the status and link speed of the port.

The adapter connects to a Fibre Channel switch at 4Gb, 8Gb or 16Gb. It can directly attach to a device without a switch at 16Gb. Attachment without a switch is not supported at 4Gb or 8Gb

N_Port ID Virtualization (NPIV) capability is supported through VIOS.

Feature #EN0A and #EN0B are electronically identical. They differ physically only that EN0A has a tail stock for full high PCIe slots and #EN0B has a tail stock for low profile PCIe slots. CCIN is 577F for both features.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth

The maximum cable lengths at the three different link speeds are:

Cable | 4 Gbps | 8 Gbps | 16 Gbps
------|--------|--------|--------
OM4   | 400m   | 190m   | 125m
OM3   | 380m   | 150m   | 100m
OM2   | 150m   | 50m    | 35m
OM1   | 70m    | 21m    | 15m
  • Attributes provided: Two 16Gb FC ports (with LC connectors)
  • Attributes required: Available PCIe Gen2 or Gen3 slot in supported server
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EN0S) - PCIe2 4-Port (10Gb+1GbE) SR+RJ45 Adapter

PCIe Gen2 x8 short Ethernet adapter supports Ethernet NIC (Network Interface Card) traffic. The adapter provides two 10 Gb SR optical ports and two 1 Gb RJ45 ports in a PCIe 8x short form adapter.

The 10Gb ports are SFP+ and include optical SR transceivers. The ports have LC Duplex type connectors and utilize shortwave laser optics and MMF-850nm fiber cabling. With 62.5 micron OM1, up to 33 meter length fiber cables are supported. With 50 micron OM2, up to 82 meter fiber cable lengths are supported. With 50 micron OM3 or OM4, up to 300 meter fiber cable lengths are supported.

For the 1Gb RJ45 ports, 4-pair CAT-5 Unshielded Twisted Pair (UTP) cable or higher is supported for distances of up to 100 meters. In addition to 1Gb (1000 Mb) networks, 100 Mb networks are also supported, but 10Mb networks are not supported.

#EN0S and #EN0T adapters are electronically identical. They are physically identical except #EN0S has a tail stock for full high PCIe slots and #EN0T has a tail stock for low profile slots. The CCIN is 2CC3 for both features.

Details for the ports include:

  • VIOS NIM and LINUX NETWORK INSTALL are supported.
  • IEEE 802.3ae (10GBASE-SR), IEEE 802.3ab (1000BASE-T GbE), IEEEu 802.3u (100BASE-T), 802.1p priority, 802.1Q VLAN tagging, 802.3x flow control, 802.3ad load-balancing and failover,
  • Link aggregation, IEEE 802.3ad 802.3
  • Multiple MAC addresses/promiscuous mode (for PowerVM/VIOS) per interface
  • Message Signalling Interrupt MSI-X, MSI and support of legacy pin interrupts
  • Ether II and IEEE 802.3 encapsulated frames
  • Jumbo frames up to 9.6 Kbytes
  • TCP checksum offload for IPv4 and IPv6
  • TCP segmentation Offload (TSO) RSS (Receive Side Scaling) support for IPv4, IPv6 and UDP for IPv4 and IPv6
  • UDP checksum offload for IPv4 and IPv6
  • AIX, IBM i, and Linux provide software iSCSI support through the adapter.
  • Attributes provided: Four ports - two 10Gb and two 1Gb E
  • Attributes required: PCIe Gen2 or Gen3 slot - full high
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported
    • Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EN0U) - PCIe2 4-port (10Gb+1GbE) Copper SFP+RJ45 Adapter

PCIe Gen2 x8 short Ethernet adapter supports Ethernet NIC (Network Interface Card) traffic. The adapter provides two 10 Gb twinax copperl ports and two 1 Gb RJ45 ports in a PCIe 8x short form adapter.

The 10Gb ports are SFP+ and do not include a transceiver. Active Copper twinax cables up to 5 meter in length are supported such as provided by feature #EN01, #EN02 or #EN03. A transceiver is included with these cables. Note that SFP+ twinax copper is NOT AS/400 5250 twinax or CX4 or 10 GBase-T. Active cables differ from passive cables.

For the 1Gb RJ45 ports, 4-pair CAT-5 Unshielded Twisted Pair (UTP) cable or higher is supported for distances of up to 100 meters. In addition to 1Gb (1000 Mb) networks, 100 Mb networks are also supported, but 10Mb networks are not supported.

#EN0U and #EN0V adapters are electronically identical. They are physically identical except #EN0U has a tail stock for full high PCIe slots and #EN0V has a tail stock for low profile slots. The CCIN is 2CC3 for both features.

Details for the ports include:

  • AIX NIM and Linux Network Install are supported.
  • IEEE 802.3ae (10 GbE),IEEE 802.3ab (1000BASE-T GbE), 100BASE-T IEEEu, 802.1p priority, 802.1Q VLAN tagging, 802.3x flow control, 802.3ad load-balancing and failover,
  • Link aggregation, IEEE 802.3ad 802.3
  • Multiple MAC addresses/promiscuous mode (for PowerVM/VIOS) per interface
  • Message Signalling Interrupt MSI-X, MSI and support of legacy pin interrupts
  • Ether II and IEEE 802.3 encapsulated frames
  • Jumbo frames up to 9.6 Kbytes
  • TCP checksum offload for IPv4 and IPv6
  • TCP segmentation Offload (TSO) for IPv4 and IPv6
  • UDP checksum offload for IPv4 and IPv6
  • AIX, IBM i and Linux provide software iSCSI support through the adapter.
  • Attributes provided: Four ports - two 10Gb and two 1Gb E
  • Attributes required: PCIe Gen2 or Gen3 slot - full high
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported
    • Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EN0W) - PCIe2 2-port 10/1GbE BaseT RJ45 Adapter

PCIe Gen2 short x8 adapter which provides two 10G-BaseT ports. The ports are RJ45. The ports default to auto negotiate the highest speed either 10Gb (10GBaseT), 1Gb (1000BaseT) or 100Mb (100BaseT) full duplex. Each RJ45 port's configuration is independent of the other. The adapter supports Ethernet NIC (Network Interface Card) traffic.

The RJ45 ports use 4-pair CAT-6A cabling for distances of up to 100 meters or CAT-6 cabling for distances up to 37 meters. CAT5 cabling is not tested and is not supported.

#EN0W and #EN0X are electronically identical with the same CCIN of 2CC4. #EN0W has a full high tail stock and #EN0X has a low profile tail stock.

Details for the ports include:

  • NIM install supported for VIOS, AIX, and Linux
  • IEEE 802.3an (10GBASE-T), IEEE 802.3ab (1000BASE-T GbE), IEEEu (100BASE-T), 802.1p priority, 802.1Q VLAN tagging, 802.3x flow control, 802.3ad load-balancing and failover, Link aggregation, IEEE 802.3ad 802.3
  • Multiple MAC addresses / promiscuous mode (for PowerVM/VIOS) per interface
  • Message Signalling Interrupt (MSI-X, MSI) support of legacy pin interrupts
  • Ether II and IEEE 802.3 encapsulated frames
  • Jumbo frames up to 9.6 Kbytes
  • TCP checksum offload for IPv4 and IPv6
  • TCP segmentation Offload (TSO)
  • RSS (Receive Side Scaling) support for IPv4, IPv6 and UDP
  • UDP checksum offload for IPv4 and IPv6
  • AIX, IBM i, and Linux provide software iSCSI support through the adapter
  • Attributes provided: Two 10G-BaseT ports
  • Attributes required: PCIe Gen2 or Gen3 slot - full high
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 51)
  • OS level required:
    • AIX - supported
    • Linux - supported
    • Refer to the Software Requirements section to find the supported O/S levels for AIX and Linux.
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: VIOS supported
(#EN1A) - PCIe3 32Gb 2-port Fibre Channel Adapter

PCIe Gen3 32 Gigabit dual-port Optical Fibre Channel (FC) Adapter is a high-performance 8x short form adapter based on the Broadcom LPe32000-series PCIe Host Bus Adapter (HBA). The adapter provides two ports of 32Gb Fibre Channel capability using SR optics. Each port can provide up to 32Gb Fibre Channel functions simultaneously.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The ports are SFP+ and include an optical SR transceiver. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 8, 16, and 32Gbps and will automatically negotiate to the highest speed possible.

Feature #EN1A and #EN1B are electronically identical. They differ physically only that EN1A has a tail stock for full high PCIe slots and #EN1B has a short tail stock for low profile PCIe slots.

CCIN is 578F for both features.

Each port has two LED indicators located on the bracket next to each connector. These LEDs communicate boot status and give a visual indication of the operating state. The LEDs have five defined states; solid on, solid off, slow blink, fast blink, and flashing. The slow blink rate is 1Hz, the fast blink is 4Hz, and the flashing refers to an irregular on/off transition that reflects test progress. The operator should observe the LED sequence for several seconds to ensure that the operating state is correctly identified.

Cables:

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 2-port 32Gb Optical FC
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN1C) - PCIe3 16Gb 4-port Fibre Channel Adapter

PCIe Gen3 16 Gigabit quad-port Optical Fibre Channel (FC) Adapter is a high-performance x8 short form PCIe adapter based on the Emulex LPe31004 PCIe Host Bus Adapter (HBA). The adapter provides four ports of 16Gb Fibre Channel capability using SR optics. Each port can provide up to 16Gb Fibre Channel functions simultaneously.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The ports are SFP+ and include an optical SR transceiver. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 4, 8 and 16 Gbps and will automatically negotiate to the highest speed possible.

Feature #EN1C and #EN1D are electronically identical. They differ physically only that EN1C has a tail stock for full high PCIe slots and #EN1D has a tail stock for low profile PCIe slots.

CCIN is 578E for both features.

Each port has two LED indicators located on the bracket next to each connector. These LEDs communicate boot status and give a visual indication of the operating state. The LEDs have five defined states; solid on, solid off, slow blink, fast blink, and flashing. The slow blink rate is 1Hz, the fast blink is 4Hz, and the flashing refers to an irregular on/off transition that reflects test progress. The operator should observe the LED sequence for several seconds to ensure that the operating state is correctly identified.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 4-port 16Gb Optical FC
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN1E) - PCIe3 16Gb 4-port Fibre Channel Adapter

This PCIe Gen3 16 Gigabit quad-port optical fibre channel (FC) adapter is a high-performance x8 short form adapter based on the Marvell QLE2694L PCIe host bus adapter (6.6 inches x 2.371 inches). The adapter provides four ports of 16Gb fibre channel capability using SR optics. Each port can provide up to 3,200MBps bandwidth per port.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The adapter ships with Soldered Small Form Factor (SFF) optical transceivers installed. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 4, 8, and 16Gbps and will automatically negotiate to the highest speed possible. The adapter supports boot on IBM power with fcode.

Feature #EN1E and #EN1F are electronically identical. They differ physically only that the #EN1E has a tail stock for full height PCIe slots and the #EN1F has a short tail stock for low profile PCIe slots.

Each port has two LED indicators located on the bracket next to each connector. These LEDs communicate boot status and give a visual indication of the operating state. The LEDs have five defined states; solid on, solid off, slow blink, fast blink, and flashing. The slow blink rate is 1Hz, the fast blink is 4Hz, and the flashing refers to an irregular on/off transition that reflects test progress. The operator should observe the LED sequence for several seconds to ensure that the operating state is correctly identified.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 4-port 16Gb Optical FC
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN1G) - PCIe3 2-Port 16Gb Fibre Channel Adapter

The PCIe3 x8 dual-port Fibre Channel (16 Gb/s) adapter is a PCI Express (PCIe) generation 3 (Gen3) x8 adapter. This PCIe adapter is based on the Marvell QLE2692 PCIe host bus adapter 15.2 cm x 7 cm (6.6 inches x 2.7 inches). The adapter provides two ports of 16 Gb Fibre Channel capability by using SR optics. Each port can provide up to 3,200 Mbps bandwidth per port. Each port provides single initiator capability over a fiber optic link or with N_Port ID Virtualization (NPIV) it provides multiple initiator capabilities. The ports are SFP+ and include an optical SR transceiver. The ports have LC type connectors and use shortwave laser optics. The adapter operates at link speeds of 4, 8, and 16 Gbps and it automatically negotiates to the highest speed possible. The adapter supports start up on IBM Power Systems with FCode.

Feature #EN1G and #EN1H are electronically identical. They differ physically only that the #EN1G has a tail stock for full height PCIe slots and the #EN1H has a low profile tail stock.

CCIN is 579B for both features.

Each port has two LED indicators located on the bracket next to each connector. These LEDs communicate boot status and give a visual indication of the operating state. The LEDs have five defined states; solid on, solid off, slow blink, fast blink, and flashing. The slow blink rate is 1Hz, the fast blink is 4Hz, and the flashing refers to an irregular on/off transition that reflects test progress. The operator should observe the LED sequence for several seconds to ensure that the operating state is correctly identified.

Cables:

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: N/A o 32GFC: N/A

Note: The hardware cannot detect the type and length of cable that is installed. The link auto-negotiates to the speed that is reported during negotiation by the target. You must manually set the maximum negotiation speed. If the speed value is set higher than the supported cable value, bit errors can occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

Limitations: This adapter is not supported in India.

  • Attributes provided: Enhanced diagnostics and manageability, Unparalleled performance and more efficient port utilization, Single initiator capability over a fiber optic link or with NPIV, 16 Gb/s of throughput per port, Multiple initiator capabilities.
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN1J) - PCIe4 32Gb 2-port Optical Fibre Channel Adapter

This PCIe 4.0 x8 dual-port 32 Gigabit optical fibre channel (FC) adapter is a high-performance short form adapter based on the Marvell QLE2772 PCIe host bus adapter (6.6 inches x 2.731 inches). The adapter provides two ports of 32Gb fibre channel capability using SR optics. Each port can provide up to 6,400MBps bandwidth per port.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The adapter ships with 32Gb SR optical transceivers installed. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 8, 16 and 32Gbps and will automatically negotiate to the highest speed possible. The adapter supports boot on IBM power with fcode.

Feature #EN1J and #EN1K are electronically identical. They differ physically only that the #EN1J has a tail stock for full height PCIe slots and the #EN1K has a short tail stock for low profile PCIe slots.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 2-port 32Gb Optical FC
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN1L) - PCIe4 32Gb 4-port Optical Fibre Channel Adapter

This PCIe 4.0 8x 4-port 32 Gigabit optical fibre channel (FC) adapter is a high-performance short form adapter PCIe host bus adapter (6.6 inches x 2.731 inches). The adapter provides four ports of 32Gb fibre channel capability using SR optics. Each port can provide up to 6,400MBps bandwidth per port.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The adapter ships with 32Gb SR optical transceivers installed. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 8, 16 and 32Gbps and will automatically negotiate to the highest speed possible. The adapter supports boot on IBM power with fcode.

Feature #EN1L and #EN1M are electronically identical with the same CCIN of 2CFC. They differ physically only that the #EN1L has a tail stock for full height PCIe slots and the #EN1M has a short tail stock for low profile PCIe slots.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 4-port 32Gb Optical FC
  • Attributes required: Full height profile PCIe Gen4 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX Version 7.3 with the 7300-01 Technology Level and Service Pack 7300-01-01-2246, or later
    • AIX Version 7.2 with the 7200-05 Technology Level and Service Pack 7200-05-05-2246, or later
    • AIX Version 7.3 with the 7300-00 Technology Level and Service Pack 7300-00-03-2246, or later (planned availability date March 17, 2023)
    • SUSE Linux Enterprise Server 15, Service Pack 4, or later
    • Red Hat Enterprise Linux 8.6, for POWER LE, or later
    • Red Hat Enterprise Linux 9.0, for POWER LE, or later
    • Red Hat OpenShift Container Platform, 4.11, or later
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS requires VIOS 3.1.4.10, or later
(#EN1N) - PCIe4 64Gb 2-port Optical Fibre Channel Adapter

This PCIe 4.0 8x 2-port 64 Gigabit optical fibre channel (FC) adapter is a high-performance short form adapter PCIe host bus adapter (6.6 inches x 2.731 inches). The adapter provides two ports of 64Gb fibre channel capability using SR optics. Each port can provide up to 6,400MBps bandwidth per port.

Each port provides single initiator capability over a fibre link or with NPIV, multiple initiator capability is provided. The adapter ships with 64Gb SR optical transceivers installed. The ports have LC type connectors and utilize shortwave laser optics. The adapter operates at link speeds of 8, 16 and 32Gbps and will automatically negotiate to the highest speed possible. The adapter supports boot on IBM power with fcode.

Feature #EN1N and #EN1P are electronically identical with the same CCIN of 2CFD. They differ physically only that the #EN1N has a tail stock for full height PCIe slots and the #EN1P has a short tail stock for low profile PCIe slots.

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 2-port 64Gb Optical FC
  • Attributes required: Full height profile PCIe Gen4 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX Version 7.3 with the 7300-01 Technology Level and Service Pack 7300-01-01-2246, or later
    • AIX Version 7.2 with the 7200-05 Technology Level and Service Pack 7200-05-05-2246, or later
    • AIX Version 7.3 with the 7300-00 Technology Level and Service Pack 7300-00-03-2246, or later (planned availability date March 17, 2023)
    • SUSE Linux Enterprise Server 15, Service Pack 4, or later
    • Red Hat Enterprise Linux 8.6, for POWER LE, or later
    • Red Hat Enterprise Linux 9.0, for POWER LE, or later
    • Red Hat OpenShift Container Platform, 4.11, or later
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS requires VIOS 3.1.4.10, or later
(#EN2A) - PCIe3 16Gb 2-port Fibre Channel Adapter

PCIe Gen3 16 Gigabit dual-port Optical Fibre Channel (FC) Adapter is a high-performance 8x short form adapter PCIe Host Bus Adapter (HBA). The adapter provides two ports of 16Gb Fibre Channel capability using SR optics. Each port can provide up to 16Gb Fibre Channel functions simultaneously.

Each port provides single initiator capability over a fibre link. If you are using N_Port ID Virtualization (NPIV), multiple initiator capability is provided. The ports are SFP+ and include an optical SR transceiver. The ports have little connector-type (LC) and utilize shortwave laser optics. The adapter operates at link speeds of 4, 8, and 16 Gbps and it will automatically negotiate to the highest speed possible.

The adapter connects to a Fibre Channel switch at 4 Gb, 8 Gb, or 16 Gb. It can directly attach to a device without a switch at 16 Gb. The adapter without a Fibre Channel switch attached is not supported at 4 Gb or 8 Gb.

NPIV capability is supported through Virtual I/O Server (VIOS).

Feature #EN2A and #EN2B are electronically identical. They differ physically only that EN2A has a tail stock for full high PCIe slots and #EN2B has a short tail stock for low profile PCIe slots.

CCIN is 579D for both features.

Each port has two LED indicators located on the bracket next to each connector. These LEDs communicate boot status and give a visual indication of the operating state. The LEDs have five defined states; solid on, solid off, slow blink, fast blink, and flashing. The slow blink rate is 1Hz, the fast blink is 4Hz, and the flashing refers to an irregular on/off transition that reflects test progress. The operator should observe the LED sequence for several seconds to ensure that the operating state is correctly identified.

The adapter has the following features:

  • The adapter is compliant with the PCIe base and Card Electromechanical (CEM) 2.0 specifications with the following characteristics:
    • Provides an x8 lane link interface at 14.025 Gbps, 8.5 Gbps, or 4.25 Gbps (automatic negotiation with system)
    • Provides support for one Virtual Channel (VC0) and one Traffic Class (TC0)
    • Provides configuration and I/O memory read and write, completion, and messaging capabilities
    • Provides support for 64-bit addressing
    • Provides error correction code (ECC) and error protection functions
    • Provides link cyclic redundancy check (CRC) on all PCIe packets and message information
    • Provides a large payload size of 2048 bytes for read and write functions
    • Provides a large read request size of 4096 bytes
  • The adapter is compatible with 4, 8, and 16 Gb Fibre Channel interface with the following characteristics:
    • Provides for automatic negotiation between 4 Gb, 8 Gb, or 16 Gb link attachments
    • Provides support for the following Fibre Channel topologies: point-to-point (16 Gb only) and fabric
    • Provides support for Fibre Channel class 3
    • Provides a maximum Fibre Channel throughput that is achieved by using full duplex hardware support
  • The adapter provides an end-to-end data path parity and CRC protection, including internal data path random-access memory (RAM)
  • Provides architectural support for multiple upper layer protocols
  • Provides comprehensive virtualization capabilities with support for N_Port ID Virtualization (NPIV) and virtual fabric (VF)
  • Provides support for message signaled interrupts extended (MSI-X)
  • Provides support for 255 VFs and 1024 MSi-X
  • Provides an internal, high-speed static random-access memory (SRAM) memory
  • Provides ECC protection of local memory that includes single-bit correction and double-bit protection
  • Provides an embedded shortwave optical connection with diagnostics capability
  • Provides support for an on-board context management by firmware:
    • Up to 8192 FC port logins
    • I/O multiplexing down to the Fibre Channel frame level
  • Provides data buffers capable of supporting 64+ buffer-to-buffer (BB) credits per port for shortwave applications
  • Provides link management and recovery that is handled by firmware
  • Provides on-board diagnostic capability accessible by an optional connection
  • Provides a performance up to 16 Gbps full duplex

Cables:

Cables are the responsibility of the customer. Use multimode fibre optic cables with short-wave lasers that adhere to the following specifications:

  • OM4 - multimode 50/125 micron fibre, 4700 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 400m o 8GFC: 0.5m - 190m o 16GFC: 0.5m - 125m o 32GFC: 0.5m - 100m
  • OM3 - multimode 50/125 micron fibre, 2000 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 380m o 8GFC: 0.5m - 150m o 16GFC: 0.5m - 100m o 32GFC: 0.5m - 70m
  • OM2 - multimode 50/125 micron fibre, 500 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 150m o 8GFC: 0.5m - 50m o 16GFC: 0.5m - 35m o 32GFC: 0.5m - 20m
  • OM1 - multimode 62.5/125 micron fibre, 200 MHz*km bandwidth with LC connectors o 4GFC: 0.5m - 70m o 8GFC: 0.5m - 21m o 16GFC: 0.5m - 15m o 32GFC: N/A

Note: The H/W cannot detect what length and type of cable is installed. The link will auto-negotiate to the speed reported during negotiation by the Target. The user must manually set the maximum negotiation speed. If too high of speed is selected, bit errors may occur.

See also optional wrap plug feature #ECW0 which is: a) Required to run some diagnostic procedures and b) In some cases may speed system boot when placed in empty ports as well as avoid useless messages pointing to a planned empty port.

  • Attributes provided: 2-port 16Gb Optical FC
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 50 (Initial order maximum: 50)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EN2W) - PCIe3 4-port 10GbE BaseT RJ45 Adapter

PCIe Gen3 short x8 adapter which provides four 10G-BaseT ports. The ports are RJ45. The ports default to auto negotiate the highest speed either 10Gb (10GBaseT), 1Gb (1000BaseT) or 100Mb (100BaseT) full duplex. Each RJ45 port's configuration is independent of the other. The adapter supports Ethernet NIC (Network Interface Card) traffic.

The RJ45 ports use 4-pair CAT-6A cabling for distances of up to 100 meters or CAT-6 cabling for distances up to 37 meters. CAT5 cabling is not tested and is not supported.

#EN2W and #EN2X are electronically identical with the same CCIN of 2F04. #EN2W has a full high tail stock and #EN2X has a low profile tail stock.

Details for the ports include:

  • NIM install supported for VIOS, AIX, and Linux
  • IEEE 802.3an (10GBASE-T), IEEE 802.3ab (1000BASE-T GbE), IEEEu (100BASE-T), 802.1p priority, 802.1Q VLAN tagging, 802.3x flow control, 802.3ad load-balancing and failover, Link aggregation, IEEE 802.3ad 802.3
  • Multiple MAC addresses / promiscuous mode (for PowerVM/VIOS) per interface
  • Message Signalling Interrupt (MSI-X, MSI) support of legacy pin interrupts
  • Ether II and IEEE 802.3 encapsulated frames
  • Jumbo frames up to 9.6 Kbytes
  • TCP checksum offload for IPv4 and IPv6
  • TCP segmentation Offload (TSO)
  • RSS (Receive Side Scaling) support for IPv4, IPv6 and UDP
  • UDP checksum offload for IPv4 and IPv6
  • AIX, IBM i, and Linux provide software iSCSI support through the adapter
  • Attributes provided: 4-ports 10G-BaseT Adapter
  • Attributes required: Full high profile PCIe Gen3 slot
  • Minimum required: 0
  • Maximum allowed: 51 (Initial order maximum: 51)
  • OS level required:
    • AIX Version 7.3 with the 7300-01 Technology Level and Service Pack 7300-01-01-2246, or later
    • AIX Version 7.2 with the 7200-05 Technology Level and Service Pack 7200-05-05-2246, or later
    • AIX Version 7.3 with the 7300-00 Technology Level and Service Pack 7300-00-03-2246, or later (planned availability date March 17, 2023)
    • SUSE Linux Enterprise Server 15, Service Pack 4, or later
    • Red Hat Enterprise Linux 8.6, for POWER LE, or later
    • Red Hat OpenShift Container Platform, 4.11, or later
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS requires VIOS 3.1.4.10, or later
(#ENSH) - IBM eBMC Inidcator node 9043-MRX for China
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EP20) - Power Enterprise Pools 2.0 Enablement

Power Enterprise Pools 2.0 Enablement

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EP2X) - Lab Services Private Cloud Capacity Assessment

Private Cloud Capacity Assessment from Lab Services as part of the Power to Cloud Rewards program, when the engagement is pre-selected via feature #EP2X on one or more qualifying Power E1080 system

  • Attributes provided: Private Cloud Capacity Assessment from Lab Services
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPA0) - Deactivation of LPM (Live Partition Mobility)

This feature codes provides firmware commands to deactivate LPM.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPEU) - 12-core Typical 3.35 to 4.0 GHZ (max) processor

Forty-eight core Typical 3.35 to 4.0 GHz (max) Power10 processor planar containing four Twelve-core processor DCMs. Each processor feature will deliver a set of four identical processors that populate all the sockets in a given system node. All processors in the system node must be identical. Activations are applied per system with a minimum of all cores activated in the first socket.

  • Attributes provided: Four 12-core Typical 3.35 to 4.0 GHz (max) DCMs providing 48-core system node
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EPEV) - 18-core Typical 3.20 to 4.0 GHZ (max) processor

Seventy-Two cores Typical 3.20 to 4.0 GHz (max) Power10 processor planar containing four Eighteen-cores processor DCMs. Each processor feature will deliver a set of four identical processors that populate all the sockets in a given system node. All processors in the system node must be identical. Activations are applied per system with a minimum of all cores activated in the first socket.

  • Attributes provided: Four 18-core Typical 3.20 to 4.0 GHz (max) DCMs providing 72-core system node
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EPGW) - 24-core Typical 2.95 to 3.90 GHZ (max) processor

Ninety-six -cores Typical 2.95 to 3.90 GHz (max) Power10 processor planar containing four Thirty-cores processor DCMs. Each processor feature will deliver a set of four identical processors that populate all the sockets in a given system node. All processors in the system node must be identical. Activations are applied per system with a minimum of all cores activated in the first socket.

  • Attributes provided: Four 24-core Typical 2.95 to 3.90 GHz (max) DCMs providing 96-core system node
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required:
    • AIX - supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EPLU) - Front Heatsink + TIM PAD (For MRX)
  • Minimum required: 0
  • Maximum allowed: 2 (Initial order maximum: 2)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPLV) - Rear Heatsink + TIM PAD (For MRX)
  • Minimum required: 0
  • Maximum allowed: 2 (Initial order maximum: 2)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRS) - 1 core Base Processor Activation (Pools 2.0) for EPEU

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEU for Pools 2.0 to support any OS.
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRT) - 1 core Base Processor Activation (Pools 2.0) for EPEV

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEV for Pools 2.0 to support any OS.
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRV) - 1 core Base Processor Activation (Pools 2.0) for EPGW

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPGW for Pools 2.0 to support any OS.
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRW) - 1 core Base Linux Processor Activation (Pools 2.0) for EPEU

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEU for Pools 2.0 to support Linux only.
  • Attributes required: #EPEU with inactive processor cores - Linux only.
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRX) - 1 core Base Linux Processor Activation (Pools 2.0) for EPEV

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEV for Pools 2.0 to support Linux only.
  • Attributes required: #EPEV with inactive processor cores - Linux only.
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPRZ) - 1 core Base Linux Processor Activation (Pools 2.0) for EPGW

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPGW for Pools 2.0 to support Linux only.
  • Attributes required: #EPGW with inactive processor cores - Linux only.
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSA) - 1 core Base Processor Activation (Pools 2.0) for #EPEU (From Static)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEU for Pools 2.0.
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSB) - 1 core Base Processor Activation (Pools 2.0) for #EPEV (From Static)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPEV for Pools 2.0.
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSD) - 1 core Base Processor Activation (Pools 2.0) for #EPGW (From Static)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One permanent activation processor core on Processor Card #EPGW for Pools 2.0.
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSE) - 1 core Base Processor Activation (Pools 2.0) for #EPEU (From Static) Linux only

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One permanent activation Linux processor core on Processor Card #EPEU for Pools 2.0.
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSF) - 1 core Base Processor Activation (Pools 2.0) for #EPEV (From Static) Linux only

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One permanent activation Linux processor core on Processor Card #EPEV for Pools 2.0.
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSH) - 1 core Base Processor Activation (Pools 2.0) for #EPGW (From Static) Linux only

Each occurrence of this feature will permanently activate one Base Linux processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One permanent activation Linux processor core on Processor Card #EPGW for Pools 2.0.
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSJ) - 1GB Base Memory activation (Pools 2.0)

Feature EPSJ allows the activation of 1 GB Memory for Pools 2.0

  • Attributes provided: 1GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 16384 (Initial order maximum: 16384)
  • OS level required:
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSP) - 100GB Base Memory activation (Pools 2.0)

Feature EPSP allows the activation of 100 GB Memory for Pools 2.0

  • Attributes provided: 100GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 163 (Initial order maximum: 163)
  • OS level required:
  • Initial Order/MES/Both/Supported: MES
  • CSU: Yes
  • Return parts MES: No
(#EPSQ) - 512GB Base Memory Activation for Pools 2.0 (From Static)

Feature EPSQ allows the activation of 512 GB Memory for Pools 2.0 (from Static)

  • Attributes provided: 512GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSR) - 1GB Base Memory Activation for Pools 2.0 (From Static)

Feature EPSR allows the activation of 1 GB Memory for Pools 2.0 (From Static)

  • Attributes provided: 1GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 16384 (Initial order maximum: 16384)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSS) - 100GB Base Memory Activation for Pools 2.0 (From Static)

Feature EPSS allows the activation of 100 GB Memory for Pools 2.0 (From Static)

  • Attributes provided: 100GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 163 (Initial order maximum: 163)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPST) - 512GB Base Memory Activation for Pools 2.0 (From Linux)

Feature EPST allows the activation of 512 GB Memory for Pools 2.0 (From Linux)

  • Attributes provided: 512GB Base Memory Activation for Pools 2.0.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 32 (Initial order maximum: 32)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSU) - 256GB Base Memory Activation for Pools 2.0 - Linux only

Feature EPSU allows the activation of 256 GB Memory for Pools 2.0 - Linux only

  • Attributes provided: 256GB Base Memory Activation for Pools 2.0 - Linux only.
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPSW) - 256GB Base Memory Activation for Pools 2.0

Feature EPSW allows the activation of 256 GB Memory for Pools 2.0

  • Attributes provided: 256GB Base Memory Activation for Pools 2.0
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPTH) - Horizontal PDU Mounting Hardware

This feature ships the hardware required to properly horizontally mount one #EPTG/EPTJ, #EPTK/EPTL, #EPTM/EPTN or #EPTP/EPTQ PDU in a 1U 19-inch rack. A 1U blank panel for the front of the rack for air-flow control is included.

Without this hardware, the PDU can be mounted vertically in the rack's side pockets, but can only be poorly mounted horizontally. The front end of the PDU will be firmly attached to the rear of the rack. But the front of the PDU will be unsupported toward the middle of the rack. Without this hardware, the unsupported end of the PDU will rest on the hardware mounted immediately below it. If that underlying hardware is removed from the rack there is no support for the PDU.

Important Note: This feature code is typically used for an MES order and not for an original order of a new rack with #EPTn PDUs. As part of factory integration, IBM Manufacturing automatically adds this hardware without a feature code and at no additional charge when its #EPTn PDU placement logic calls for horizontally mounted PDUs. Use this feature code when (1) converting an existing vertically mounted #EPTn PDU to horizontal mounting or (2) separately ordering a #EPTn PDU for horizontal field installation.

  • Attributes provided: mounting hardware
  • Attributes required: High Function PDU (#EPT*) and space in 19-inch rack
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPTJ) - High Function 9xC19 PDU

Switched, Monitoring

This is an intelligent, switched 200-240 volt AC Power Distribution Unit (PDU) with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the nine C19 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Depending on country wiring standards the PDU is single-phase or three-phase wye. See three-phase #EPTK/EPTL for countries which do not use wye wiring.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features #6489, #6491, #6492, #6653, #6654, #6655, #6656, #6657, #6658, #6667, #ELC1 or #ELC2.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

There are also three C13 receptacles on the rear of the PDU positioned toward the middle of the rack. These are generally not easily accessed and therefore IBM does not generally recommend their use.

#EPTG and #EPTJ are identical PDUs. Up to one lower price #EPTG can be ordered with a new 7014-T42/T00 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #7189 PDU.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Nine C19 PDU - switched, power monitoring
  • Attributes required: PDU wall line cord & space in 19-inch rack
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EPTL) - High Function 9xC19 PDU 3-Phase

Switched, Monitoring

This is an intelligent, switched 208 volt 3-phase AC Power Distribution Unit (PDU) with nine C19 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the nine C19 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C20 plug connect to C19 PDU receptacles and are ordered separately. One wall line cord is provided with the PDU (no separate feature code) and has a IEC60309 60A plug (3P+G). The PDU supports up to 48 amps.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

There are also three C13 receptacles on the rear of the PDU positioned toward the middle of the rack. These are generally not easily accessed and therefore IBM does not generally recommend their use.

#EPTK and #EPTL are identical PDUs. Up to one lower price #EPTK can be ordered with a new 7014-T42/T00 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #7196 PDU.

Not orderable in China and Hong Kong.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Nine C19 PDU - switched, power monitoring
  • Attributes required: space in rack, 3-phase 208V AC delta electrical service
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EPTN) - High Function 12xC13 PDU

Switched, Monitoring

This is an intelligent, switched 200-240 volt AC Power Distribution Unit (PDU) with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the twelve C13 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker. Depending on country wiring standards the PDU is single- phase or three-phase wye. See three-phase #EPTK/EPTL for countries which do not use wye wiring.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C14 plug connect to C13 PDU receptacles and are ordered separately. One country-specific wall line cord is also ordered separately and attaches to a UTG524-7 connector on the front of the PDU. Supported line cords include features #6489, #6491, #6492, #6653, #6654, #6655, #6656, #6657, #6658, #6667, #ELC1 or #ELC2.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

#EPTM and #EPTN are identical PDUs. Up to one lower price #EPTM can be ordered with a new 7014-T42/T00 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #7109 PDU.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Twelve C13 PDU - switched, power monitoring
  • Attributes required: PDU wall line cord & space in 19-inch rack
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EPTQ) - High Function 12xC13 PDU 3-Phase

Switched, Monitoring

This is an intelligent, switched 208 volt 3-phase AC Power Distribution Unit (PDU) with twelve C13 receptacles on the front of the PDU. The PDU is mounted on the rear of the rack making the twelve C13 receptacles easily accessible. Each receptacle has a 20 amp circuit breaker.

The PDU can be mounted vertically in rack side pockets or it can be mounted horizontally. If mounted horizontally, it uses 1 EIA (1U) of rack space. See feature #EPTH for horizontal mounting hardware.

Device power cords with a C14 plug connect to C13 PDU receptacles and are ordered separately. One wall line cord is provided with the PDU (no separate feature code) and has a IEC60309 60A plug (3P+G). The PDU supports up to 48 amps.

Two RJ45 ports on the front of the PDU enable the client to monitor each receptacle's electrical power usage and to remotely switch any receptacle on or off. The PDU is shipped with a generic PDU password and IBM strongly urges clients to change it upon installation.

#EPTP and #EPTQ are identical PDUs. Up to one lower price #EPTP can be ordered with a new 7014-T42/T00 rack in place of a no-charge #9188 PDU.

For comparison, this is most similar to the earlier generation #7196 PDU, but offers C13 receptacles.

Not orderable in China and Hong Kong.

Limitation: Some configurations of the Elastic Storage Server (ESS) are delivered with a Intelligent PDU. At this time, the intelligent management capabilities of this PDU are not configured or used by the ESS system. If the ESS Customer would like to use this capability, it is the Customers responsibility to configure this PDU. In any case the ethernet port on the Intelligent PDU must not be connected to the ESS Management switch.

  • Attributes provided: Twelve C13 PDU - switched, power monitoring
  • Attributes required: space in rack, 3-phase 208V AC delta electrical service
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 0)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
(#EPUR) - 1 core Processor Activation for #EPEU

Each occurrence of this feature will permanently activate one processor core on Processor Card #EPEU

  • Attributes provided: One processor core activation on Processor Card #EPEU.
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required:
    • See feature #EPEU to find the supported OS levels .
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPUS) - 1 core Processor Activation for #EPEV

Each occurrence of this feature will permanently activate one processor core on Processor Card #EPEV

  • Attributes provided: One processor core activation on Processor Card #EPEV.
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required:
    • See feature #EPEV to find the supported OS levels .
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPVV) - PowerVM - Enterprise Edition

This feature allows the customer to create partitions that are in units of less than 1 CPU (sub-CPU LPARs) and allows the same system I/O to be virtually allocated to these partitions. The processors on the system can be partitioned up to 20 LPARS per processor core. An encrypted key is supplied to the customer and installed on the system, authorizing the partitioning at the sub-processor level.

Included with Feature EPVV is the IBM Virtual I/O Server and Live Partition Mobility, which allows for the movement of a logical partition from one POWER8 processor-based server to another with no application downtime. to provide additional virtualization function.

  • Attributes provided: System virtualization with Partition Mobility
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EPYT) - 1 core Processor Activation for #EPGW

Each occurrence of this feature will permanently activate one processor core on Processor Card #EPGW.

  • Attributes provided: One processor core activation on Processor Card #EPGW.
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required:
    • See feature #EPGW to find the supported OS levels .
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ0) - 1 core Base Processor Activation (Pools 2.0) for EPEU (from Prev)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One Base processor core activation (Pools 2.0) for #EPEU
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ1) - 1 core Base Processor Activation (Pools 2.0) for EPEV (from Prev)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One Base processor core activation (Pools 2.0) for #EPEV
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ2) - 1 core Base Processor Activation (Pools 2.0) for EPGW (from Prev)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One Base processor core activation (Pools 2.0) for #EPGW
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ4) - 1 core Base Linux only Processor Activation (Pools 2.0) for EPEU (from Prev)

Each occurrence of this feature will permanently activate one Base Linux only processor core on Processor Card #EPEU for Pools 2.0

  • Attributes provided: One Base Linux only processor core activation (Pools 2.0) for #EPEU
  • Attributes required: #EPEU with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ5) - 1 core Base Linux only Processor Activation (Pools 2.0) for EPEV (from Prev)

Each occurrence of this feature will permanently activate one Base Linux only processor core on Processor Card #EPEV for Pools 2.0

  • Attributes provided: One Base Linux only processor core activation (Pools 2.0) for #EPEV
  • Attributes required: #EPEV with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 72 (Initial order maximum: 72)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQ6) - 1 core Base Linux only Processor Activation (Pools 2.0) for EPGW (from Prev)

Each occurrence of this feature will permanently activate one Base Linux only processor core on Processor Card #EPGW for Pools 2.0

  • Attributes provided: One Base Linux only processor core activation (Pools 2.0) for #EPGW
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 96 (Initial order maximum: 96)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQM) - 256GB Base Memory Activation (Pools 2.0) (from Prev)

This feature delivers 256 GB Base Memory only for Pools 2.0

  • Attributes provided: 256GB Base Memory Activation for Pools 2.0
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQN) - 256GB Base Linux only Memory Activation (Pools 2.0) (from Prev)

This feature delivers 256 GB Base Linux only Memory activation for Pools 2.0

  • Attributes provided: 256GB Base Memory Activation for Pools 2.0 - Linux only
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required:
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQP) - 1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW - any O/S

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPGW for Pools 2.0 - Healthcare

  • Attributes provided: One Base processor core activation (Pools 2.0 - Healthcare) for #EPGW
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQQ) - 1 Base Processor Activation (PEP 2.0 Healthcare) for #EPGW - any O/S (Conv from HSE)

Each occurrence of this feature will permanently activate one Base processor core on Processor Card #EPGW for Pools 2.0 - Healthcare

  • Attributes provided: One Base processor core activation (Pools 2.0 - Healthcare) for #EPGW
  • Attributes required: #EPGW with inactive processor cores
  • Minimum required: 0
  • Maximum allowed: 48 (Initial order maximum: 48)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQR) - 512GB Base Memory Activation for Pools2.0

This feature delivers 512 GB Base Memory only for Pools 2.0

  • Attributes provided: 512GB Base Memory Activation for Pools 2.0
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQS) - 512GB Base Memory Activation for Pools2.0 Healthcare

This feature delivers 512 GB Base Memory only for Pools 2.0 - Healthcare

  • Attributes provided: 512GB Base Memory Activation for Pools 2.0 - Healthcare
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ERQT) - 512GB Base Memory Activation for Pools2.0 (convert Healthcare)

This feature delivers 512 GB Base Memory only for Pools 2.0 - Healthcare

  • Attributes provided: 512GB Base Memory Activation for Pools 2.0 - Healthcare
  • Attributes required: Inactive Memory available for temporary use installed
  • Minimum required: 0
  • Maximum allowed: 4 (Initial order maximum: 4)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ES1E) - Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 1.6 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES1E and #ES1F are physically identical drives with the same CCIN of 59B8. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature ES1E indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature ES1F indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ES1G) - Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 3.2 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES1G and #ES1H are physically identical drives with the same CCIN of 59B9. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature ES1G indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature ES1H indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ES3B) - Enterprise 1.6 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 1.6 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES3B and #ES3C are physically identical drives with the same CCIN of 5B52. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature ES3B indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature ES3C indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 1.6 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ES3D) - Enterprise 3.2 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 3.2 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES3D and #ES3E are physically identical drives with the same CCIN of 5B51. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature ES3D indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature ES3E indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 3.2 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ES3F) - Enterprise 6.4 TB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 6.4 TB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES3F and #ES3G are physically identical drives with the same CCIN of 5B50. Different feature codes to help the IBM configuration tools understand how the NVMe is used. Feature ES3F indicates usage by AIX, Linux or VIOS in which the SSD is formatted in 4096 byte sectors. Feature ES3G indicates usage by IBM i in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger.Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 6.4 TB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ES3H) - Enterprise 800GB SSD PCIe4 NVMe U.2 module for AIX/Linux

Enterprise 800 GB NVMe SFF U.2 15mm SSD (Solid State Drive) is a Peripheral Component Interconnect Express (PCIe) generation 4 (Gen4) drive. The SSD can be used in any U.2 15mm NVMe slot in the system and uses Non-Volatile Memory Express (NVMe). NVMe is a high performance architecture and command protocol that can read/write flash memory. Compared to a SAS or SATA SSD, the NVMe SSD provides more read/write input/output operations per second (IOPS) and larger throughput (GB/sec).

Features #ES3H has CCIN number of xxxx and indicates usage by AIX/ Linux in which the SSD is formatted in 4160 byte sectors.

This Enterprise solid-state drive is rated at 3 DWPD (Drive Writes Per Day) calculated over a 5-year period for 100% (4K bytes or larger) random write workloads. Use for workloads within this rating are fully supported and will maintain high reliability and MTBF.

The nature of the workload has a great impact on the maximum write capacity. If a high percentage of more sequentially oriented writes is used instead of random writes, the maximum write capacity will be larger. Writes past the SSD's maximum write capacity will continue to work for some period of time, but perform much more slowly. Whether the application uses sequential or random reads from the device does not affect the life of the device. A Predictive Failure Analysis message will indicate that it is time to replace the SSD if enabled by the operating system (OS) and system administrator. Customers are recommended to monitor SMART log critical information via the appropriate OS utility to observe drive life remaining information. IBM NVMe SSD failures will be replaced during the standard warranty and maintenance period for SSD's that have not reached the maximum number of write cycles. SSD's that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Boot supported. Data redundancy on a failed SSD may be provided by OS mirroring or software RAID wherever applicable.

This PCIe NVMe device can have 64 namespaces per device.

  • Attributes provided: 800 GB PCIe4 NVMe SSD
  • Attributes required: SFF U.2 slot
  • Minimum required: 0
  • Maximum allowed: 10 (Initial order maximum: 10)
  • OS level required:
    • AIX supported
    • Linux supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ES94) - 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24S (#5887) or EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ES94 and #ES95 are physically identical drives with the same CCIN of 5B10. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ES94 indicates usage by AIX, Linux or VIOS. Feature ES95 indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX supported
    • Linux supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESB2) - 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESB2 CCIN is 5B16. Different feature codes to help the IBM configuration tools understand how the SSD is used. ESB2 indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 5xx SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESB6) - 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESGZ CCIN is 5B17. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESGZ indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 5xx SSD
  • Attributes required: SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESBA) - 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESBA and #ESBB are physically identical drives with the same CCIN of 5B10. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESBA indicates usage by AIX, Linux or VIOS. Feature ESBB indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESBG) - 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESBG and #ESBH are physically identical drives with the same CCIN of 5B11. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESBG indicates usage by AIX, Linux or VIOS. Feature ESBH indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESBL) - 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 1.55 TB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESBL and #ESBM are physically identical drives with the same CCIN of 5B12. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESBL indicates usage by AIX, Linux or VIOS. Feature ESBM indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 1.55 TB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESC0) - S&H - No Charge

No charge shipping and handling

  • Attributes provided: None
  • Attributes required: Sales Preapproval Required
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Both
  • CSU: N/A
  • Return parts MES: Does not apply
(#ESC7) - S&H

Shipping and handling

  • Attributes provided: None
  • Attributes required: Sales Preapproval Required
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply
(#ESCT) - Virtual Capacity Expedited Shipment

This feature will instruct the Manufacture scheduling team to schedule shipment of orders with only activation features immediately (within 24 hours). Set (ESCT = 1) to trigger the expedite and receive and electronic notification. Set (ESCT = 0) to receive the paper notification and normal order scheduling.

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 0)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: MES
  • CSU: N/A
  • Return parts MES: Does not apply
(#ESCZ) - iSCSI SAN Load Source Specify for AIX

Indicates that an LAN adapter is being used as the Load Source for the AIX operating system.

  • Attributes provided: iSCSI load source placement specify
  • Attributes required: LAN adapter
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:
    • AIX supported
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#ESEV) - 600GB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux

600 GB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive on Gen-2 carrier/tray. Supported in SFF-2 SAS bays such as found in EXP24S storage drawer. IBM Manufacturing may ship formatted with 4224 byte sectors or with 4096 sectors. With 4096 byte sectors the drive's capacity is 600 GB or with 4224 byte sectors the capacity is 571 GB. Using 4224 byte sectors provides additional data integrity protection. Reformatting large drives takes significant time.

Features #ESEU and #ESEV are physically identical drives with the same 59D2 CCIN. Different feature codes help the IBM configuration tools understand how the HDD is used. #ESEV indicates usage by AIX, Linux or VIOS. #ESEU indicates usage by IBM i.

Limitations:

  • Cannot be combined in the same array as a drive using different sector size
  • Physically does not fit in a SFF-1 or SFF-3 bay due to carrier/ tray differences

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: 571GB 10K RPM SFF-2 Disk 4K
  • Attributes required: one SFF-2 SAS bay
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 672)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#ESF3) - 1.2TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux

1.2 TB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive on Gen-2 carrier/tray. Supported in SFF-2 SAS bays such as found in EXP24S storage drawer. IBM Manufacturing may ship formatted with 4224 byte sectors or with 4096 sectors. With 4096 byte sectors the drive's capacity is 1.2 TB or with 4224 byte sectors the capacity is 1.14TB. Using 4224 byte sectors provides additional data integrity protection. Reformatting large drives takes significant time.

Features #ESF2 and #ESF3 are physically identical drives with the same 59DA CCIN. Different feature codes help the IBM configuration tools understand how the HDD is used. #ESF3 indicates usage by AIX, Linux or VIOS. #ESF2 indicates usage by IBM i.

Limitations:

  • Cannot be combined in the same array as a drive using different sector size
  • Physically does not fit in a SFF-1 or SFF-3 bay due to carrier/ tray differences

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: 1.2TB 10K RPM SFF-2 Disk 4K
  • Attributes required: one SFF-2 SAS bay
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 672)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#ESFT) - 1.8TB 10K RPM SAS SFF-2 HDD 4K for AIX/Linux

1.8 TB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive on Gen-2 carrier/tray. Supported in SFF-2 SAS bays such as found in EXP24S storage drawer. IBM Manufacturing may ship formatted with 4224 byte sectors or with 4096 sectors. With 4096 byte sectors the drive's capacity is 1.8 TB or with 4224 byte sectors the capacity is 1.71TB. Using 4224 byte sectors provides additional data integrity protection. Reformatting large drives takes significant time.

Features #ESFS and #ESFT are physically identical drives with the same 59DD CCIN. Different feature codes help the IBM configuration tools understand how the HDD is used. #ESFT indicates usage by AIX, Linux or VIOS. #ESFS indicates usage by IBM i.

Limitations:

  • Cannot be combined in the same array as a drive using different sector size
  • Physically does not fit in a SFF-1 or SFF-3 bay due to carrier/ tray differences

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: 1.8TB 10K RPM SFF-2 Disk 4K
  • Attributes required: one SFF-2 SAS bay
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 672)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#ESGV) - 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24S (#5887) or EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESGV CCIN is 5B16. Different feature codes to help the IBM configuration tools understand how the SSD is used. ESGV indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 5xx SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESGZ) - 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24S (#5887) or EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESGZ CCIN is 5B17. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESGZ indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 5xx SSD
  • Attributes required: SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJ0) - 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

931 GB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJ0 and #ESJ1 are physically identical drives with the same 5B29 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJ0 indicates usage by AIX, Linux or VIOS. #ESJ1 indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 931 GB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter or later.
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJ2) - 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

1.86 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJ2 and #ESJ3 are physically identical drives with the same 5B21 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJ2 indicates usage by AIX, Linux or VIOS. #ESJ3 indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 1.86 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJ4) - 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

3.72 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJ4 and #ESJ5 are physically identical drives with the same 5B2D CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJ4 indicates usage by AIX, Linux or VIOS. #ESJ5 indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 3.72 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJ6) - 7.45TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

7.45 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJ6 and #ESJ7 are physically identical drives with the same 5B2F CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJ6 indicates usage by AIX, Linux or VIOS. #ESJ7 indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitations:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 7.45 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux supported
    • AIX supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJJ) - 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

931 GB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJJ and #ESJK are physically identical drives with the same 5B29 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJJ indicates usage by AIX, Linux or VIOS. #ESJK indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 931 GB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter or later.
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux supported
    • AIX supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJL) - 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

1.86 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJL and #ESJM are physically identical drives with the same 5B21 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJL indicates usage by AIX, Linux or VIOS. #ESJM indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 1.86 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux supported
    • AIX supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJN) - 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

3.72 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.45 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJN and #ESJP are physically identical drives with the same 5B2D CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJN indicates usage by AIX, Linux or VIOS. #ESJP indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 3.72 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESJQ) - 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

7.44 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.44 TB 13601

Depending on the nature of the workload, the lifetime TBW may be somewhat larger. To read the warranty and maintenance applicable to mainstream devices on Power10 servers, see the Terms and Conditions section for additional detail.

Features #ESJQ and #ESJR are physically identical drives with the same 5B2F CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESJQ indicates usage by AIX, Linux or VIOS. #ESJR indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitations:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9/Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 7.44 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESK1) - 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ESK1 CCIN is 5B16. Different feature codes to help the IBM configuration tools understand how the SSD is used. ESK1 indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 5xx SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESK3) - 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ESK3 CCIN is 5B17. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESK3 indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 5xx SSD
  • Attributes required: SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESK8) - 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ESK8 and #ESK9 are physically identical drives with the same CCIN of 5B10. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESK8 indicates usage by AIX, Linux or VIOS. Feature ESK9 indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKC) - 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ESKC and #ESKD are physically identical drives with the same CCIN of 5B11. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESKC indicates usage by AIX, Linux or VIOS. Feature ESKD indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKG) - 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 1.55 TB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ESKG and #ESKH are physically identical drives with the same CCIN of 5B12. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESKG indicates usage by AIX, Linux or VIOS. Feature ESKH indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 1.55 TB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKK) - 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

931 GB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.44 TB 13601

Features #ESKK and #ESKM are physically identical drives with the same 5B29 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESKK indicates usage by AIX, Linux or VIOS. #ESKM indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 931 GB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKP) - 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

1.86 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB) 931 GB 1700 1.86 TB 3399 3.72 TB 6799 7.44 TB 13601

Features #ESKP and #ESKR are physically identical drives with the same 5B21 CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESKP indicates usage by AIX, Linux or VIOS. #ESKR indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 1.86 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKT) - 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

3.72 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Features #ESKT and #ESKV are physically identical drives with the same 5B2D CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESKT indicates usage by AIX, Linux or VIOS. #ESKV indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 3.72 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESKX) - 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

7.44 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Features #ESKX and #ESKZ are physically identical drives with the same 5B2F CCIN. Different feature codes help the IBM configuration tools understand how the SSD is used. #ESKX indicates usage by AIX, Linux or VIOS. #ESKZ indicates usage by IBM i.
Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.

Limitations:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive can not be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 7.44 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESLA) - Specify AC Power Supply for EXP24SX Storage Enclosure

No-charge specify for AC power supply for an EXP24SX SAS Storage Enclosure.

The power supply has a 320-C14 inlet electrical connection for a separately ordered power cord. It is rated 800 Watts Output Power and 100-240 VAC (RMS) input voltage.

  • Attributes provided: communicates to IBM Manufacturing an AC Power Supply is to be used
  • Attributes required: EXP24SX Storage Enclosure and AC power cord
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#ESLS) - EXP24SX SAS Storage Enclosure

The EXP24SX is a storage expansion enclosure with 24 2.5-inch small form factor (SFF) SAS bays. It supports up to 24 hot-swap Hard Disk Drives (HDD) or Solid State Drives (SSD) in only 2 EIA of space in a 19-inch rack. The EXP24SX SFF bays use SFF gen2 (SFF-2) carriers/ trays identical to the carrier/trays in the previous EXP24S Drawer .

With AIX/Linux/VIOS, the EXP24SX can be ordered with four sets of 6 bays (mode 4), two sets of 12 bays (mode 2) or one set of 24 bays (mode 1). With IBM i one set of 24 bays (mode 1) is supported. The mode setting can be changed in the field using software commands along with a specificly documented procedure. IMPORTANT NOTE: when changing mode, it is very important that you follow the documented procedures and that there is no data on the drives before the change. Improperly changing modes can potentially destroy existing RAID sets, prevent access to existing data, or allow other partitions to access another partition's existing data. Hire an expert to assist if you are not familiar with this type of re-configuration work.

The EXP24SX has redundant SAS paths to all drives via two redundant Enclosure Services Modules (ESMs). Four mini-SAS HD narrow ports are attached to PCIe Gen3 SAS adapters such as the #EJ0J/EJ0M or #EJ0L or #EJ14, or attached to an imbedded SAS controller in a POWER8/POWER9 Scale-out server such as the Power S814, S822, S824, S914, S922, S924, H922, or H924. Attachment between the SAS controller and the storage enclosure SAS ports is via the appropriate SAS YO12 or X12 cables. The PCIe Gen3 SAS adapters support 6Gb throughput. The EXP24SX has been designed to support up to 12Gb throughput if future SAS adapters support that capability.

The EXP24SX uses redundant power supplies and two power cords. Order two feature #ESLA for AC power supplies. The enclosure is shipped with adjustable depth rails and can accommodate rack depths from 59.5 - 75 cm (23.4 - 29.5 inches). Slot filler panels are provided for empty bays when initially shipped from IBM.

  • Attributes provided: 24 SFF-2 SAS bays in a 2U enclosure
  • Attributes required: PCIe Gen3 SAS adapter/controller; Power System (at least POWER8/ POWER9 generation); 2U 19-inch rack space; Appropriate SAS cables
  • Minimum required: 0
  • Maximum allowed: 64 (Initial order maximum: 64)
  • OS level required:
    • AIX - supported
    • Linux - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESMB) - 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

931 GB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9 or Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive cannot be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 931 GB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESMF) - 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

1.86 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9 or Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive cannot be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 1.86 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESMK) - 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

3.72 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Limitation:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9 or Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive cannot be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 3.72 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESMV) - 7.44TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

7.44 TB SAS 2.5-inch (SFF) Mainstream solid state drive (SSD) formatted in 4224 byte sectors (4k). The drive is mounted on a 2.5-inch SFF-2 carrier/tray to fit an expansion drawer such as the EXP24SX. Drive is rated at 6Gb/s though actual performance is dependent upon multiple factors.

DWPD (Drive Write Per Day) rating is 1 calculated over a 5 year period. See the following table for the approximate lifetime Total Bytes Written (TBW) supported by each drive capacity:

Drive Capacity Total Bytes Written (TBW) in (TB)
931 GB 1700
1.86 TB 3399
3.72 TB 6799
7.44 TB 13601

Limitations:

  • The drive is mounted on a SFF-2 carrier/tray and does not physically fit into a Power9 or Power10 system unit's SFF-3 bays. JBOD formatting of 4096 byte sectors is not tested or supported. Drive cannot be reformatted to 5xx byte sectors. 5xx and 4k drives cannot be mixed in the same array. Older SAS adapters such as PCIe2 or earlier do not support 4k drives.
  • Attributes provided: 7.44 TB Mainstream SSD
  • Attributes required: Open SFF-2 SAS bay controlled by PCIe Gen3 PCIe SAS adapter, or later
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESNA) - 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24S (#5887) or EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESNA and #ESNB are physically identical drives with the same CCIN of 5B11. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESNA indicates usage by AIX, Linux or VIOS. Feature ESNB indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESNE) - 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 1.55 TB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24S (#5887) or EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM solid state device failures will be replaced during the standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense.

Features #ESNE and #ESNF are physically identical drives with the same CCIN of 5B12. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ESNE indicates usage by AIX, Linux or VIOS. Feature ESNF indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9/Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 1.55 TB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 0)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Supported
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ESNM) - 300GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/Linux)

300 GB 2.5-inch (Small Form Factor (SFF)) 15k rpm SAS disk drive on Gen-2 carrier/tray. Supported in SFF-2 SAS bays. Disk is formatted for 4096 byte sectors. If reformatted to 4224 byte sectors, capacity would be 283 GB. Drive includes enhanced caching capability with 256MB DRAM which may improve performance somewhat compared to previous disk drives without the cache.

CCIN is 5B43.

Limitations:

  • Cannot be combined in the same array as a drive of the same capacity, but using different sector size. However, can be combined with non-cached drives of same capacity in the same array.
  • This HDD feature is not supported in the EXP24S drawer (#5887 or #EL1S).
  • Attributes provided: 300 GB Disk Drive - SFF-2
  • Attributes required: one SFF-2 drive bay
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 672)
  • OS level required:
    • AIX - supported
    • IBM i - not supported
    • Linux - supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#ESNR) - 600GB 15K RPM SAS SFF-2 4k Block Cached Disk Drive (AIX/Linux)

600 GB 2.5-inch (Small Form Factor (SFF)) 15k rpm SAS disk drive on Gen-2 carrier/tray. Supported in SFF-2 SAS bays. Disk is formatted for 4096 byte sectors. If reformatted to 4224 byte sectors, capacity would be 571 GB. Drive includes enhanced caching capability with 256MB DRAM which may improve performance somewhat compared to previous disk drives without the cache.

CCIN is 5B47.

Limitations:

  • Cannot be combined in the same array as a drive of the same capacity, but using different sector size. However, can be combined with non-cached drives of same capacity in the same array.
  • This HDD feature is not supported in the EXP24S drawer (#5887 or #EL1S).
  • Attributes provided: 600 GB Disk Drive - SFF-2
  • Attributes required: one SFF-2 drive bay
  • Minimum required: 0
  • Maximum allowed: 672 (Initial order maximum: 672)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
  • VIOS supported
(#ESWK) - AIX Update Access Key (UAK)

With the introduction of the Power10 server, IBM expands upon the use of the update access key (UAK) with the addition of an AIX Software Maintenance (SWMA) UAK. This functionality provides proactive notification of AIX SWMA expirations to ensure continued and uninterrupted software support. AIX SWMA UAKs do not limit the operability of or capability to update AIX. For additional information see announcement letters:

  • For Japan: JP21-0387
  • For Asia Pacific: AP21-0322
  • For United States: 221-331
  • For Latin America: LP21-0395
  • For Canada: A21-050
  • For Europe Middle East and Africa: ZP21-0403
  • Attributes provided: AIX software maintenance agreements (SWMA) validation
  • Attributes required: AIX OS on server
  • Minimum required: 0
  • Maximum allowed: 999 (Initial order maximum: 999)
  • OS level required:
    • AIX - supported
    • IBM i - not supported
    • Linux - not supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#ETK1) - 387GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ETK1 CCIN is 5B16. Different feature codes to help the IBM configuration tools understand how the SSD is used. ETK1 indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9 or Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 5xx SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ETK3) - 775GB Enterprise SAS 5xx SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 5xx (528) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ETK3 CCIN is 5B17. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ETK3 indicates usage by AIX, Linux or VIOS.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9 or Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 512 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 5xx SSD
  • Attributes required: SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ETK8) - 387GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 387 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ETK8 and #ETK9 are physically identical drives with the same CCIN of 5B10. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ETK8 indicates usage by AIX, Linux or VIOS. Feature ETK9 indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9 or Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 387 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ETKC) - 775GB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 775 GB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ETKC and #ETKD are physically identical drives with the same CCIN of 5B11. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ETKC indicates usage by AIX, Linux or VIOS. Feature ETKD indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9 or Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 775 GB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#ETKG) - 1.55TB Enterprise SAS 4k SFF-2 SSD for AIX/Linux

This SFF (2.5") Enterprise SAS Solid State Drive (SSD) is shipped from IBM with 1.55 TB capacity formatted with 4k (4224) byte sectors. The drive is supported in SFF-2 SAS bays in the EXP24SX (#ESLS) I/O drawer. This drive is rated at 10 DWPD (Drive Writes Per Day) calculated over a 5-year period.

IBM SDD device failures will be replaced during standard warranty and maintenance period for devices that have not reached the maximum number of write cycles. Devices that reach this limit may fail to operate according to specifications and must be replaced at the client's expense. Individual service life may vary and can be monitored using an operating system command.

Features #ETKG and #ETKH are physically identical drives with the same CCIN of 5B12. Different feature codes to help the IBM configuration tools understand how the SSD is used. Feature ETKG indicates usage by AIX, Linux or VIOS. Feature ETKH indicates usage by IBM i.

Limitations:

  • Due to physical differences in the carrier/tray on which the drive is mounted, the SSD only fits in SFF-2 bays such as found in EXP24SX storage enclosure and cannot be used in Power9 or Power10 system units (SFF-3) or in older SFF-1 SAS bays. Also the drive was not tested with 4096 byte sectors and thus JBOD mode for AIX/Linux is not supported. 4k drives cannot be reformatted to 5xx drives (or vice versa).

Note: As part of a larger industry transition, IBM Power Systems is in the process of gradually shifting away from offering 5xx (512/ 528) byte sector SAS drives (HDD or SSD) to 4K byte sector drives. Most AIX/Linux applications access SAS drives through a file system and experience no effect of this sector size transition. In much less common cases, an AIX/Linux application may access the disk drive directly through the raw device interface and may still require only 5xx byte sectors drives. If there are 4k usage concerns, check with the application provider to ensure compatibility with 4K byte sector drives.
  • Attributes provided: one 1.55 TB SFF-2 4k SSD
  • Attributes required: one SFF-2 SAS bay, PCIe3 SAS controller
  • Minimum required: 0
  • Maximum allowed: 336 (Initial order maximum: 336)
  • OS level required:
    • Linux - supported
    • AIX - supported
    • Refer to Software Requirements for specific O/S levels supported
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EU29) - Order Placed Indicator

This feature is use to identify ORDER PLACED for administrative purposes within manufacturing to Facilitate processing.

  • Attributes provided: ORDER PLACED INDICATOR FOR ADMINISTRATIVE TRACKING
  • Attributes required: None.
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#EUA5) - Standalone USB DVD drive w/cable

The Standalone USB DVD drive (FC EUA5) is an optional, standalone external USB-DVD device. It requires high current at 5V and must use the front USB 3.0 port on the 9008-22L, 9009-22A, 9009-41A, 9009-42A, 9223-22H, 9223-42H, and 9043-MRX systems.

  • Custom card identification number (CCIN): 6331 model 005
  • Media: Reads CD-ROM, CD-R, CD-RW, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-ROM, and DVD-RAM discs; Writes 4.7 GB DVD-RAM discs; CD read speed at 24X; DVD-ROM read speed at 8X; DVD-RAM at 5X; DVD-RAM has a write speed of 5X; The buffer size is 0.75 MB and cannot be disabled.
  • Interface: USB
  • Connector: USB 2.0
  • Loading tray: supports 12 cm and 8 cm discs floor) Note: A USB extension cable is included (P/N 32N1311). The USB extension cable is to be used when there are no safe, flat spots available in the rack. This cable allows the drive to reach the floor. Alternate or additional extension cables are not supported as the total USB cable length can be no longer than 3 meters.
  • Form factor: standalone USB DVD drive
  • DVD video: not supported
  • Attributes provided: USB DVD drive
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required:
    • AIX - supported

    Refer to Software Requirements for specific O/S levels supported

  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
    Note: Assignment to the VIOS supported
(#EXA3) - 3 YEAR, ADVANCED EXPERT CARE

This feature indicates IBM Power Expert Care Advanced 3 years

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EXA4) - 4 YEAR, ADVANCED EXPERT CARE

This feature indicates the IBM Power Expert Care Advanced 4 year

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EXA5) - 5 YEAR, ADVANCED EXPERT CARE

This feature indicates IBM Power Expert Care Advanced 5 years

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EXP3) - 3 YEAR, PREMIUM EXPERT CARE

This feature indicates IBM Power Expert Care Premium 3 years

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EXP4) - 4 YEAR, PREMIUM EXPERT CARE

This feature indicates the IBM Power Expert Care Premium 4 year

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#EXP5) - 5 YEAR, PREMIUM EXPERT CARE

This feature indicates IBM Power Expert Care Premium 5 years

  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: No
(#SVBP) - BP Post-Sale Services

1 Day

BP Post-Sale Services: 1 Day

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#SVCS) - IBM Systems Lab Services Post-Sale Services

1 Day

IBM Systems Lab Services Post-Sale Services: 1 Day

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#SVNN) - Other IBM Post-Sale Services

1 Day

Other IBM Post-Sale Services: 1 Day

  • Attributes provided: None
  • Attributes required: None
  • Minimum required: 0
  • Maximum allowed: 9999 (Initial order maximum: 9999)
  • OS level required: None
  • Initial Order/MES/Both/Supported: Both
  • CSU: Yes
  • Return parts MES: No
(#SVPC) - 5000 Power to Cloud Reward points

The IBM Power to Cloud Reward Program is designed to accelerate the transformation of your IT infrastructure to private and hybrid cloud, by helping you design, build and deliver a cloud platform on IBM Power Systems servers with help from IBM Systems Lab Services.

You can earn reward points on select purchases of IBM Power Systems servers. Reward points can be used for a range of services focused on helping the transition from traditional IT platforms to private and hybrid cloud platforms by leveraging the proven expertise of IBM Systems Lab Services consultants.

For additional details, visit ibm.biz/PowertoCloud

This feature is ONLY for new initial orders or MES upgrades from Power9 to Power10. It DOES NOT allow loose part MES on Power10

  • Attributes provided: 5,000 Power to Cloud Reward points
  • Minimum required: 0
  • Maximum allowed: 1 (Initial order maximum: 1)
  • OS level required: N/A
  • Initial Order/MES/Both/Supported: Initial
  • CSU: N/A
  • Return parts MES: Does not apply

Feature exchanges

Not applicable.



Back to topBack to top

Accessories

Top rule

None.

Customer replacement parts

None.



Back to topBack to top

Supplies

Top rule

None.

Supplemental media

None.



Back to topBack to top

Trademarks

Top rule

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this Sales Manual at any time without notice. This Sales Manual is provided for your information only. Additional terms of use are located at

Terms of use


© IBM Corporation 2022.