The next generation of Power Systems servers with POWER9 technology
is built with innovations that can help deliver security and
reliability for the data-intensive workloads of today's enterprises.
POWER9 technology is designed from the ground up for data-intensive
workloads like databases and analytics.

This server generation has twice the memory footprint of POWER8
servers, making it an ideal platform for in-memory and data-centric
applications. Changes in the memory subsystem and the use of industry
standard memory DIMMs take POWER9 technology to the next level by
superseding a number of existing price/performance offerings.
Designed to run commercial, cognitive, and database workloads POWER9
technology provides a highly competitive server platform, client
references indicate POWER servers help provide a robust and secure
backbone of their IT infrastructure. More companies are using POWER
technology in their IT infrastructure down from the shop level to
large data center deployments.

The Power System H924 (9223-42H) for SAP HANA server by default has
its Power Management mode set to Max Performance. This mode can
dynamically optimize the processor frequency at any given time based
on CPU utilization and operating environmental conditions. For a
description of this feature and other power management options
available for this server, see the
IBM EnergyScale for POWER9 Processor-Based Systems
website.

The Power System H924 (9223-42H) for SAP HANA server provides an
optimized system configuration using enhanced processors, DDR4 ECC
memory, and IBM PowerVM Enterprise Edition virtualization for
enterprise-class deployment of the SAP HANA database and applications.

With this highly flexible system with best-in-class virtualization,
clients can consolidate their workloads and reduce the footprint in
their data center. In addition, clients can run mixed workloads with
traditional SAP and nonproduction workloads running in a shared pool
side by side with Production SAP HANA, leading to an efficient use of
the system and a high utilization. SAP HANA Tailored Datacenter
Integration Phase 5 (TDI5) gives clients the flexibility to use the
storage and networking of their choice, and change configurations,
with support from SAP, all while achieving a lower TCO.

The Power H924 for SAP HANA server supports a maximum of 32 DDR4
ECC DIMM slots.
Memory features supported are 8 GB, 16 GB, 32 GB, 64 GB, and 128 GB
and run at different speeds of 2133, 2400, and 2666 Mbps, offering a
maximum system memory of 4096 GB.

One RDX bay (only available with x12 disk bays, not available with
x18 disk bays)

PCIe3 NVMe carrier card with two M.2 module slots

One front and two rear USB 3.0 ports

Service processor

2+2 Redundant hot-plug AC power supplies in each enclosure

19-inch rack-mount 4U configuration

PowerVM

Model abstract 9223-42H

The Power H924 for SAP HANA server
supports two processor sockets, offering 8-core or
16-core typical 3.8 to 4.0 GHz (max), 10-core or 20-core typical 3.5 to
3.9 GHz (max), 12-core or 24-core typical 3.4 to 3.9 GHz (max)
configurations in a 19-inch rack-mount, 4U (EIA units) drawer
configuration. All the cores are active. The Power S924 server supports a
maximum of 32 DDR4 DIMM slots. Memory features supported are 8 GB, 16 GB,
32 GB, 64 GB, and 128 GB and run at different speeds of 2133, 2400, and
2666 Mbps, offering a maximum system memory of 4096 GB.
Back to top

IBM Power Systems are designed for memory-intensive workloads like
SAP HANA. These highly flexible systems with best-in-class
virtualization give clients the ability to consolidate their workloads
and can help to reduce the footprint in their data center.

Help guard against security threats because the server's features,
reliability, and performance.

Harness the integrated virtualization capabilities of the server
to rapidly deploy, optimize, and recover workloads.

Migrate from previous Power Systems servers with Live Partition
Mobility capabilities. Every new Power H924 server comes with a
temporary IBM PowerVM license for your old server to support a
seamless move to IBM POWER9 technology-based servers.

Use this cloud-enabled server to build an agile, containerized
cloud on a server platform that is optimized for data and cognitive
services.

Extend IBM i, the integrated operating system, and connect to the
cognitive capabilities of the IBM Cloud using secure APIs.

The IBM Power System H924 (9223-42H) is a powerful 2-socket server
and is an ideal system for SAP HANA. With best-in-class
virtualization and up to 4096 GB of DDR4 ECC memory, this system can
be used as a building block for SAP HANA clusters. The Power System
H924 server ships with up to 24 activated cores and I/O configuration
flexibility to meet today's growth and tomorrow's processing needs.
The server features:

The POWER9 scale-out family is the first set of entry servers that
comes completely cloud-enabled out of the box with integrated PowerVM
Enterprise capabilities. Additionally, on-chip analytics and
algorithms help clients run their workloads at an optimized processor
frequency for performance and throughput. In combination with the
DDR4 memory footprint of 4 TB, IBM provides systems that are unmatched
by the competition in terms of memory scaling as well as the core to
memory ratio needed for data-centric and in-memory workloads. Live
Partition Mobility capabilities are built in, to cloud-enable your
POWER9 infrastructure and help you migrate from previous Power
Systems. Every new H924 also has the option of a temporary PowerVM
license for your old server to support a seamless move of workloads to
POWER9. The Power System H924 server has built-in security that can
help you be ready for current and future security threats.

Up to two PCIe3 NVMe carrier cards with two M.2 module slots (with
up to four Mainstream 400 GB SSD NVMe M.2 modules)

Quantity of one PCIe3 NVMe carrier card can be ordered only with a
storage backplane. If PCIe3 NVMe carrier card is ordered with a
storage backplane, then the optional split feature is not supported.

PCIe slots with single processor:

One x16 Gen4 full-height, half-length (CAPI)

One x8 Gen4, full-height, half-length (with x16 connector) (CAPI)

Two x8 Gen3, full-height, half-length (with x16 connectors)

Four x8 Gen3 full-height, half-length (One of these slots is used
for the required base LAN adapter.)

PCIe slots with two processors:

Three x16 Gen4 full-height, half-length (CAPI)

Two x8 Gen4 full-height, half-length (with x16 connectors) (CAPI)

Two x8 Gen3 full-height, half-length (with x16 connectors)

Four x8 Gen3 full-height, half-length (One of these slots is used
for the required base LAN adapter.)

Integrated:

Service processor

EnergyScale technology

Hot-swap and redundant cooling

One front USB 3.0 ports

Two rear USB 3.0 ports

Two HMC 1GbE RJ45 ports

One system port with RJ45 connector

Four hot-plug, redundant power supplies

19-inch rack-mounting hardware (4U)

PowerVM

PowerVM, which delivers industrial-strength virtualization for AIX
and Linux environments on POWER processor-based systems, has been
enhanced with a virtualization-oriented performance monitor, and
performance statistics are available through the HMC. These
performance statistics can be used to understand the workload
characteristics and to prepare for capacity planning.

PowerVM is included with the 9223-42H and 9223-22H. PowerVM includes
VIOS and it addresses any IBM i requirement for features that require
VIOS.

H924 SW tier for IBM i

IBM i SW tier is P20.

The IBM i QPRCFEAT number is the same numeric value as the
processor feature code.

Power H924 system configuration

The minimum Power H924 initial order must include a processor module,
base memory is 2x 8 GB DIMMs (#EM6G) with one socket installed and
4x 8 GB DIMMs (#EM6G) with two sockets installed (2 per socket),
four power supplies and line cords, an operating system
indicator, a cover set indicator, and a Language Group Specify. Also, it
must include one of these storage options and one of these network
options:

Storage options:

For boot from NVMe: One NVMe carrier and one NVMe M.2 Module.

For boot from local SFF-3 HDD/SDD: One storage backplane and one
SFF-3 HDD or SDD.

For boot from SAN: Internal HDD or SSD and RAID cards are not
required if feature 0837 (Boot from SAN) is selected. A Fibre Channel
adapter must be ordered if feature 0837 is selected.

Network options:

One PCIe2 4-port 1 Gb Ethernet adapter.

One of the supported 10 Gb Ethernet adapters

AIX or Linux is the primary operating system. The minimum defined
initial order configuration is as follows:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

If NVMe carrier card feature EC59 is selected, no disk units are
required to be ordered. If neither feature EC59 nor feature 0837 (SAN
boot) is ordered, then at least one disk unit is required to be
ordered. If no HDD/SSD/SAN boot (0837) is ordered, then feature EC59
(with at least one of #ES14) is the load source.

One PCIe2 4-port 1 GbE Adapter (#5899) is defaulted. Options for
servers with AIX and Linux as the primary operating system are one of
a 10 Gb Ethernet adapter, either feature EC2S, EC2U, EN0H, EN0K, EN0S,
EN0U, EN0W, or EN15.

The minimum defined initial order configuration, if no choice is
made, when IBM i is the primary operating system, is:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

IBM i operating system performance: Clients with write-sensitive
disk/HDD workloads should upgrade from the feature EJ1C/EJ1E base
storage backplane to the feature EJ1M/EJ1D expanded function storage
backplanes to gain the performance advantage of write cache.

Processor modules

A maximum of two processors with eight processor cores (#EP1V), or
two processors with ten processor cores (#EP1W), or two processors with
twelve processor cores (#EP1X) is allowed. All processor cores must be
activated. The following defines the allowed quantities of processor
activation entitlements.

Four power cords are required. A maximum of two feature 6458 cords
is allowed on the system unless a valid I/O drawer or tower is
attached to the system. The Power H924 server supports power cord 4.3
m (14 ft), Drawer to Wall/IBM PDU (250V/10A) in the base shipment
group. See the feature listing for other options.

PCIe slots

The Power H924 server has up to 11 PCIe hot-plug slots, providing
excellent configuration flexibility and expandability. For more
information about PCIe slots, see the I/O expansion drawer section.

With one POWER9 processor SCM, eight PCIe slots are available. One
is x16 Gen4 full-height, half-length slot (CAPI), one is x8 Gen4 full-
height, half-length slot (with x16 connector) (CAPI), two are x8 Gen3
full-height, half-length slots (with x16 connectors), and four are x8
Gen3 full-height, half-length slots (one of these slots is used for
the required base LAN adapter).

The x16 slots can provide up to twice the bandwidth of x8 slots
because they offer twice as many PCIe lanes. PCIe Gen4 slots can
support up to twice the bandwidth of a PCIe Gen3 slot and PCIe Gen3
slots can support up to twice the bandwidth of a PCIe Gen2 slot,
assuming an equivalent number of PCIe lanes.

At least one PCIe Ethernet adapter is required on the server by IBM
to ensure proper manufacture, test, and support of the server. One of
the x8 PCIe slots is used for this required adapter.

These servers are smarter about energy efficiency when cooling the
PCIe adapter environment. They sense which IBM PCIe adapters are
installed in their PCIe slots and if an adapter requires higher levels
of cooling, they automatically speed up fans to increase airflow
across the PCIe adapters. Note that faster fans increase the sound
level of the server. Higher wattage PCIe adapters include the PCIe3
SAS adapters and SSD/flash PCIe adapters (#EJ10, #EJ14, and #EJ0J).

The backplane options provide SFF-3 SAS bays in the system unit.
These 2.5-inch or small form factor (SFF) SAS bays can contain SAS
drives (HDD or SSD) mounted on a Gen3 tray or carrier. Thus the
drives are designated SFF-3. SFF-1 or SFF-2 drives do not fit in an
SFF-3 bay. All SFF-3 bays support concurrent maintenance or hot-plug
capability.

These backplane options use leading-edge, integrated SAS RAID
controller technology designed and patented by IBM. A custom-designed
PowerPC based ASIC chip is the basis of these SAS RAID controllers and
provides RAID 5 and RAID 6 performance levels, especially for SSD.
Internally, SAS ports are implemented and provide plenty of bandwidth.
The integrated SAS controllers are placed in dedicated slots and do
not reduce the number of available PCIe slots.

By optionally adding the feature EJ1E Split Backplane, a second
integrated SAS controller with no write cache is provided, and the
twelve SSF-3 bays are logically divided into two sets of six bays.
Each SAS controller independently runs one of the six-bay sets of
drives.

This backplane option supports HDDs or SSDs or a mixture of HDDs
and SSDs in the SFF-3 bays. "Mixing" HDDs and SSDs applies even
within a single set of six bays of the split backplane option. Note,
if mixing HDDs and SSDs, they must be in separate arrays.

This backplane option can offer different drive protection options:
RAID 0, RAID 5, RAID 6, or RAID 10. RAID 5 requires a minimum of
three drives of the same capacity. RAID 6 requires a minimum of four
drives of the same capacity. RAID 10 requires a minimum of two
drives. Hot spare capability is supported with RAID 5, or RAID 6, or
RAID 10.

Note that RAID 5 and RAID 6 result in more drive write activity
than mirroring or than unprotected drives.

This backplane option is supported by AIX, Linux, VIOS, and IBM i.
It is highly recommended but not required that the drives be
protected. With IBM i, all drives are required to be protected by
either RAID or Mirroring.

If the client needs a change after the server is installed, the
backplane option can be changed. For example, the feature EJ1E split
backplane feature can be added to an existing feature EJ1C backplane.

Unlike the hot-plug PCIe slots and SAS bays, concurrent maintenance
is not available for the integrated SAS controllers. Scheduled
downtime is required if a service action is required for these
integrated resources.

In addition to supporting HDDs and SSDs in the SFF-3 SAS bays, the
Expanded Function Storage Backplanes (#EJ1D and #EJ1M) support the
optional attachment of an EXP12SX/EXP24SX drawer in mode 1. For these
expanded function backplanes, all bays are accessed by both of the
integrated SAS controllers. The bays support concurrent maintenance
(hot-plug).

Cable management arm

A folding arm is attached to the server's rails at the rear of the
server. The server's power cords and the cables from the PCIe
adapters or integrated ports run through the arm and into the rack.
The arm enables the server to be pulled forward on its rails for
service access to PCIe slots, memory, processors, and so on without
disconnecting the cables from the server. Approximately 1 meter (3
feet) of cord/cable length is needed for the arm.

Integrated I/O ports

In addition to the integrated SAS controllers and SAS ports
associated with the storage backplane, there are two HMC ports, one
system port, and three USB ports. The two HMC ports are RJ45
supporting 1 Gb Ethernet connections.

The one system port is RJ45 and is supported by AIX and Linux for
attaching serial devices such as an asynchronous devices like a
console. If the device does not have an RJ45 connection, a converter
cable such as feature 3930 can provide a 9-pin D-shell connection.
Note that serial devices can have very individual characteristics
(different pin outs), and the feature 3930 may not be appropriate for
all possible devices. In this case, the user should acquire an OEM
converter cable appropriate for their device.

Three USB-3 ports are available for general client use; one is
located in front and two in the rear. Additionally, there are two
USB-2 ports in the service processor located in the rear of the
system. These ports are for limited client use. A converter cable
ECCF provides a USB-to-9-pin D-Shell connection for this function.

Rack-integrated system with I/O Expansion Drawer

Regardless of the rack-integrated system to which the PCIe Gen3 I/O
Expansion Drawer is attached to, if the Expansion Drawer is ordered as
factory integrated, the PDUs in the rack will be defaulted to be
placed horizontally to enhance cable management.

Expansion Drawers complicate the access to vertical PDUs if located
at the same height. IBM recommends accommodating PDUs horizontally on
racks containing one or more PCIe Gen3 I/O Expansion Drawers.

After the rack with expansion drawers is delivered to the client,
the client is allowed to rearrange the PDUs from horizontal to
vertical. However, the configurator will continue to consider the
PDUs as being placed horizontally for the matter of calculating the
free space still available in the rack.

Vertical PDUs can be used only if CSRP (#0469) is on the order.
When specifying CSRP, the client will provide the locations where the
PCIe Gen3 I/O Expansion Drawers must be placed, avoiding locating
those adjacent to vertical PDU locations, EIA 6 through 16 and 21
through 31.

The I/O expansion drawer can be migrated from a POWER8 to a POWER9
processor-based system. Only I/O cards supported on POWER9 in the I/O
expansion drawer are allowed.Clients migrating the I/O expansion drawer
configuration might have one or two PCIe3 6-slot fanout modules (#EMXF or
#EMXG) installed in the rear of the I/O expansion drawer. For a 4U server
configuration with two processor modules, up to two I/O expansion drawers
and three fanout modules are supported (the right PCIe module bay for the
second I/O expansion drawer must be populated by a filler module). For a
4U server configuration with one processor module, up to one I/O
expansion drawer and one fanout module are supported (the right PCIe
module bay must be populated by a filler module).

RDX docking station

The RDX docking station EU04 accommodates RDX removable disk
cartridges of any capacity. The disk is in a protective rugged cartridge
enclosure that plugs into the docking station. The docking station holds
one removable rugged disk drive/cartridge at a time. The rugged removable
disk cartridge and docking station performs saves, restores, and backups
similar to a tape drive. This docking station can be an excellent entry
capacity/performance option.

EXP24SX SAS Storage Enclosure (#ESLS/#ELLS)

The EXP24SX is a storage expansion enclosure with twenty-four
2.5-inch SFF SAS bays. It supports up to 24 hot-plug HDDs or SSDs in
only 2 EIA of space in a 19-inch rack. The EXP24SX SFF bays use SFF
Gen2 (SFF-2) carriers or trays.

The EXP24SX drawer feature ESLS is supported on the Power H922 and
H924 servers by AIX, IBM i, Linux, and VIOS. The EXP24SX drawer
feature ELLS is supported on the Linux-only Power L922 server.

With AIX/Linux/VIOS, the EXP24SX can be ordered with four sets of
six bays (mode 4), two sets of twelve bays (mode 2), or one set of
twenty-four bays (mode 1). With IBM i, only one set of twenty-four
bays (mode 1) is supported. It is possible to change the mode setting
in the field using software commands along with a specifically
documented procedure. The predecessor EXP24S did not support this
mode change in the field.

Important: When changing modes, a skilled, technically
qualified person should follow the special documented procedures.
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 reconfiguration work.

Four mini-SAS HD ports on the EXP24SX are attached to PCIe Gen3 SAS
adapters or attached to an integrated SAS controller in a POWER9
scale-out server such as the Power H922 or H924 servers. The
following PCIe3 SAS adapters support the EXP24SX:

Earlier generation PCIe2 or PCIe1 SAS adapters are not supported
with the EXP24SX.

The attachment between the EXP24SX and the PCIe3 SAS adapters or
integrated SAS controllers is through SAS YO12 or X12 cables. X12 and
YO12 cables are designed to support up to 12 Gb SAS. The PCIe Gen3
SAS adapters support up to 6 Gb throughput. The EXP24SX has been
designed to support up to 12 Gb throughput if future SAS adapters
support that capability. All ends of the YO12 and X12 cables have
mini-SAS HD narrow connectors. Cable options are:

X12 cable: 3-meter copper (#ECDJ)

YO12 cables: 1.5-meter copper (#ECDT), 3-meter copper (#ECDU)

3M 100 GbE Optical Cable QSFP28 (AOC) (#EB5R)

5M 100 GbE Optical Cable QSFP28 (AOC) (#EB5S)

10M 100 GbE Optical Cable QSFP28 (AOC) (#EB5T)

15M 100 GbE Optical Cable QSFP28 (AOC) (#EB5U)

20M 100 GbE Optical Cable QSFP28 (AOC) (#EB5V)

30M 100 GbE Optical Cable QSFP28 (AOC) (#EB5W)

50M 100 GbE Optical Cable QSFP28 (AOC) (#EB5X)

100M 100 GbE Optical Cable QSFP28 (AOC) (#EB5Y)

An AA12 cable interconnecting a pair of PCIe3 12 GB cache adapters
(two #EJ14) is not attached to the EXP24SX. These higher-bandwidth
cables could support 12 Gb throughput if future adapters support that
capability. Copper feature ECE0 is 0.6 meters long, ECE3 is 3 meters
long, and optical AA12 feature ECE4 is 4.5-meter long.

One no-charge specify code is used with each EXP24SX I/O Drawer
(#ESLS/#ELLS) to communicate to IBM configurator tools and IBM
Manufacturing which mode setting, adapter, and SAS cable are needed.
With this specify code, no hardware is shipped. The physical
adapters, controllers, and cables must be ordered with their own
chargeable feature numbers. There are more technically supported
configurations than are represented by these specify codes. IBM
Manufacturing and IBM configurator tools such as e-config only
understand and support EXP24SX configurations represented by these
specify codes.

All of the above EXP24SX specify codes assume a full set of
adapters and cables able to run all the SAS bays configured. The
following specify codes communicate to IBM Manufacturing a lower-cost
partial configuration is to be configured where the ordered adapters
and cables can run only a portion of the SAS bays. The future MES
addition of adapters and cables can enable the remaining SAS bays for
growth. The following specify codes are used:

An EXP24SX drawer in mode 4 can be attached to two or four SAS
controllers and provide a great deal of configuration flexibility.
For example, if using unpaired feature EJ0J adapters, these EJ0J
adapters could be in the same server in the same partition, same
server in different partitions, or even different servers.

An EXP24SX drawer in mode 2 has similar flexibility. If the I/O
drawer is in mode 2, then half of its SAS bays can be controlled by
one pair of PCIe3 SAS adapters, such as a 12 GB write cache adapter
pair (#EJ14), and the other half can be controlled by a different
PCIe3 SAS 12 GB write cache adapter pair or by zero-write-cache PCIe3
SAS adapters.

Note that for simplicity, IBM configurator tools such as e-config
assume that the SAS bays of an individual I/O drawer are controlled by
one type of SAS adapter. As a client, you have more flexibility than
e-config understands.

A maximum of twenty-four 2.5-inch SSDs or 2.5-inch HDDs is
supported in the EXP24SX 24 SAS bays. There can be no mixing of HDDs
and SSDs in the same mode 1 drawer. HDDs and SSDs can be mixed in a
mode 2 or mode 4 drawer, but they cannot be mixed within a logical
split of the drawer. For example, in a mode 2 drawer with two sets of
12 bays, one set could hold SSDs and one set could hold HDDs, but you
cannot mix SSDs and HDDs in the same set of 12 bays.

The indicator feature EHS2 helps IBM Manufacturing understand where
SSDs are placed in a mode 2 or a mode 4 EXP24SX drawer. On one mode 2
drawer, use a quantity of one feature EHS2 to have SSDs placed in just
half the bays, and use two EHS2 features to have SSDs placed in any of
the bays. Similarly, on one mode 4 drawer, use a quantity of one,
two, three, or four EHS2 features to indicate how many bays can have
SSDs. With multiple EXP24SX orders, IBM Manufacturing will have to
guess which quantity of feature ESH2 is associated with each EXP24SX.
Consider using CSP (#0456) to reduce guessing.

Two-and-a-half-inch small form factor (SFF) SAS HDDs and SSDs are
supported in the EXP24SX. All drives are mounted on Gen2
carriers/trays and thus named SFF-2 drives.

The EXP24SX drawer has many high-reliability design points:

SAS drive bays that support hot swap

Redundant and hot-plug-capable power and fan assemblies

Dual line cords

Redundant and hot-plug enclosure service modules (ESMs)

Redundant data paths to all drives

LED indicators on drives, bays, ESMs, and power supplies that
support problem identification

Through the SAS adapters/controllers, drives that can be protected
with RAID and mirroring and hot-spare capability

Order two ESLA features for AC power supplies. The enclosure is
shipped with adjustable depth rails and can accommodate 19-inch rack
depths from 59.5 - 75 cm (23.4 - 29.5 in.). Slot filler panels are
provided for empty bays when initially shipped from IBM.

EXP12SX SAS Storage Enclosure (#ESLL/#ELLL)

The EXP12SX is a storage expansion enclosure with twelve 3.5-inch
LFF SAS bays. It supports up to 12 hot-plug HDDs in only 2 EIA of
space in a 19-inch rack. The EXP12SX SFF bays use LFF Gen1 (LFF-1)
carriers/trays. The 4k byte sector drives (#4096 or #4224) are
supported. SSDs are not supported.

The EXP12SX drawer feature ESLL is supported on the Power H922 and
H924 servers by AIX, Linux, and VIOS. The EXP24SX drawer feature ELLL
is supported on the Linux-only Power L922 server.

With AIX/Linux/VIOS, the EXP12SX enclosure can be ordered with four
sets of three bays (mode 4), two sets of six bays (mode 2), or one set
of twelve bays (mode 1). The mode setting can be changed in the field
using software commands along with a specifically documented
procedure.

Important: When changing modes, it is very important
that you follow the documented procedures. 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 reconfiguration work.

Four mini-SAS HD ports on the EXP12SX are attached to PCIe Gen3 SAS
adapters or attached to an integrated SAS controller in a POWER9
scale-out server such as the Power H922 or H924 server. The following
PCIe3 SAS adapters support the EXP12SX:

Earlier generation PCIe2 or PCIe1 SAS adapters are not supported
with the EXP12SX drawer.

The EXP12SX drawer and the PCIe3 SAS adapters or integrated SAS
controllers are attached through SAS YO12 or X12 cables. X12 and YO12
cables are designed to support up to 12 Gb. The PCIe Gen3 SAS
adapters support up to 6 Gb throughput. The EXP12SX has been designed
to support up to 12 Gb throughput if future SAS adapters support that
capability. All ends of the YO12 and X12 cables have mini-SAS HD
narrow connectors. Cable options are:

X12 cable: 3-meter copper (#ECDJ)

YO12 cables: 1.5-meter copper (#ECDT), 3-meter copper (#ECDU)

3M 100 GbE Optical Cable QSFP28 (AOC) (#EB5R)

5M 100 GbE Optical Cable QSFP28 (AOC) (#EB5S)

10M 100 GbE Optical Cable QSFP28 (AOC) (#EB5T)

15M 100 GbE Optical Cable QSFP28 (AOC) (#EB5U)

20M 100 GbE Optical Cable QSFP28 (AOC) (#EB5V)

30M 100 GbE Optical Cable QSFP28 (AOC) (#EB5W)

50M 100 GbE Optical Cable QSFP28 (AOC) (#EB5X)

100M 100 GbE Optical Cable QSFP28 (AOC) (#EB5Y)

An AA12 cable interconnecting a pair of PCIe3 12 GB cache adapters
(two #EJ14) is not attached to the EXP12SX drawer. These higher-
bandwidth cables could support 12 Gb throughput if future adapters
support that capability. Copper feature ECE0 is 0.6-meter long,
feature ECE3 is 3-meter long, and optical AA12 feature ECE4 is
4.5-meter long.

One no-charge specify code is used with each EXP12SX I/O Drawer
(#ELLL/#ESLL) to communicate to IBM configurator tools and IBM
Manufacturing which mode setting, adapter, and SAS cable are needed.
With this specify code, no hardware is shipped. The physical
adapters, controllers, and cables must be ordered with their own
chargeable feature numbers. There are more technically supported
configurations than are represented by these specify codes. IBM
Manufacturing and IBM configurator tools such as e-config only
understand and support EXP12SX configurations represented by these
specify codes.

All of the above EXP12SX specify codes assume a full set of
adapters and cables able to run all the SAS bays configured. The
following specify codes communicate to IBM Manufacturing a lower cost,
partial configuration is to be configured where the ordered adapters
and cables can run only a portion of the SAS bays. The future MES
addition of adapters and cables can enable the remaining SAS bays for
growth. The following specify codes are used:

An EXP12SX drawer in mode 4 can be attached to two or four SAS
controllers and provide a great deal of configuration flexibility.
For example, if using unpaired feature EJ0J adapters, these EJ0J
adapters could be in the same server in the same partition, same
server in different partitions, or even different servers.

An EXP12SX drawer in mode 2 has similar flexibility. If the I/O
drawer is in mode 2, then half of its SAS bays can be controlled by
one pair of PCIe3 SAS adapters, such as a 12 GB write cache adapter
pair (#EJ14), and the other half can be controlled by a different
PCIe3 SAS 12 GB write cache adapter pair or by zero-write-cache PCIe3
SAS adapters.

Note that for simplicity, IBM configurator tools such as e-config
assume that the SAS bays of an individual I/O drawer are controlled by
one type of SAS adapter. As a client, you have more flexibility than
e-config understands.

The 3.5-inch large form factor (LFF) SAS HDDs are supported in the
EXP24SX. All drives are mounted on Gen1 carriers/trays and thus named
LFF-1 drives. Only 4k byte sector drives are supported in the EXP24SX
drawer. The 5xx byte sector drives are not announced or planned.
Drives are 7200 rpm and sometimes referred to as nearline.
These drives provide excellent cost per gigabyte. Note that
formatting or rebuilding arrays on large disk drives can take hours.
If higher performance is required, consider higher rpm disks or SSDs
in the EXP24SX drawer.

LED indicators on drives, bays, ESMs, and power supplies that
support problem identification

Through the SAS adapters/controllers, drives that can be protected
with RAID and mirroring and hot-spare capability

Order two ESLA features for AC power supplies. The enclosure is
shipped with adjustable depth rails and can accommodate 19-inch rack
depths from 59.5 - 75 cm (23.4 - 29.5 in.). Slot filler panels are
provided for empty bays when initially shipped from IBM.

EXP24SX and EXP12SX enclosures can be mixed on the same server.
EXP24SX and EXP12SX enclosures can be mixed on the same PCIe3 adapter.

PCIe Gen3 I/O Drawer Cabling Option

A copper cabling option (#ECCS) is available for the scale-out
servers. The cable option offers a much lower-cost connection between
the server and the PCIe Gen3 I/O drawer fanout modules. The currently
available Active Optical Cable (AOC) offers much longer length cables,
providing rack placement flexibility. Plus AOC cables are much
thinner and have tighter bend radius and thus are much easier to cable
in the rack.

The 3M Copper CXP Cable Pair (#ECCS) has the same performance and
same reliability, availability, and serviceability (RAS)
characteristics as the AOC cables. One copper cable length of 3 m is
offered. Note that the cable management arm of the scale-out servers
requires about 1 m of cable.

Like the AOC cable pair, the copper pair is cabled in the same
manner. One cable attaches to the top CXP port in the PCIe adapter in
the x16 PCIe slot in the server system unit and then attaches to the
top CXP port in the fanout module in the I/O drawer. Its cable pair
attaches to the bottom CXP port of the same PCIe adapter and to the
bottom CXP port of the same fanout module. Note that the PCIe adapter
providing the CXP ports on the server was named a PCIe3 "Optical"
Cable Adapter. In hindsight, this naming was unfortunate as the
adapter's CXP ports are not unique to optical. But at the time,
optical cables were the only connection option planned.

Copper and AOC cabling can be mixed on the same server. However,
they cannot be mixed on the same PCIe Gen3 I/O drawer or mixed on the
same fanout module.

Copper cables have the same operating system software prerequisites
as AOC cables.

High-function (switched and monitored) PDUs

The high-function PDUs (power distribution units) provide
switching, better monitoring, and 50% more C19 receptacles than
previous Power System PDUs. Depending on country wiring standards,
either two or four full-price features are orderable.

These PDUs can be mounted vertically in rack-side pockets or they
can be mounted horizontally. If mounted horizontally, they each use 1
EIA (1U) of rack space. See feature EPTH for horizontal mounting
hardware, which is used when IBM Manufacturing doesn't automatically
factory-install the PDU. 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. These PDUs do provide the same low price as the
low-function 12xC13 PDU feature (#7188).

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.

Memory subsystem RAS

The memory has error detection and correction circuitry designed
such that the failure of any one specific memory module within an ECC
word by itself can be corrected absent any other fault.

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 Systems family does ambient and over temperature
monitoring and reporting.

POWER9 processor functions

As in POWER8, the POWER9 processor has the ability to do processor
instruction retry for some transient errors.

Cache availability

The L2 and L3 caches in the POWER9 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. If the data is used, termination may be
limited to the program/kernel or hypervisor owning the data; or the
I/O adapters controlled by an I/O hub controller would freeze if data
were transferred to an I/O device.

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 Customer Set Up (CSU), Customer Installed Features
(CIF), and Customer Replaceable Units (CRU)

Error Detection and Fault Isolation (ED/FI)

First Failure Data Capture (FFDC)

Lightpath service indicators

Service labels and service diagrams available on the system and
delivered through IBM Knowledge Center

Step-by-step service procedures documented in IBM Knowledge Center
or available through the Hardware Management Console

Automatic reporting of serviceable events to IBM through the
Electronic Service Agent Call Home application

CRU videos planned to be available on the web at general
availability

Mobile access to important customer service functions available by
scanning a QR label

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 allows
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 POWER9 processor-based platforms 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.

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.

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

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 amber system fault LED, 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 locate and system locate
LEDs will occur. These enclosure LEDs will turn on solid and can be
used to follow the light path from the system to 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.

Because of the FFDC technology designed into IBM servers, it is not
necessary to perform re-create diagnostics for failures or 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.

Stand-alone diagnostics with PowerVM

As the name implies, stand-alone 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 is supported with PowerVM. Concurrent maintenance of
the Operator Panel is supported through ASMI. Additional concurrent
maintenance includes power supplies, fans, and HDD/SSD drives.

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, CPUs, processor books, fans,
adapter cards, LEDs, 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. Once the QR label is scanned, it
will go to a landing page specific to that server which contains many
of the service functions of interest while physically located at the
server. These include things such as installation and repair
instructions, service diagrams, reference code look up, and so on.

Packaging for service

The following service enhancements 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,
thumb-screws, 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. 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 Live Partition Mobility, users can migrate an AIX or IBM i
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.

Service processor

The service processor provides the capability to diagnose, check
the status of, and sense the operational conditions of a system. It
runs on its own power boundary and does not require resources from a
system processor to be operational to perform its tasks.

Under PowerVM, 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 service processors menus
(ASMI) can be accessed concurrently with system operation, allowing
nondisruptive abilities to change system default parameters.

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 HMC or most
non-HMC-managed systems through Electronic Service Agent running on
top of the operating system. 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. The Electronic Service Agent application can be
configured for automated call home. See the next section for specific
details on this application.

IBM Electronic Services

Electronic Service Agent and the IBM Electronic Services web portal
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, performance issues, and
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.

System configuration and inventory information collected by
Electronic Service Agent also can be viewed on the secure Electronic
Services web portal and 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 new 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
website.

Select your country.

Click "IBM Electronic Service Agent Connectivity Guide."

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 either through the internet (HTTPS or VPN) or modem to
provide clients a single point of exit from their site. Communication
is one way. Activating Electronic Service Agent does not enable IBM
to call into a client's system.

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.

Customized support

By using the IBMid entered during activation, clients can view
system and support information in the "My Systems" and "Premium
Search" sections of the Electronic Services website.

The Electronic Services web 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. The newly improved My Systems and Premium Search
functions make it even easier for Electronic Service Agent-enabled
clients to track system inventory and find pertinent fixes.

My Systems 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 IBMid. Premium Search combines the
function of search and the value of Electronic Service Agent
information, providing advanced search of the technical support
knowledgebase. Using Premium Search and the Service Agent information
that has been collected from the system, clients are able to see
search results that apply specifically to their systems.

Accessibility by people with disabilities

A US Section 508 Voluntary Product Accessibility Template (VPAT)
containing details on accessibility compliance can be found on the
Product accessibility information
website.

Section 508 of the US Rehabilitation Act

Power H924 (9223-42H) for SAP HANA server is capable as of March
20, 2018, when used in accordance with IBM's associated documentation,
of satisfying the applicable requirements of Section 508 of the
Rehabilitation Act, provided that any assistive technology used with
the product properly interoperates with it. A US Section 508
Voluntary Product Accessibility Template (VPAT) can be found on the
Product accessibility information
website.
Back to top

Get the best out of SAP HANA with Power Systems. Power Systems is
designed for data-intensive, in-memory workloads such as SAP HANA.
With powerful, built-in, virtualization, reliability that you can bet
your business on, and the performance that you expect from an
enterprise-grade platform, Power Systems is the platform for SAP HANA.

This highly flexible system with best-in-class virtualization can
help clients to consolidate their workloads and reduce the footprint
in their data centers. In addition, you can run mixed workloads with
traditional SAP and nonproduction workloads running in a shared pool
side by side with production SAP HANA, leading to an efficient use of
the system and a high utilization.

Power is supported for SAP HANA Tailored Datacenter Integration
Phase 5 (TDI5), which gives you the flexibility to use the storage and
networking of your choice, to change configurations, and have support
from SAP, all while achieving a lower TCO. This means you can use
nearly any Power System for SAP HANA, including H924, and re-use
storage and networking already on hand.

Scale-up or scale-out your SAP HANA workload while maintaining the
same level of flexibility. A separate purchase of SAP HANA is
required for this use case.
Back to top

Model summary matrix

Model

Processor

Processor sockets

Memory

42H

POWER9

Two

4096 GB

Customer setup (CSU)

Yes.

Devices supported

The 7226-1U3 that offers a 1U rack-mountable dual bay enclosure
with storage device options of LTO5, 6, 7,and 8 tape drives with both
SAS and Fiber Channel interface; the 7226 also offers DVD-RAM SAS and
USB drive features as well as RDX 500GB, 1TB, and 2TB drive options.
Up to two drives (or four DVD-RAM) can be installed in any combination
in the 7226 enclosure.

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.

Up to two PCIe3 NVMe carrier cards with two M.2 module slots (with
up to four Mainstream 400 GB SSD NVMe M.2 modules)

Quantity of one PCIe3 NVMe carrier card can be ordered only with a
storage backplane. If PCIe3 NVMe carrier card is ordered with a
storage backplane, then the optional split feature is not supported.

PCIe slots with single processor:

One x16 Gen4 full-height, half-length (CAPI)

One x8 Gen4, full-height, half-length (with x16 connector) (CAPI)

Two x8 Gen3, full-height, half-length (with x16 connectors)

Four x8 Gen3 full-height, half-length (One of these slots is used
for the required base LAN adapter.)

PCIe slots with two processors:

Three x16 Gen4 full-height, half-length (CAPI)

Two x8 Gen4 full-height, half-length (with x16 connectors) (CAPI)

Two x8 Gen3 full-height, half-length (with x16 connectors)

Four x8 Gen3 full-height, half-length (One of these slots is used
for the required base LAN adapter.)

Integrated:

Service processor

EnergyScale technology

Hot-swap and redundant cooling

One front USB 3.0 ports

Two rear USB 3.0 ports

Two HMC 1GbE RJ45 ports

One system port with RJ45 connector

Four hot-plug, redundant power supplies

19-inch rack-mounting hardware (4U)

PowerVM

PowerVM, which delivers industrial-strength virtualization for AIX
and Linux environments on POWER processor-based systems, has been
enhanced with a virtualization-oriented performance monitor, and
performance statistics are available through the HMC. These
performance statistics can be used to understand the workload
characteristics and to prepare for capacity planning.

H924 SW tier for IBM i

IBM i SW tier is P20.

The IBM i QPRCFEAT number is the same numeric value as the
processor feature code.

Power H924 system configuration

The minimum Power H924 initial order must include a processor module,
base memory is 2x 8 GB DIMMs (#EM6G) with one socket installed and
4x 8 GB DIMMs (#EM6G) with two sockets installed (2 per socket),
four power supplies and line cords, an operating system
indicator, a cover set indicator, and a Language Group Specify. Also, it
must include one of these storage options and one of these network
options:

Storage options:

For boot from NVMe: One NVMe carrier and one NVMe M.2 Module.

For boot from local SFF-3 HDD/SDD: One storage backplane and one
SFF-3 HDD or SDD.

For boot from SAN: Internal HDD or SSD and RAID cards are not
required if feature 0837 (Boot from SAN) is selected. A Fibre Channel
adapter must be ordered if feature 0837 is selected.

Network options:

One PCIe2 4-port 1 Gb Ethernet adapter.

One of the supported 10 Gb Ethernet adapters

AIX or Linux is the primary operating system. The minimum defined
initial order configuration is as follows:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

If NVMe carrier card feature EC59 is selected, no disk units are
required to be ordered. If neither feature EC59 nor feature 0837 (SAN
boot) is ordered, then at least one disk unit is required to be
ordered. If no HDD/SSD/SAN boot (0837) is ordered, then feature EC59
(with at least one of #ES14) is the load source.

One PCIe2 4-port 1 GbE Adapter (#5899) is defaulted. Options for
servers with AIX and Linux as the primary operating system are one of
a 10 Gb Ethernet adapter, either feature EC2S, EC2U, EN0H, EN0K, EN0S,
EN0U, EN0W, or EN15.

The minimum defined initial order configuration, if no choice is
made, when IBM i is the primary operating system, is:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

IBM i operating system performance: Clients with write-sensitive
disk/HDD workloads should upgrade from the feature EJ1C/EJ1E base
storage backplane to the feature EJ1M/EJ1D expanded function storage
backplanes to gain the performance advantage of write cache.

Processor modules

A maximum of two processors with eight processor cores (#EP1V), or
two processors with ten processor cores (#EP1W), or two processors with
twelve processor cores (#EP1X) is allowed. All processor cores must be
activated. The following defines the allowed quantities of processor
activation entitlements.

Four power cords are required. A maximum of two feature 6458 cords
is allowed on the system unless a valid I/O drawer or tower is
attached to the system. The Power H924 server supports power cord 4.3
m (14 ft), Drawer to Wall/IBM PDU (250V/10A) in the base shipment
group. See the feature listing for other options.

PCIe slots

The Power H924 server has up to 11 PCIe hot-plug slots, providing
excellent configuration flexibility and expandability. For more
information about PCIe slots, see the I/O expansion drawer section.

With one POWER9 processor SCM, eight PCIe slots are available. One
is x16 Gen4 full-height, half-length slot (CAPI), one is x8 Gen4 full-
height, half-length slot (with x16 connector) (CAPI), two are x8 Gen3
full-height, half-length slots (with x16 connectors), and four are x8
Gen3 full-height, half-length slots (one of these slots is used for
the required base LAN adapter).

The x16 slots can provide up to twice the bandwidth of x8 slots
because they offer twice as many PCIe lanes. PCIe Gen4 slots can
support up to twice the bandwidth of a PCIe Gen3 slot and PCIe Gen3
slots can support up to twice the bandwidth of a PCIe Gen2 slot,
assuming an equivalent number of PCIe lanes.

At least one PCIe Ethernet adapter is required on the server by IBM
to ensure proper manufacture, test, and support of the server. One of
the x8 PCIe slots is used for this required adapter.

These servers are smarter about energy efficiency when cooling the
PCIe adapter environment. They sense which IBM PCIe adapters are
installed in their PCIe slots and if an adapter requires higher levels
of cooling, they automatically speed up fans to increase airflow
across the PCIe adapters. Note that faster fans increase the sound
level of the server. Higher wattage PCIe adapters include the PCIe3
SAS adapters and SSD/flash PCIe adapters (#EJ10, #EJ14, and #EJ0J).

The backplane options provide SFF-3 SAS bays in the system unit.
These 2.5-inch or small form factor (SFF) SAS bays can contain SAS
drives (HDD or SSD) mounted on a Gen3 tray or carrier. Thus the
drives are designated SFF-3. SFF-1 or SFF-2 drives do not fit in an
SFF-3 bay. All SFF-3 bays support concurrent maintenance or hot-plug
capability.

These backplane options use leading-edge, integrated SAS RAID
controller technology designed and patented by IBM. A custom-designed
PowerPC based ASIC chip is the basis of these SAS RAID controllers and
provides RAID 5 and RAID 6 performance levels, especially for SSD.
Internally, SAS ports are implemented and provide plenty of bandwidth.
The integrated SAS controllers are placed in dedicated slots and do
not reduce the number of available PCIe slots.

By optionally adding the feature EJ1E Split Backplane, a second
integrated SAS controller with no write cache is provided, and the
twelve SSF-3 bays are logically divided into two sets of six bays.
Each SAS controller independently runs one of the six-bay sets of
drives.

This backplane option supports HDDs or SSDs or a mixture of HDDs
and SSDs in the SFF-3 bays. "Mixing" HDDs and SSDs applies even
within a single set of six bays of the split backplane option. Note,
if mixing HDDs and SSDs, they must be in separate arrays.

This backplane option can offer different drive protection options:
RAID 0, RAID 5, RAID 6, or RAID 10. RAID 5 requires a minimum of
three drives of the same capacity. RAID 6 requires a minimum of four
drives of the same capacity. RAID 10 requires a minimum of two
drives. Hot spare capability is supported with RAID 5, or RAID 6, or
RAID 10.

Note that RAID 5 and RAID 6 result in more drive write activity
than mirroring or than unprotected drives.

This backplane option is supported by AIX, Linux, VIOS, and IBM i.
It is highly recommended but not required that the drives be
protected. With IBM i, all drives are required to be protected by
either RAID or Mirroring.

If the client needs a change after the server is installed, the
backplane option can be changed. For example, the feature EJ1E split
backplane feature can be added to an existing feature EJ1C backplane.

Unlike the hot-plug PCIe slots and SAS bays, concurrent maintenance
is not available for the integrated SAS controllers. Scheduled
downtime is required if a service action is required for these
integrated resources.

In addition to supporting HDDs and SSDs in the SFF-3 SAS bays, the
Expanded Function Storage Backplanes (#EJ1D and #EJ1M) support the
optional attachment of an EXP12SX/EXP24SX drawer in mode 1. For these
expanded function backplanes, all bays are accessed by both of the
integrated SAS controllers. The bays support concurrent maintenance
(hot-plug).

Cable management arm

A folding arm is attached to the server's rails at the rear of the
server. The server's power cords and the cables from the PCIe
adapters or integrated ports run through the arm and into the rack.
The arm enables the server to be pulled forward on its rails for
service access to PCIe slots, memory, processors, and so on without
disconnecting the cables from the server. Approximately 1 meter (3
feet) of cord/cable length is needed for the arm.

Integrated I/O ports

In addition to the integrated SAS controllers and SAS ports
associated with the storage backplane, there are two HMC ports, one
system port, and three USB ports. The two HMC ports are RJ45
supporting 1 Gb Ethernet connections.

The one system port is RJ45 and is supported by AIX and Linux for
attaching serial devices such as an asynchronous devices like a
console. If the device does not have an RJ45 connection, a converter
cable such as feature 3930 can provide a 9-pin D-shell connection.
Note that serial devices can have very individual characteristics
(different pin outs), and the feature 3930 may not be appropriate for
all possible devices. In this case, the user should acquire an OEM
converter cable appropriate for their device.

Three USB-3 ports are available for general client use; one is
located in front and two in the rear. Additionally, there are two
USB-2 ports in the service processor located in the rear of the
system. These ports are for limited client use. A converter cable
ECCF provides a USB-to-9-pin D-Shell connection for this function.

Rack-integrated system with I/O Expansion Drawer

Regardless of the rack-integrated system to which the PCIe Gen3 I/O
Expansion Drawer is attached to, if the Expansion Drawer is ordered as
factory integrated, the PDUs in the rack will be defaulted to be
placed horizontally to enhance cable management.

Expansion Drawers complicate the access to vertical PDUs if located
at the same height. IBM recommends accommodating PDUs horizontally on
racks containing one or more PCIe Gen3 I/O Expansion Drawers.

After the rack with expansion drawers is delivered to the client,
the client is allowed to rearrange the PDUs from horizontal to
vertical. However, the configurator will continue to consider the
PDUs as being placed horizontally for the matter of calculating the
free space still available in the rack.

Vertical PDUs can be used only if CSRP (#0469) is on the order.
When specifying CSRP, the client will provide the locations where the
PCIe Gen3 I/O Expansion Drawers must be placed, avoiding locating
those adjacent to vertical PDU locations, EIA 6 through 16 and 21
through 31.

RDX docking station

The RDX docking station EU04 accommodates RDX removable disk
cartridges of any capacity. The disk is in a protective rugged cartridge
enclosure that plugs into the docking station. The docking station holds
one removable rugged disk drive/cartridge at a time. The rugged removable
disk cartridge and docking station performs saves, restores, and backups
similar to a tape drive. This docking station can be an excellent entry
capacity/performance option.

EXP24SX SAS Storage Enclosure (#ESLS/#ELLS)

The EXP24SX is a storage expansion enclosure with twenty-four
2.5-inch SFF SAS bays. It supports up to 24 hot-plug HDDs or SSDs in
only 2 EIA of space in a 19-inch rack. The EXP24SX SFF bays use SFF
Gen2 (SFF-2) carriers or trays.

The EXP24SX drawer feature ESLS is supported on the Power H922 and
H924 servers by AIX, IBM i, Linux, and VIOS. The EXP24SX drawer
feature ELLS is supported on the Linux-only Power L922 server.

With AIX/Linux/VIOS, the EXP24SX can be ordered with four sets of
six bays (mode 4), two sets of twelve bays (mode 2), or one set of
twenty-four bays (mode 1). With IBM i, only one set of twenty-four
bays (mode 1) is supported. It is possible to change the mode setting
in the field using software commands along with a specifically
documented procedure. The predecessor EXP24S did not support this
mode change in the field.

Important: When changing modes, a skilled, technically
qualified person should follow the special documented procedures.
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 reconfiguration work.

Four mini-SAS HD ports on the EXP24SX are attached to PCIe Gen3 SAS
adapters or attached to an integrated SAS controller in a POWER9
scale-out server such as the Power H922 or H924 servers. The
following PCIe3 SAS adapters support the EXP24SX:

Earlier generation PCIe2 or PCIe1 SAS adapters are not supported
with the EXP24SX.

The attachment between the EXP24SX and the PCIe3 SAS adapters or
integrated SAS controllers is through SAS YO12 or X12 cables. X12 and
YO12 cables are designed to support up to 12 Gb SAS. The PCIe Gen3
SAS adapters support up to 6 Gb throughput. The EXP24SX has been
designed to support up to 12 Gb throughput if future SAS adapters
support that capability. All ends of the YO12 and X12 cables have
mini-SAS HD narrow connectors. Cable options are:

X12 cable: 3-meter copper (#ECDJ)

YO12 cables: 1.5-meter copper (#ECDT), 3-meter copper (#ECDU)

3M 100 GbE Optical Cable QSFP28 (AOC) (#EB5R)

5M 100 GbE Optical Cable QSFP28 (AOC) (#EB5S)

10M 100 GbE Optical Cable QSFP28 (AOC) (#EB5T)

15M 100 GbE Optical Cable QSFP28 (AOC) (#EB5U)

20M 100 GbE Optical Cable QSFP28 (AOC) (#EB5V)

30M 100 GbE Optical Cable QSFP28 (AOC) (#EB5W)

50M 100 GbE Optical Cable QSFP28 (AOC) (#EB5X)

100M 100 GbE Optical Cable QSFP28 (AOC) (#EB5Y)

An AA12 cable interconnecting a pair of PCIe3 12 GB cache adapters
(two #EJ14) is not attached to the EXP24SX. These higher-bandwidth
cables could support 12 Gb throughput if future adapters support that
capability. Copper feature ECE0 is 0.6 meters long, ECE3 is 3 meters
long, and optical AA12 feature ECE4 is 4.5-meter long.

One no-charge specify code is used with each EXP24SX I/O Drawer
(#ESLS/#ELLS) to communicate to IBM configurator tools and IBM
Manufacturing which mode setting, adapter, and SAS cable are needed.
With this specify code, no hardware is shipped. The physical
adapters, controllers, and cables must be ordered with their own
chargeable feature numbers. There are more technically supported
configurations than are represented by these specify codes. IBM
Manufacturing and IBM configurator tools such as e-config only
understand and support EXP24SX configurations represented by these
specify codes.

All of the above EXP24SX specify codes assume a full set of
adapters and cables able to run all the SAS bays configured. The
following specify codes communicate to IBM Manufacturing a lower-cost
partial configuration is to be configured where the ordered adapters
and cables can run only a portion of the SAS bays. The future MES
addition of adapters and cables can enable the remaining SAS bays for
growth. The following specify codes are used:

An EXP24SX drawer in mode 4 can be attached to two or four SAS
controllers and provide a great deal of configuration flexibility.
For example, if using unpaired feature EJ0J adapters, these EJ0J
adapters could be in the same server in the same partition, same
server in different partitions, or even different servers.

An EXP24SX drawer in mode 2 has similar flexibility. If the I/O
drawer is in mode 2, then half of its SAS bays can be controlled by
one pair of PCIe3 SAS adapters, such as a 12 GB write cache adapter
pair (#EJ14), and the other half can be controlled by a different
PCIe3 SAS 12 GB write cache adapter pair or by zero-write-cache PCIe3
SAS adapters.

Note that for simplicity, IBM configurator tools such as e-config
assume that the SAS bays of an individual I/O drawer are controlled by
one type of SAS adapter. As a client, you have more flexibility than
e-config understands.

A maximum of twenty-four 2.5-inch SSDs or 2.5-inch HDDs is
supported in the EXP24SX 24 SAS bays. There can be no mixing of HDDs
and SSDs in the same mode 1 drawer. HDDs and SSDs can be mixed in a
mode 2 or mode 4 drawer, but they cannot be mixed within a logical
split of the drawer. For example, in a mode 2 drawer with two sets of
12 bays, one set could hold SSDs and one set could hold HDDs, but you
cannot mix SSDs and HDDs in the same set of 12 bays.

The indicator feature EHS2 helps IBM Manufacturing understand where
SSDs are placed in a mode 2 or a mode 4 EXP24SX drawer. On one mode 2
drawer, use a quantity of one feature EHS2 to have SSDs placed in just
half the bays, and use two EHS2 features to have SSDs placed in any of
the bays. Similarly, on one mode 4 drawer, use a quantity of one,
two, three, or four EHS2 features to indicate how many bays can have
SSDs. With multiple EXP24SX orders, IBM Manufacturing will have to
guess which quantity of feature ESH2 is associated with each EXP24SX.
Consider using CSP (#0456) to reduce guessing.

Two-and-a-half-inch small form factor (SFF) SAS HDDs and SSDs are
supported in the EXP24SX. All drives are mounted on Gen2
carriers/trays and thus named SFF-2 drives.

The EXP24SX drawer has many high-reliability design points:

SAS drive bays that support hot swap

Redundant and hot-plug-capable power and fan assemblies

Dual line cords

Redundant and hot-plug enclosure service modules (ESMs)

Redundant data paths to all drives

LED indicators on drives, bays, ESMs, and power supplies that
support problem identification

Through the SAS adapters/controllers, drives that can be protected
with RAID and mirroring and hot-spare capability

Order two ESLA features for AC power supplies. The enclosure is
shipped with adjustable depth rails and can accommodate 19-inch rack
depths from 59.5 - 75 cm (23.4 - 29.5 in.). Slot filler panels are
provided for empty bays when initially shipped from IBM.

EXP12SX SAS Storage Enclosure (#ESLL/#ELLL)

The EXP12SX is a storage expansion enclosure with twelve 3.5-inch
LFF SAS bays. It supports up to 12 hot-plug HDDs in only 2 EIA of
space in a 19-inch rack. The EXP12SX SFF bays use LFF Gen1 (LFF-1)
carriers/trays. The 4k byte sector drives (#4096 or #4224) are
supported. SSDs are not supported.

The EXP12SX drawer feature ESLL is supported on the Power H922 and
H924 servers by AIX, Linux, and VIOS. The EXP24SX drawer feature ELLL
is supported on the Linux-only Power L922 server.

With AIX/Linux/VIOS, the EXP12SX enclosure can be ordered with four
sets of three bays (mode 4), two sets of six bays (mode 2), or one set
of twelve bays (mode 1). The mode setting can be changed in the field
using software commands along with a specifically documented
procedure.

Important: When changing modes, it is very important
that you follow the documented procedures. 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 reconfiguration work.

Four mini-SAS HD ports on the EXP12SX are attached to PCIe Gen3 SAS
adapters or attached to an integrated SAS controller in a POWER9
scale-out server such as the Power H922 or H924 server. The following
PCIe3 SAS adapters support the EXP12SX:

Earlier generation PCIe2 or PCIe1 SAS adapters are not supported
with the EXP12SX drawer.

The EXP12SX drawer and the PCIe3 SAS adapters or integrated SAS
controllers are attached through SAS YO12 or X12 cables. X12 and YO12
cables are designed to support up to 12 Gb. The PCIe Gen3 SAS
adapters support up to 6 Gb throughput. The EXP12SX has been designed
to support up to 12 Gb throughput if future SAS adapters support that
capability. All ends of the YO12 and X12 cables have mini-SAS HD
narrow connectors. Cable options are:

X12 cable: 3-meter copper (#ECDJ)

YO12 cables: 1.5-meter copper (#ECDT), 3-meter copper (#ECDU)

3M 100 GbE Optical Cable QSFP28 (AOC) (#EB5R)

5M 100 GbE Optical Cable QSFP28 (AOC) (#EB5S)

10M 100 GbE Optical Cable QSFP28 (AOC) (#EB5T)

15M 100 GbE Optical Cable QSFP28 (AOC) (#EB5U)

20M 100 GbE Optical Cable QSFP28 (AOC) (#EB5V)

30M 100 GbE Optical Cable QSFP28 (AOC) (#EB5W)

50M 100 GbE Optical Cable QSFP28 (AOC) (#EB5X)

100M 100 GbE Optical Cable QSFP28 (AOC) (#EB5Y)

An AA12 cable interconnecting a pair of PCIe3 12 GB cache adapters
(two #EJ14) is not attached to the EXP12SX drawer. These higher-
bandwidth cables could support 12 Gb throughput if future adapters
support that capability. Copper feature ECE0 is 0.6-meter long,
feature ECE3 is 3-meter long, and optical AA12 feature ECE4 is
4.5-meter long.

One no-charge specify code is used with each EXP12SX I/O Drawer
(#ELLL/#ESLL) to communicate to IBM configurator tools and IBM
Manufacturing which mode setting, adapter, and SAS cable are needed.
With this specify code, no hardware is shipped. The physical
adapters, controllers, and cables must be ordered with their own
chargeable feature numbers. There are more technically supported
configurations than are represented by these specify codes. IBM
Manufacturing and IBM configurator tools such as e-config only
understand and support EXP12SX configurations represented by these
specify codes.

All of the above EXP12SX specify codes assume a full set of
adapters and cables able to run all the SAS bays configured. The
following specify codes communicate to IBM Manufacturing a lower cost,
partial configuration is to be configured where the ordered adapters
and cables can run only a portion of the SAS bays. The future MES
addition of adapters and cables can enable the remaining SAS bays for
growth. The following specify codes are used:

An EXP12SX drawer in mode 4 can be attached to two or four SAS
controllers and provide a great deal of configuration flexibility.
For example, if using unpaired feature EJ0J adapters, these EJ0J
adapters could be in the same server in the same partition, same
server in different partitions, or even different servers.

An EXP12SX drawer in mode 2 has similar flexibility. If the I/O
drawer is in mode 2, then half of its SAS bays can be controlled by
one pair of PCIe3 SAS adapters, such as a 12 GB write cache adapter
pair (#EJ14), and the other half can be controlled by a different
PCIe3 SAS 12 GB write cache adapter pair or by zero-write-cache PCIe3
SAS adapters.

Note that for simplicity, IBM configurator tools such as e-config
assume that the SAS bays of an individual I/O drawer are controlled by
one type of SAS adapter. As a client, you have more flexibility than
e-config understands.

The 3.5-inch large form factor (LFF) SAS HDDs are supported in the
EXP24SX. All drives are mounted on Gen1 carriers/trays and thus named
LFF-1 drives. Only 4k byte sector drives are supported in the EXP24SX
drawer. The 5xx byte sector drives are not announced or planned.
Drives are 7200 rpm and sometimes referred to as nearline.
These drives provide excellent cost per gigabyte. Note that
formatting or rebuilding arrays on large disk drives can take hours.
If higher performance is required, consider higher rpm disks or SSDs
in the EXP24SX drawer.

LED indicators on drives, bays, ESMs, and power supplies that
support problem identification

Through the SAS adapters/controllers, drives that can be protected
with RAID and mirroring and hot-spare capability

Order two ESLA features for AC power supplies. The enclosure is
shipped with adjustable depth rails and can accommodate 19-inch rack
depths from 59.5 - 75 cm (23.4 - 29.5 in.). Slot filler panels are
provided for empty bays when initially shipped from IBM.

EXP24SX and EXP12SX enclosures can be mixed on the same server.
EXP24SX and EXP12SX enclosures can be mixed on the same PCIe3 adapter.

PCIe Gen3 I/O Drawer Cabling Option

A copper cabling option (#ECCS) is available for the scale-out
servers. The cable option offers a much lower-cost connection between
the server and the PCIe Gen3 I/O drawer fanout modules. The currently
available Active Optical Cable (AOC) offers much longer length cables,
providing rack placement flexibility. Plus AOC cables are much
thinner and have tighter bend radius and thus are much easier to cable
in the rack.

The 3M Copper CXP Cable Pair (#ECCS) has the same performance and
same reliability, availability, and serviceability (RAS)
characteristics as the AOC cables. One copper cable length of 3 m is
offered. Note that the cable management arm of the scale-out servers
requires about 1 m of cable.

Like the AOC cable pair, the copper pair is cabled in the same
manner. One cable attaches to the top CXP port in the PCIe adapter in
the x16 PCIe slot in the server system unit and then attaches to the
top CXP port in the fanout module in the I/O drawer. Its cable pair
attaches to the bottom CXP port of the same PCIe adapter and to the
bottom CXP port of the same fanout module. Note that the PCIe adapter
providing the CXP ports on the server was named a PCIe3 "Optical"
Cable Adapter. In hindsight, this naming was unfortunate as the
adapter's CXP ports are not unique to optical. But at the time,
optical cables were the only connection option planned.

Copper and AOC cabling can be mixed on the same server. However,
they cannot be mixed on the same PCIe Gen3 I/O drawer or mixed on the
same fanout module.

Copper cables have the same operating system software prerequisites
as AOC cables.

High-function (switched and monitored) PDUs

The high-function PDUs (power distribution units) provide
switching, better monitoring, and 50% more C19 receptacles than
previous Power System PDUs. Depending on country wiring standards,
either two or four full-price features are orderable.

These PDUs can be mounted vertically in rack-side pockets or they
can be mounted horizontally. If mounted horizontally, they each use 1
EIA (1U) of rack space. See feature EPTH for horizontal mounting
hardware, which is used when IBM Manufacturing doesn't automatically
factory-install the PDU. 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. These PDUs do provide the same low price as the
low-function 12xC13 PDU feature (#7188).

Note: The maximum measured value is the worst case power consumption
expected from a fully populated server under an intensive workload.
The maximum measured value also accounts for component tolerance and
non-ideal operating conditions. Power consumption and heat load vary
greatly by server configuration and utilization. The
IBM Systems Energy Estimator
should be used to
obtain a heat output estimate based on a specific configuration.

Placing multiple servers in a rack increases the total power noise
level coming from the rack

Placing servers in racks with acoustic doors reduces the power
noise levels.

EMC conformance classification

This equipment is subject to FCC rules and shall comply with the
appropriate FCC rules before final delivery to the buyer or centers of
distribution.

US: FCC Class A

Europe: CISPR 22 Class A

Japan: VCCI-A

Korea: Korean Requirement Class A

China: People's Republic of China commodity inspection law Class
A

Homologation -- Telecom environmental testing (Safety and
EMC):

Homologation approval for specific countries has been initiated
with the IBM Homologation and Type Approval (HT&A) organization in
LaGaude, France. This Power Systems model and applicable features
meet the environmental testing requirements of the country telecom and
have been designed and tested in compliance with the Full Quality
Assurance Approval (FQAA) process as delivered by the British Approval
Board for Telecom (BABT), the UK Telecom regulatory authority.

This product is not certified for connection by any means
whatsoever 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.

Integrated system port is not supported under AIX or Linux when
the HMC ports are connected to an HMC. Either the HMC ports or the
integrated system ports can be used, but not both. The FSP2 USB 2.0
port is used for communication to a UPS.

The integrated system port is supported for modem and TTY terminal
connections by AIX or Linux. Any other application using serial ports
requires a serial port adapter to be installed in a PCI slot. The
integrated system port does not support HACMP configurations.

Boot requirements

If IBM i (#2145) is selected as the primary operating system and
SAN boot is not selected (#0837), one of the following Load Source
specify codes must be specified.

If IBM i (#2145) is selected and the load source disk unit is not
in the CEC (system unit), one of the following specify codes must also
be selected:

#0719 Load Source Not in CEC and are to be placed in I/O drawers
or in external SAN-attached disk

The minimum Power H924 initial order must include a processor
module, two 16 GB DIMMs, four power supplies and line cords, an
operating system indicator, a cover set indicator, and a Language
Group Specify. Also, the configuration must include one of the
storage options and the network options below:

Storage options:

For boot from NVMe: One NVMe carrier and one NVMe M.2 Module.

For boot from local SFF-3 HDD/SDD: One storage backplane and one
SFF-3 HDD or SDD.

For boot from SAN: Internal HDD or SSD and RAID card are not
required if feature 0837 (Boot from SAN) is selected. A Fibre Channel
adapter must be ordered if feature 0837 is selected.

Network options:

One PCIe2 4-port 1 Gb Ethernet adapter.

One of the supported 10 Gb Ethernet adapters

AIX or Linux is the primary operating system. The minimum defined
initial order configuration is as follows:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

If NVMe carrier card feature EC59 is selected, no disk units are
required to be ordered. If neither feature EC59 nor feature 0837 (SAN
boot) is ordered, then at least one disk unit is required to be
ordered. If no HDD/SSD/SAN boot (0837) is ordered, then feature EC59
(with at least one of #ES14) is the load source.

One PCIe2 4-port 1 GbE Adapter (#5899) is defaulted. Options for
servers with AIX and Linux as the primary operating system are one of
a 10 Gb Ethernet adapter, either feature EC2S, EC2U, EN0H, EN0K, EN0S,
EN0U, EN0W, or EN15.

The minimum defined initial order configuration, if no choice is
made, when IBM i is the primary operating system, is:

The racking approach for the initial order must be either a
7014-T00, 7014-T42, 7965-S42, or 7953-94Y. If an additional rack is
required for I/O expansion drawers as an MES to an existing system,
either a feature 0551, 0553, or ER05 rack must be ordered.

IBM i operating system performance: Clients with write-sensitive
disk/HDD workloads should upgrade from the feature EJ1C/EJ1E base
storage backplane to the feature EJ1M/EJ1D expanded function storage
backplanes to gain the performance advantage of write cache.

Hardware Management Console (HMC) machine code

An HMC is required to manage the Power H924 server implementing
partitioning. Multiple POWER7, POWER8, and POWER9 processor-based
servers can be supported by a single HMC.

Planned HMC hardware and software support:

X86 based - 7042-CR7, 7042-CR8, 7042-CR9

vHMC x86

POWER8 based Open Power: 7063-CR1

vHMC PowerVM based LPAR

If you are attaching an HMC to a new server or adding function to
an existing server that requires a firmware update, the HMC machine
code may need to be updated because HMC code must always be equal to
or higher than the managed server's firmware. Access to firmware and
machine code updates is conditioned on entitlement and license
validation in accordance with IBM policy and practice. IBM may verify
entitlement through customer number, serial number, electronic
restrictions, or any other means or methods employed by IBM at its
discretion.

To determine the HMC machine code level required for the firmware
level on any server, go to the following web page to access the Fix
Level Recommendation Tool (FLRT) on or after the planned availability
date for this product. FLRT will identify the correct HMC machine
code for the selected system firmware level; see the

https://www14.software.ibm.com/support/customercare/flrt/

website.

If a single HMC is attached to multiple servers, the HMC machine
code level must be updated to be at or higher than the server with the
most recent firmware level. All prior levels of server firmware are
supported with the latest HMC machine code level.

The HMC code latest level contains the following:

Support for managing Power H924 system.

Support for the new HMC model 7063-CR1.

Support for PowerVM functions such as the new HMC GUI interface
for VIOS management.

GUI for HMC's Performance and Capacity Monitoring function.

An HMC command to initiate a remote restart operation. This
removes the requirement of VMControl for the PowerVM Remote Restart
function.

For PowerVM GUI functions, VIOS is recommended.

For clients installing systems higher than the EIA 29 position
(location of the rail that supports the rack-mounted server) in any
IBM or non-IBM rack, acquire approved tools outlined in the server
specifications section at
IBM Knowledge Center.
In situations where IBM
service is required and the recommended tools are not available, there
could be delays in repair actions.

The IBM Systems Information Center provides you with a single
information center where you can access product documentation for IBM
systems hardware, operating systems, and server software. Through a
consistent framework, you can efficiently find information and
personalize your access. See the IBM Systems Information Center, at
IBM Knowledge Center.

The IBM Knowledge Center provides you with a single point of
reference where you can access product documentation for IBM systems
hardware, operating systems, and server software. Through a
consistent framework, you can efficiently find information and
personalize your access by going to
IBM Knowledge Center
for all your product
information needs.

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.

The following feature availability matrix for MT 9223 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.

The following is a list of all feature codes in numeric order for
the IBM Power Systems 9223 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.

LA--->

(#0004) - EMEA Bulk MES Indicator

NON-AAP BULK ORDER INDICATOR

Attributes provided: None

Attributes required: None

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 0)

OS level required: None

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#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: No

(#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: 100 (Initial order maximum: 100)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0040) - Mirrored System Disk Level, Specify Code

This code indicates the level of disk protection desired and helps
ensure that adequate hardware is in the final configuration.

Attributes provided: Device-level mirrored protection

Attributes required: Minimum of two (2) disk units

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0041) - Device Parity Protection-All, Specify Code

This code indicates the level of disk protection desired and helps
ensure that adequate hardware is in the final configuration.

Attributes provided: RAID Data Protection

Attributes required: RAID-capable disk unit controller

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0043) - Mirrored System Bus Level, Specify Code

This code indicates the level of disk protection desired and helps
ensure that adequate hardware is in the final configuration.

For new systems: The marketing configurator will error
on an order if sufficient disk units, and expansion units are not
included on the order to support bus-level mirrored
protection for all disk units. New, preloaded systems will be shipped
with bus-level mirroring enabled.

Attributes provided: Bus-level mirrored protection

Attributes required: Minimum of 2 (Two) disk units

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0047) - Device Parity RAID-6 All, Specify Code

This code indicates the level of disk protection desired and helps
ensure that adequate hardware is in the final configuration.

Attributes provided: RAID-6 Data Protection

Attributes required: RAID-6 capable disk unit controller

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0205) - RISC-to-RISC Data Migration

#0205 is used on initial orders to designate that the new server
should only receive a partial load of IBM i in IBM Mfg.

When #0205 is on the order, manufacturing will only load SLIC and
up through QSYS of IBM i. Ensure that enough storage is ordered to
contain the additional OS code that will be loaded following
installation of the system at the Client location. Specify code #0205
is mutually exclusive with #5000, SW Preload Required

The migration process requires that the installed model be at the
same version and release level of IBM i and other licensed programs as
the new server.

More information, and an updated IBM i Upgrade and Data Migration
Road Map (RISC-RISC) are available at

(#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: 480 (Initial order maximum: 250)

OS level required:

AIX supported

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: 480 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0267) - IBM i Operating System Partition Specify

This feature indicates customers intend to create a partition on
the system that will use the IBM i operating system. This feature
should be included once for each intended IBM i 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 IBM i operating system.

Minimum required: 0

Maximum allowed: 480 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0296) - Specify Custom Data Protection

#0296 specifies that a system has multiple IBM i partitions and
that data protection schemes should be considered separately for each
partition instead of only for an overall system level. Each
partition's data protection scheme can be different or the same.

Attributes provided: N/A

Attributes required: N/A

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0308) - Mirrored Level System Specify Code

This specify code indicates the level of disk protection desired
and helps ensure that adequate hardware is in the final configuration.

For new systems, the marketing configurator will show an error if
sufficient disk units and disk controllers are not included on the
order to support IOA-level mirroring protection. #0308 causes all
disk units to be placed into configurations capable of IOA-level
mirroring. Each disk unit and its mirrored pair must be on a
different disk controller.

Note that the load source disk unit in a new, preloaded system will
be device-level mirrored (same protection as provided with feature
#0040). This means that the load source is controlled by the first
disk unit controller on the first system bus, and will be mirrored
with a like disk unit that is also attached to the same first disk
controller on the first system bus.

For upgrade orders, #0308 will cause the marketing configurator to
show an error if sufficient disk units and disk controllers are not
available to provide the capability to enable IOA-level mirrored
protection for all DASD.

It is the client's responsibility to start mirroring on their
system.

Attributes provided: IOA level system mirroring

Attributes required: A minimum of two disk controllers and an
even number of disk units (with a minimum of four disk units on a
system).

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0347) - RAID Hot Spare Specify

#0347 is a specify code that indicates to IBM configuration tools
and to IBM Manufacturing that RAID-5 or RAID-6 disk arrays should be
further protected using the IBM i function of RAID hot spare. If
specified, IBM will ship a configuration which has at least one stand-
by disk drive for each disk controller in the system or designated
partition. The customer may alter the hot spare configuration
selecting different options once the system is installed.

Attributes provided: N/A

Attributes required: Existence of #0041 or #0047

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0348) - V.24/EIA232 6.1m (20-Ft) PCI Cable

This feature provides a 20-foot WAN PCI cable that supports a V.24
or a EIA232 electrical connection interface.

(#0456) - Customer Specified Placement

Requests that IBM deliver the system to the customer according to
the slot in drawer hardware placement defined by the account team.

Eliminates the need to have these parts relocated in the customers
environment as may happen if the order is placed without this feature
code.

Client placement specifications are collected using the System
Planning Tool (SPT) and processed through the marketing configurator.
(Use of the SPT is not required).

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.)

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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#0551) - 19 inch, 1.8 meter high rack

Provides a 19 inch, 1.8 meter high rack with 36 EIA units of total
space for installing rack mounted CECs and/or expansion units. Every
feature #0551 rack is equipped with a standard rear door and (2x) side
covers. #0551 racks, however, do not come equipped with a front door
or trim kit. One of the following front door or trim kit features is
therefore required with every #0551:

#6068 - Optional Front Door for 1.8m Rack

#6263 - 1.8m Rack Trim Kit

#6248 - 1.8m Rack Acoustic Doors

The following features are also orderable on the #0551:

#0599 - Rack Filler Panel Kit

#6580 - Optional Rack Security Kit

#6586 - Modem Tray

The #0551 can support up to eight PDUs, four mounted vertically and
four mounted horizontally. Each PDU mounted horizontally takes up 1
EIA of rack space. The following PDUs are supported:

(#0553) - 19 inch, 2.0 meter high rack

Provides a 19-inch, 2.0 meter high rack with 42 EIA units of total
space for installing rack mounted CECs and/or expansion units. Every
0553 rack is equipped with a standard rear door and (2x) side covers.
#0553 racks, however, do not come equipped with a front door or trim
kit. One of the following front door or trim kit features is
therefore required with every #0553:

The #0553 can support up to nine power distribution units (PDU),
four mounted vertically and five mounted horizontally. Each PDU
mounted horizontally takes up 1 EIA of rack space. The following PDUs
are supported:

#7188 - Power Distribution Unit (12, C13 sockets)

#7109 - Power Distribution Unit (12, C13 sockets)

#7196 - Power Distribution Unit (6, C19 sockets)

#EPTJ - Power Distribution Unit (9, C19 sockets)

#EPTL - Power Distribution Unit (9, C19 sockets)

#EPTN-Power Distribution Unit (12, C13 sockets)

#EPTQ-Power Distribution Unit (12, C13 sockets)

#EPAA - HVDC Power Distribution Unit (6, Rong Feng sockets)

The manufacturing practice and recommended configuration of the
rack is:

(#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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0728) - EXP24S SFF Gen2 Load Source Specify (#5887 or #EL1S)

Indicates that Load Source DASD are placed in an EXP24S SFF
Gen2-bay Drawer.

Attributes provided: External load source placement specify

Attributes required: DASD Slot 1 open in drawer

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 0)

OS level required: None

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#0837) - 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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#0872) - #1948 Load Source Specify (283GB 15k RPM SAS SFF-2 Disk)

This specify code indicates that a #1948 Disk Unit is being used as
the Load Source.

Attributes provided: None

Attributes required: Feature #1948

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 0)

OS level required: See feature 1948

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#0875) - #1962 Load Source Specify (571GB 10k RPM SAS SFF-2 Disk)

This specify code indicates that a #1962 Disk Unit is being used as
the Load Source.

Attributes provided: None

Attributes required: Feature #1962

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 0)

OS level required: See feature 1962

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#0911) - #ESD2 Load Source Specify (1.1TB 10k SFF-2)

Indicates that a #ESD2 (1.1 TB 10k rpm SFF-2 disk drive) is being
used as the Load Source.

Attributes provided: None

Attributes required: Feature #ESD2

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 0)

OS level required: See feature ESD2

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#1025) - Modem Cable - US/Canada and General Use

Modem cable, use with #2893, 6808 and 6833 or similar modem
adapters. Maximum of two per adapter. Select this cable for use with
your modem if there is not another cable feature that is identified as
specific to your country.

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: No

(#1107) - USB 500 GB Removable Disk Drive

Provides an RDX disk drive in a rugged cartridge to be used in an
RDX Internal and External docking station such as the #1103, #1104,
#1123, #EU03, #EU04, #EU23 or #EU07. 500 GB is uncompressed. With
typical 2X compression, capacity would be 1000 GB. Compression/
decompression is provided by the operating system, not the drive
itself. Feature 1107 is not entitled under the IBM Maintenance
Agreement, if one is purchased.

Attributes provided: 500 GB RDX rugged disk/cartridge

Attributes required: None.

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#1817) - Quantity 150 of #1962

This feature ships a quantity of 150 #1962 disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: see feature #1962

Attributes required: see feature #1962

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 0)

OS level required: See feature 1962

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#1818) - Quantity 150 of #1964

This feature ships a quantity of 150 #1964 disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: see feature #1964

Attributes required: see feature #1964

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature 1964

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#1927) - Quantity 150 of #1948

This feature ships a quantity of 150 #1948 disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: see feature #1948

Attributes required: see feature #1948

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 0)

OS level required: See feature 1948

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#1929) - Quantity 150 of #1953

This feature ships a quantity of 150 #1953 disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: see feature #1953

Attributes required: see feature #1953

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature 1953

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#1948) - 283GB 15k RPM SAS SFF-2 Disk Drive (IBM i)

283 GB SFF 15k RPM SAS disk drive mounted in a Gen-2 carrier and
supported in SFF SAS bay such as provided in the #5887 EXP24S I/O
drawer. Disk is formatted for 528 sectors as shipped from IBM
Manufacturing. CCIN is 19B1.

Limitations: physical difference in Gen1 and Gen2 carriers prevent
usage in SFF-1 bays such as used in the #5802/5803 I/O drawer.

(#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 POWER8/POWER9 system units.

(#1962) - 571GB 10k RPM SAS SFF-2 Disk Drive (IBM i)

Limitation: can not be used in #5802/5803 I/O drawers or in CEC
bays due to physical difference in Gen1 and Gen2 carriers.

Attributes provided: 571GB of Disk Storage mounted in a Gen2
carrier

Attributes required: one SFF SAS disk drive bay

Minimum required: 0

Maximum allowed: 672 (Initial order maximum: 0)

OS level required:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#1964) - 600GB 10k RPM SAS SFF-2 Disk Drive (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.

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 POWER8/POWER9 system units.

(#2145) - Primary OS - IBM i

Indicates clients intend to use the IBM i 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 IBM i
operating system on the primary system partition.

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#2146) - Primary OS - AIX

(No longer available as of June 12, 2018)

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

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#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:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#2319) - Factory Deconfiguration of 1-core

Factory deconfiguration of 1 processor core to assist with
optimization of software licensing. The maximum number of this
feature that can be ordered is one less than the number of cores on
the system, e.g. 7 for an 8-core system and 15 for a 16-core system.

Attributes provided: None

Attributes required: None

Minimum required: 0

Maximum allowed: 23 (Initial order maximum: 23)

OS level required: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#2456) - 2M LC-SC 50 Micron Fiber Converter Cable

The 50 micron fiber cable is used to convert from LC type to SC
type connectors. The 2 meter cable has a male LC type connector on
one end and a female SC type connector on the other.

#0367 - Operations Console PCI Cable (ships with a 25 pin to 9 pin
adapter) Multiple #0367 cables can be ordered but only one per #2893)
to serve as consoles for secondary partitions when Logical
Partitioning is utilized. ECS is supported from both the modem port,
and the RVX port.

The following cable is required to support ECS from the RVX port:

#0348 - V.24/EIA232 20-Ft PCI Cable

The #2893 does not support the remote ring indicate function.

Attributes provided: One PCIe slot

Attributes required: Modem

Minimum required: 0

Maximum allowed: 7 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: Does not apply

(#2934) - 3M Asynchronous Terminal/Printer Cable EIA-232

The Asynchronous Printer/Terminal Cable is used for attaching
printers, plotters, and terminals that support the EIA-232 standard to
any asynchronous adapter. This cable is the equivalent of the
combination of FC 2936 (modem cable) and FC 2937 (printer/terminal
interposer) and replaces this method of printer/terminal attachment.

This cable is 3m (9.8 feet) long, uses DB25 connectors and is
supported on all RS/6000 systems using any asynchronous ports.

Attributes provided: EIA232 device attachment capability

Attributes required: Any Asynchronous port

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: No

(#2936) - Asynchronous Cable EIA-232/V.24 3M

Used to attach a modem to the standard I/O ports with the 10-pin to
25-pin converter cable (#3925), 8-port Cable Assembly, 16-Port Cable
Assembly. The cable is 3 meters (9.8 feet) in length.

Attributes provided: Modem attachment to async or serial port

Attributes required: Async or serial port

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: No

(#3124) - Serial-to-Serial Port Cable for Drawer/Drawer- 3.7M

This 3.7 meter cable is available to provide a null-modem
connection between the serial ports of two system drawers that are
mounted within the same rack. The cable provides a DB25 female
connector at each end.

Attributes provided: None

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: No

(#3125) - Serial-to-Serial Port Cable for Rack/Rack- 8M

This 8 meter cable is available to provide a null-modem connection
between the serial ports of two system drawers that are mounted in
separate racks. The cable provides a DB25 female connector at each
end.

Attributes provided: None

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: No

(#3632) - Widescreen LCD Monitor

The Widescreen LCD Monitor has the following general
characteristics:

Black color

Minimum 533mm (21 inch) diagonal LCD digital screen

Maximum native resolution of 1680 x 1050 (widescreen format 1.6:1)

Can display traditional resolutions (1024x768 and 1280x1024)
without stretching

Tilt, swivel, and height stand adjustments

Industry standard analog input (15-pin D) and a DVI to VGA
converter

Attributes provided: Color Flat-panel Monitor

Attributes required: Graphics Adapter

Attributes provided: Color Flat-panel Monitor

Attributes required: Graphics Adapter

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

Note: Not supported in Mainland China.

(#3925) - 0.3M Serial Port Converter Cable, 9-Pin to 25-Pin

This cable converts the 9-pin serial port on the system to a 25-pin
serial port which allows the user to attach 25-pin serial devices to
the system.

Attributes provided: 9-Pin to 25-Pin connectivity

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: No

(#3927) - Serial Port Null Modem Cable, 9-pin to 9-pin, 3.7M

This 3.7 meter 9 pin to 9 pin Null modem Serial cable allows two
EIA-232 communications ports to exchange data with one another without
going through a modem.

Attributes provided: 9 pin female connector at each end of the
cable

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: No

(#3928) - Serial Port Null Modem Cable, 9-pin to 9-pin, 10M

This 10 meter 9 pin to 9 pin Null Modem Serial cable allows two
EIA-232 communications ports to exchange data with one another without
going through a modem.

Attributes provided: 9 pin female connector at each end of the
cable

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: No

(#3930) - System Serial Port Converter Cable

This cable is used to connect the System port/UPS Conversion Cable
(#1827) to the CEC serial port. Also used to connect an ASCII
terminal or modem to the serial port which is physically an RJ45
connection on the Power 710/720/730/740 and Power S824/S822/S814/
S822L/S812L systems unit .

Attributes provided: Attachment of #1827 to CEC serial port;
attachment of ASCII terminal or modem to the serial port.

This cable is required to connect displays with a 15-pin "D" shell
connector to the appropriate accelerator connector when it is farther
away than the attached monitor cable can reach. Rack mounted systems
are likely candidates for this extender cable.

(#4256) - Extender Cable - USB Keyboards, 1.8M

This feature provides a 1.8M extension cable for use with USB
keyboards.

Attributes provided: 1.8M Extension Cable

Attributes required: USB Keyboard

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: No

(#4276) - VGA to DVI Connection Converter

This feature is a plug converter that will allow a Video device
with a 15 pin D-shell VGA cable plug (such as a KVM switch) to connect
to a graphics adapter with a 28 pin D-shell DVI receptacle connector.
This device has both a 28 pin D-Shell DVI plug and a 15 pin D-shell
VGA receptacle.

One and only one rack indicator feature is required onall orders (#4650 to #4666).

(#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.

A rack integration indicator is required on all 19" Rack mountable
device initial 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.

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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#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.

(#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.

Attributes provided: Software Pre-load

Attributes required: N/A

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#5228) - 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. When PowerVM is
installed in the system, all activated processors must have the
PowerVM feature. A fully activated 4-core system requires that four
of this feature be ordered. An encrypted key is supplied to the
customer and is installed on the system, authorizing the partitioning
at the sub-processor level. PowerVM Enterprise Edition also includes
Live Partition Mobility, which allows for the movement of a logical
partition from one Power6, Power7, Power7+ or Power8 server to another
Power6, Power7, Power7+, Power8, or POWER9 with no application
downtime. Note: If feature 5228 is ordered, the quantity ordered
must be equal to the number of active processors.

Attributes provided: Capability to partition processor

Attributes required: None

Minimum required: 1

Maximum allowed: 24 (Initial order maximum: 24)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#5550) - Sys Console On HMC

With #5550, system console function is driven by the Hardware
Management Console (HMC) connected to the system. The HMC is required
if the following functions are desired/selected for the system:

(#5557) - System Console-Ethernet LAN adapter

Indicates that the system console is driven by an Ethernet LAN
adapter. This LAN adapter must be dedicated to console support
functions and cannot be used for any other purpose.

Attributes provided: System Console connection through an
Ethernet LAN adapter

Attributes required: Ethernet LAN adapter

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#5729) - PCIe2 8Gb 4-port Fibre Channel Adapter

PCIe Gen2 8 Gigabit quad port Fibre Channel Adapter is a high-
performance 8x short form adapter based on the Emulex LPe12004 PCIe
Host Bus Adapter (HBA). Each port provides single initiator
capability over a fibre link or with NPIV, multiple initiator
capability is provided. The ports have LC type connectors and utilize
shortwave laser optics. The adapter operates at link speeds of 2, 4,
and 8 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. Direct device
attachment has not been tested and is not supported.

N_Port ID Virtualization (NPIV) capability is supported through
VIOS.

Cables are the responsibility of the customer. Use multimode fibre
optic cables with short-wave lasers that adhere to the following
specifications:

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

Because core sizes are different, OM1 cables can only be connected
to other OM1 cables. For best results, OM2 cables should not be
connected to OM3 cables. However, if an OM2 cable is connected to an
OM3 cable, the characteristics of the OM2 cable apply to the entire
length of the cables.

The following table shows the supported distances for the three
different cable types at the three different link speeds.

A Gen2 PCIe slot is required to provide the bandwidth for all four
ports to operate at full speed.

Consult with your IBM representative or Business Partner for
additional information relative to any third party attachment.

Attributes provided: Four Port Fibre Channel Adapter

Attributes required: 1 Empty PCIe Gen2 slot

Minimum required: 0

Maximum allowed: 25 (Initial order maximum: 25)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported only through VIOS

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#5735) - 8 Gigabit PCI Express Dual Port Fibre Channel Adapter

The 8 Gigabit PCI Express Dual Port Fibre Channel Adapter is a
high-performance 8x short form adapter based on the Emulex LPe12002
PCIe Host Bus Adapter (HBA). Each port provides single initiator
capability over a fibre link. The ports have LC type connectors and
utilize shortwave laser optics. The adapter operates at link speeds
of 2, 4, and 8 Gbps and will automatically negotiates 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 (AIX, IBM i,
Linux,VIOS). If in an IBM i environment, devices can also be directly
attached.

N_Port ID Virtualization (NPIV) capability is supported through
VIOS.

Cables are the responsibility of the customer. Use multimode fibre
optic cables with short-wave lasers that adhere to the following
specifications:

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

Because core sizes are different, OM1 cables can only be connected
to other OM1 cables. For best results, OM2 cables should not be
connected to OM3 cables. However, if an OM2 cable is connected to an
OM3 cable, the characteristics of the OM2 cable apply to the entire
length of the cables.

The following table shows the supported distances for the three
different cable types at the three different link speeds.

#5735 feature indicates a full high adapter. #5273 feature
indicates a low profile adapter which is electronically identical.
CCIN is 577D. Consult with your IBM representative or Business
Partner for additional information relative to any third party
attachment.

See also feature #EN0F or #EN0G for a 2-port 8Gb Fibre Channel
adapter based on a QLogic adapter.

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: Dual Port Fibre Channel

Attributes required: 1 Empty PCIe slot

Minimum required: 0

Maximum allowed: 25 (Initial order maximum: 25)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#5748) - POWER GXT145 PCI Express Graphics Accelerator

The POWER GXT145 is a versatile, low-priced 2D graphics
accelerator. It can be configured to operate in either 8-bit or
24-bit color modes. This adapter supports both analog and digital
monitors. The adapter requires a PCI Express slot. If attaching a
device that requires a 15 pin D-Shell receptacle for a VGA connection
(eg. when the graphic adapter output is routed directly to a 7316-TF3
display or indirectly through a KVM switch), order a VGA to DVI
Connection Converter, feature number 4276 to accommodate the attaching
device.

Note: Feature #5748 adapter is not supported in the PCIe Gen3 I/O
Drawer.

(#5785) - 4 Port Async EIA-232 PCIe Adapter

Connection for 4 asynchronous EIA-232 devices. Ports are
programmable to support EIA-232 protocols, at a line speed of 128K
bps. One connector on the rear of the adapter provides attachment for
a fan-out cable (provided) which provides four EIA-232 ports.

Note #5785 and # 5277 are physically and electrically identical
adapters, except for the type of PCIe slot used (full-high or low
profile). Note also the 4-port #5277/5785 is functionally nearly
identical to the 2-port #5289/5290 except for the number and type of
connectors.

(#5887) - EXP24S SFF Gen2-bay Drawer

The EXP24S SFF Gen2-bay Drawer is an expansion drawer with twenty-
four 2.5-inch form factor SAS bays. #5887 supports up to 24 hot-swap
SFF SAS Hard Disk Drives (HDD). It uses only 2 EIA of space in a
19-inch rack. The EXP24S includes redundant AC power supplies and two
power cords. The EXP24S SFF bays use Gen-2 or SFF-2 SAS bays that are
not compatible with CEC SFF Gen-1 SAS bays or with #5802/ 5803 SFF SAS
bays.

With AIX/Linux/VIOS, the EXP24S can be ordered with four sets of 6
bays, two sets of 12 bays or one set of 24 bays (mode 4, 2 or 1).
With IBM i the EXP24S can be ordered as one set of 24 bays (mode 1).

The EXP24S SAS ports are attached to SAS controller(s) which can be
a SAS PCI-X or PCIe adapter or pair of adapters. The EXP24S can also
be attached to an imbedded SAS controller in a server with an imbedded
SAS port. Attachment between the SAS controller and the EXP24S SAS
ports is via the appropriate SAS Y or X cables.

Limitations: The mode is set at the IBM factory. The capability
to change modes after manufacture is not offered.

(#5899) - PCIe2 4-port 1GbE Adapter

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.

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: 26 (Initial order maximum: 26)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6068) - Opt Front Door for 1.8m Rack

#6068 provides an attractive black full height rack door on the
#0551 19 Inch 1.8m Rack. The door is steel, with a perforated flat
front surface. The perforation pattern extends from the bottom to the
top of the door to enhance ventilation and provide some visibility
into the rack.

Attributes provided: Front Door

Attributes required: #0551 19 inch 1.8m Rack

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

(#6069) - Opt Front Door for 2.0m Rack

#6069 provides an attractive black full height rack door on the
#0553 19 inch 2.0m Rack. The door is steel, with a perforated flat
front surface. The perforation pattern extends from the bottom to the
top of the door to enhance ventilation and provide some visibility
into the rack.

Attributes provided: Front Door

Attributes required: #0553 19 inch 2.0 meter Rack

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

(#6248) - 1.8m Rack Acoustic Doors

#6248 provides front and rear doors for use with the #0551 19 inch
1.8m Rack. This door kit provides additional acoustic dampening for
use where a quieter environment is desired. #6248 results in a larger
footprint and requires additional space.

Attributes provided: Acoustic Door Kit

Attributes required: #0551 19 inch 1.8m Rack

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

(#6249) - 2.0m Rack Acoustic Doors

#6249 provides front and rear doors for use with the #0553 19 inch
2.0m Rack. This door kit provides additional acoustic dampening for
use where a quieter environment is desired. #6249 results in a larger
footprint and requires additional space.

Attributes provided: Acoustic Door Kit

Attributes required: #0553 19 inch 2.0 meter Rack

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

(#6263) - 1.8m Rack Trim Kit

This feature provides a decorative trim kit for the front of
feature number 0551 (19 inch 1.8m Rack).

Attributes provided: Decorative trim kit

Attributes required: #0551 19 inch 1.8m Rack

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

Note: 1x#6263 per #0551

(#6272) - 2.0m Rack Trim Kit

This feature provides a decorative trim kit for the front of
feature number 0553 (19 inch 2.0m Rack).

Attributes provided: Decorative trim kit

Attributes required: #0553 19 inch 2.0 meter Rack

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

Note: 1X#6272 per #0553

(#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: None

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.

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:

(#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:

(#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

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: None

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: None

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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6492) - 4.3m (14-Ft) 1PH/48-60A 200-240V Power Cord

#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

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: 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: None

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: None

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: None

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 7014-T00 or T42 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: 114 (Initial order maximum: 114)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: 1 or 2 per I/O drawer or CEC. MES orderable for SDIs only. The
MES order will ship the 14 foot cable equivalent to feature number
6458.

(#6580) - Optional Rack Security Kit

This feature provides hardware that can be added to a rack to
prevent unauthorized access. It includes keyed front and rear locks
for the #0551 and #0553 rack doors. It also includes two sliding bars
that mount inside the left and right rack side panels. The sliding
bars are accessible when the rack rear door is open. They can be
moved to a position that disables the external latches on the rack
side panels, and prevents removal of the side panels.

Attributes provided: Locking hardware for rack doors and
sidepanels

Attributes required: #0551 or #0553 19-Inch Rack

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

(#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: None

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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6654) - 4.3m (14-Ft) 1PH/24-30A Power Cord

#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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6655) - 4.3m (14-Ft) 1PH/24-30A WR Power Cord

#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: None

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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6657) - 4.3m (14-Ft) 1PH/32A Power Cord

#6657 is a 14-FT/4.3m 1PH/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: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#6658) - 4.3m (14-Ft) 1PH/24A Power Cord-Korea

#6658 is a 14-FT/4.3m 200-240V/24A power cord with a Type KP 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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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:

(#7109) - Intelligent PDU+, 1 EIA Unit, Universal UTG0247 Connector

This feature is for an intelligent AC power distribution unit
(PDU+) that will allow the user to monitor the amount of power being
used by the devices that are plugged in to this PDU+. This AC power
distribution unit provides twelve C13 power outlets. It receives
power through a UTG0247 connector. It can be used for many different
countries and applications by varying the PDU to Wall Power Cord,
which must be ordered separately. Each PDU requires one PDU to Wall
Power Cord. Supported power cords include the following features:
#6489, #6491, #6492, #6653, #6654, #6655, #6656, #6657, and #6658.

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.

Note: When purchased on an MES order with a feature code rack. This
PDU will be mounted in the rear side pockets until all 4 side pockets
on the rack have been filled. Any additional PDUs on the order will
be mounted in 1 unit of EIA rack space. When purchased as an MES
order for addition to a rack in the field. This PDU may not fit in
the side pockets of your rack due to a hardware interference with the
rack, and may require mounting in 1 unit of rack EIA space. Insure
rack space is available before placing the MES order for this PDU when
it is being ordered for field installation.

(#7118) - Environmental Monitoring Probe

The Environmental Monitoring Probe (EMP) enables you to remotely
monitor environmental conditions. Using a standard Web browser, you
can view the ambient temperature and humidity of the remote
environment, as well as the status of two additional contact devices,
such as a smoke detector or open-door sensor. The
temperature/humidity probe plugs into a RJ45 connector an a PDU+. The
EMP can be used with any Powerware UPS equipped with a 10/100 Mb
ConnectUPS Web/SNMP Card (firmware v3.01 or higher). The EMP can be
located up to 20m (65.6 feet) away.

Attributes provided: Monitoring of temperature, humidity, and
status of two contacts/ sensors. A one meter cat5 Ethernet cable,
double sided hook and loop fabric, often called VELCRO(R) tape, two
tie-wraps, and screw with wall anchor for mounting.

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: No

Note: Maximum support is 8x 7118 per 0553 rack and 8x 7118 per 0551
rack. Maximum of one 7118 per 7109 is supported.

(#7188) - Power Distribution Unit

An AC Power Distribution Unit (PDU) which mounts in a 19" rack and
provides twelve C13 power outlets. The #7188 has six 16A circuit
breakers, with two power outlets per circuit breaker. System units and/or
expansion units must use a power cord with a C14 plug to connect to the
#7188.

One of the following line cords must be used to distribute power
from a wall outlet to the #7188;

#6489 - 14-Ft 3PH/32A Power Cord

#6491 - 14-Ft 1PH/63A Power Cord

#6492 - 14-Ft 1PH/48-60A Power Cord

#6653 - 14-Ft 3PH/16A Power Cord

#6654 - 14-Ft 1PH/24-30A Power Cord

#6655 - 14-Ft 1PH/24-30A WR Power Cord

#6656 - 14-Ft 1PH/32A Power Cord

#6657 - 14-Ft 1PH/24A Power Cord

#6658 - 14-Ft 1PH/24A Power Cord-Korea

Attributes provided: Power Distribution Unit with Twelve C13
power outlets.

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.

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#8143) - Linux Software Preinstall

This feature indicates that the Linux operating system is to be
preinstalled on the system. Requires feature number 5000.

Attributes provided: Linux preinstall

Attributes required: Feature number 5000.

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

Refer to Software Requirements for specific O/S levels supported

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#8144) - Linux Software Preinstall (Business Partners)

This feature indicates that the Linux operating system is to be
preinstalled on the system. Requires feature number 5000 or 7305.
This feature is only available to IBM Business Partner - Solution
Providers and IBM Business Partner - Systems Integrators.

Attributes provided: Linux preinstall

Attributes required: Feature number 5000 or 7305.

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

Refer to Software Requirements for specific O/S levels supported

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#8845) - USB Mouse

The optical LED USB Mouse has 2 buttons and a scroll wheel that
acts as a third button. Mouse cable is 1.8 meters long. OS does not
support scrolling with the wheel. Business black with red scroll
wheel.

(#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: None

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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#9387) - Specify mode-1 & CEC SAS port for EXP24 #5887/EL1S

Feature indicates that EXP24S SFF Gen2 Drawer (#5887 or EL1S) will
be configured by IBM Manufacturing in Mode 1 (One group of 24 drive
bays) with the two internal 6G SAS ports on the rear of the system
unit. Dual IOA high performance/function storage backplane provides
the two SAS ports.

Two YO cables connect the EXP24S to the SAS ports. Use the cable
length appropriate to the configuration and select from features such
as #ECBT, #ECBU, #ECBV or #ECBW.

IBM does not provide changes to the mode setting after #5887 or
EL1S is shipped.

(#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: 24 (Initial order maximum: 24)

OS level required: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#9441) - New IBM i License Core Counter

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

Attributes provided: None

Attributes required: None

Minimum required: 0

Maximum allowed: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

OS level required: None

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: 24 (Initial order maximum: 24)

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

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: 24 (Initial order maximum: 24)

OS level required: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

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: None

Initial Order/MES/Both/Supported: Initial

CSU: N/A

Return parts MES: Does not apply

(#EB27) - QSFP+ 40GbE Base-SR Transceiver

IBM QSFP+ optical tranceiver required for 40 Gbs ports which are
not using copper QSFP+ transceiver.

Attributes provided: QSFP+ tranceiver for 40 Gbs ports.

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: No

(#EB2B) - 1m (3.3-ft), IBM Passive QSFP+ to QSFP+ Cable (DAC)

QSFP+ cable is used for 40Gb-to-40Gb Ethernet connectivity.
Clients can use this QSFP+ Direct Attach Cable for Ethenet
connectivity. This copper cable has QSFP+ transceivers already
attached to each end.

Attributes provided: 1m QSFP+ to QSFP+ Cable

Attributes required: QSFP/QSFP+ ports

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: No

(#EB2H) - 3m (9.8-ft), IBM Passive QSFP+ to QSFP+ Cable (DAC)

QSFP+ cable is used for 40Gb-to-40Gb Ethernet connectivity.
Clients can use this QSFP+ Direct Attach Cable for Ethenet
connectivity. This copper cable has QSFP+ transceivers already
attached to each end.

Attributes provided: 3m QSFP+ to QSFP+ Cable

Attributes required: QSFP/QSFP+ ports

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: No

(#EB2J) - 10m (30.3-ft), IBM Passive QSFP+ MTP Optical Cable

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EB2K) - 30m (90.3-ft), IBM Passive QSFP+ MTP Optical Cable

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EB2M) - AC Power Supply - 1400W for Server (200-240 VAC)

This feature provides one 200 - 240V, 1400 watt AC power supply.

The power supply is configurated in a one plus one for a 2U server
or two plus two for a 4U server 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.

(#EB3Z) - Lift tool based on GenieLift GL-8 (standard)

Feature #EB3Z is a feature that is available on multiple server
types (POWER S812L, S822L, S824L, S814, S824, S812, S822, E850C, E850,
E880C, E870C, E880, and E870, also 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.

Attributes provided: Lift Tool

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: 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+ SR. 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: 250)

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 adapter's 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: 250)

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: 250)

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EB4L) - 1.5m SFP28/25GbE copper Cable

Feature EB4L is a passive 1.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: 250)

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: 250)

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.

(#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.

Attributes provided: Wedge/angle shelf

Attributes required: Feature EB3Z

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EB50) - 0.5m EDR IB Copper Cable QSFP28

(No longer available as of January 18, 2019)

0.5 meter length copper twinax cable, also called a DAC (Direct
Attached Copper) cable. The cable can be used for either 100Gb EDR
InfiniBand (IB) adapters or IB switches. Built onto each end of the
cable is a passive Quad (4-channel) Small Form-Factor Pluggable
(QSFP28) copper cable transceiver. Cable can also be used for FDR IB
(56Gb). Cables are available in various lengths: 0.5m = #EB50, 1m =
#EB51, 2m = #EB52, 1.5m = #EB54 See also optical fiber cables for
longer lengths such as #EB5A through #EB5H.

Attributes provided: Copper twinax cable with QSFP28 transceivers

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: No

(#EB51) - 1.0m EDR IB Copper Cable QSFP28

1.0 meter length copper twinax cable, also called a DAC (Direct
Attached Copper) cable. The cable can be used for either 100Gb EDR
InfiniBand (IB) adapters or IB switches. Built onto each end of the
cable is a passive Quad (4-channel) Small Form-Factor Pluggable
(QSFP28) copper cable transceiver. Cable can also be used for FDR IB
(56Gb). Cables are available in various lengths: 0.5m = #EB50, 1m =
#EB51, 2m = #EB52, 1.5m = #EB54 See also optical fiber cables for
longer lengths such as #EB5A through #EB5H.

Attributes provided: Copper twinax cable with QSFP28 transceivers

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: No

(#EB52) - 2.0M EDR IB Copper Cable QSFP28

2.0 meter length copper twinax cable, also called a DAC (Direct
Attached Copper) cable. The cable can be used for either 100Gb EDR
InfiniBand (IB) adapters or IB switches. Built onto each end of the
cable is a passive Quad (4-channel) Small Form-Factor Pluggable
(QSFP28) copper cable transceiver. Cable can also be used for FDR IB
(56Gb). Cables are available in various lengths: 0.5M = #EB50, 1M =
#EB51, 2M = #EB52, 1.5M = #EB54 See also optical fiber cables for
longer lengths such as #EB5A through #EB5H.

Attributes provided: Copper twinax cable with QSFP28 transceivers

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: No

(#EB54) - 1.5M EDR IB Copper Cable QSFP28

1.5 meter length copper twinax cable, also called a DAC (Direct
Attached Copper) cable. The cable can be used for either 100Gb EDR
InfiniBand (IB) adapters or IB switches. Built onto each end of the
cable is a passive Quad (4-channel) Small Form-Factor Pluggable
(QSFP28) copper cable transceiver. Cable can also be used for FDR IB
(56Gb). Cables are available in various lengths: 0.5M = #EB50, 1M =
#EB51, 2M = #EB52, 1.5M = #EB54 See also optical fiber cables for
longer lengths such as #EB5A through #EB5H.

Attributes provided: Copper twinax cable with QSFP28 transceivers

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: No

(#EB59) - 100GbE Optical Transceiver QSFP28

One optical transceiver for 100Gb Ethernet adapter such as #EC3L or
#EC3M 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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EB5A) - 3M EDR IB Optical Cable QSFP28

3 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5B) - 5M EDR IB Optical Cable QSFP28

5 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5C) - 10M EDR IB Optical Cable QSFP28

10 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5D) - 15M EDR IB Optical Cable QSFP28

15 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5E) - 20M EDR IB Optical Cable QSFP28

20 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5F) - 30M EDR IB Optical Cable QSFP28

30 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5G) - 50M EDR IB Optical Cable QSFP28

50 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5H) - 100M EDR IB Optical Cable QSFP28

100 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver. Cables are available in various lengths: 3m =
#EB5A, 5M = #EB5B, 10M = #EB5C, 15M = #EB5D, 20M = #EB5E, 30M = #EB5F,
and 50M = #EB5G, 100M = #EB5H. See also copper twinax cables for
shorter lengths such as #EB50 through #EB54. Limitation: Adapter and
switch must have been manufactured by Mellanox to use this cable.
Cable is not supported for FDR IB (56Gb).

Attributes provided: Optical fiber cable with QSFP28 transceivers

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: No

(#EB5J) - 0.5M 100GbE Copper Cable QSFP28

0.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).

(#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).

(#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).

(#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).

(#EB5N) - 25M EDR IB Optical Cable QSFP28

25 meter length optical fiber cable, also called an AOC (Active
Optical Cable). The cable can be used for either 100Gb EDR InfiniBand
(IB) adapters or IB switches. Built onto each end of the cable is a
active Quad (4-channel) Small Form-Factor Pluggable (QSFP28) optical
cable transceiver.

(#EB72) - IBM i 7.2 Indicator

This feature is used to indicate the correct level of code when IBM
i is specified.

Attributes provided: IBM i 7.2 Indicator

Attributes required: IBM i operating system

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EB73) - IBM i 7.3 Indicator

This feature is used to indicate the correct level of code when IBM
i is specified.

Attributes provided: IBM i 7.3 Indicator

Attributes required: IBM i operating system

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: Does not apply

(#EC01) - Rack Front Door (Black)

This feature provides a front door in flat black color with an IBM
logo for the 7965-94Y rack. A front door such as #EC01 is required on
the 7965-94Y. The door is the full width of the rack and the hinges
and lockplate can be moved from side to side allowing the door to be
opened on the left or on the right (this door hinges on either the
left side or right side). IBM ships rack with the handle on the right
and hinges on the left viewed facing the front of the rack. The door
comes with a lock which is keyed the same as the rear door or side
panels. Uniquely keyed locks can be obtained by the client directly
from Southco, the vendor from whom IBM purchased the lock.

Attributes provided: Front Door with lock

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

(#EC02) - Rack Rear Door

This feature provides a rear door in flat black color for the
7965-94Y rack. Either feature number EC02 or feature EC05 is required
on the 7965-94Y. The door is the full width of the rack and the
hinges and lockplate can be moved from side to side allowing the door
to be opened on the left or on the right (this door hinges on either
the left side or right side). IBM ships rack with the handle on the
right and hinges on the left viewed facing the rear of the rack. The
front doors , rear doors and side panels come with a lock which is
keyed the same as the front door or side panels. Uniquely keyed locks
can be obtained by the client directly from Southco, the vendor from
whom IBM purchased the lock.

Attributes provided: Rear Door with lock

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

(#EC03) - Rack Side Cover

This feature provides two side panels in black color for the
7953-94X rack. Each side panel can cover either the left or the right
side of the rack. These side covers are optional but recommended for
optimal airflow through a rack and for physical security. The front
door, rear doors and side panels come with a lock which is keyed the
same as the front door or side panels. Uniquely keyed locks can be
obtained by the client directly from Southco, the vendor from whom IBM
purchased the lock.

Attributes provided: Left and Right side panels for 7953 rack.

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

(#EC04) - Rack Suite Attachment Kit

This feature provides the attachment hardware to allow two IBM
PureFlex System 42U Racks with or without side panels to be bolted
together in a continuous suite. Order one EC04 feature for each 42U
rack attached to the starting rack. For example, in a three-rack
suite, order two EC04 features. When multiple racks are joined in
this way without internal side panels, cables can be more easily run
between racks without having to exit the continuous rack enclosure.
With the side panels installed optimum thermal efficiencies are
gained. If the optional rear door heat exchanger is chosen, side
panels must remain on racks in the suite. Side panels should be used
on the leftmost and rightmost racks of the suite.

Attributes provided: Hardware and trim to attach two racks

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

(#EC07) - Slim Rear Acoustic Door

Slim rear acoustic door for use on the 7014-T42 or server feature
#0553 2.0M racks. Depth of this acoustic door is only about 113 mm
(4.45 inches).

Physically #EC07 and #EC08 are identical, but have two feature
codes to assist IBM sales configurator logic. #EC07 designates a rear
door and #EC08 designates a front door.

Attributes provided: Rear Acoustic door

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

(#EC08) - Slim Front Acoustic Door

Slim front acoustic door for use on the 7014-T42 or server feature
#0553 2.0M racks. Depth of this acoustic door is only about 113 mm
(4.45 inches).

Physically #EC07 and #EC08 are identical, but have two feature
codes to assist IBM sales configurator logic. #EC07 designates a rear
door and #EC08 designates a front door.

Attributes provided: Acoustic front door

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

(#EC15) - Rear Door Heat Exchanger for 2.0 Meter Slim Rack

This feature indicates that the rear door heat exchanger (1164-95X)
is ordered for the 7965-94Y rack. Either feature EC02 or feature EC05
is required on the 7965-94Y. This door hinges on the right side.
("Right" is as you face the door from the outside of the rack).

Attributes provided: RDHX

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

(#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.

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.3, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.3, or later

AIX supported

IBM i 7.3 TR4, or later

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS supported, NIC capability only.

(#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.

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.

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.

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.3, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.3, or later

AIX supported

IBM i 7.3 TR4, or later

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EC38) - PCIe3 2-port 10GbE NIC&RoCE SFP+ Copper Adapter

This PCIe Gen3 adapter provides two 10 Gb SFP+ ports for copper
twinax cabling/transceivers. 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.

Active Copper twinax cables up to 5 meter in length are supported
such as provided by feature #EN01, #EN02 or #EN03. These cables also
include copper transceivers. Active cables differ from passive
cables.

Feature code #EC37 and #EC38 have identical electronics and
function and CCIN (57BC), but have different tail stocks. #EC37 is
low profile and #EC38 is full high. Compared to EC2M/EC2N, the EC37/
EC38 have identical application capability, but different cabling
(optical fiber vs copper twinax). The EC37/EC38 is based on the
Mellanox ConnectX-3 Pro ASIC and is newer technology than previous
features EC27/EC28.

(#EC3B) - PCIe3 2-Port 40GbE NIC RoCE QSFP+ Adapter

RoCE is Remote Direct Memory Access (RDMA) over Converged Ethernet.
RoCE 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.

The #EC3A/EC3B adapter does not include transceivers. Shorter
distance copper cables include transceivers on the end of the QSFP+
cable (see #EB2B (1m), #EB2H (3m), #ECBN (5m)). For longer distance
use two optical SR transceiver (two #EB27). QSFP+ optical cables to
be used with the #EB27 transceiver are #EB2J (10m) or #EB2K (30m). Do
not mix copper and optical on the same adapter.

Feature code #EC3A and #EC3B have identical electronics and
function and the same CCIN (57BD), but they have different tail
stocks. #EC3A is low profile and #EC3B is full height.

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 11, Service Pack 4, or later, with Mellanox OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12, Service Pack 3, or later, with Mellanox OFED 4.3, or later

SUSE Linux Enterprise Server 12, Service Pack 3, or later, with
Mellanox OFED 4.3, or later

SUSE Linux Enterprise Server 15, or later, with Mellanox OFED 4.3,
or later

Red Hat Enterprise Linux 7 for Power LE, version 7.5, or later,
with Mellanox OFED 4.3, or later

Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 7
for Power LE version 7.5, or later, with Mellanox OFED 4.3, or later

Red Hat Enterprise Linux 7 for Power LE, version 7.5, for POWER9,
or later, with Mellanox OFED 4.3, or later

AIX supported

IBM i only supported through VIOS

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Assignment to the VIOS supported. NIC capability only.

(#EC3F) - PCIe3 2-port 100Gb EDR IB Adapter x16

The PCIe Gen3 x16 2-port InfiniBand EDR adapter provides high speed
connectivity with other servers or IB switches. Each port maximum of
100Gb assumes no other system and/or switch bottlenecks are present.
A PCIe Gen3 x16 PCIe slot is required. This adapter is sourced from
Mellanox Corporation based on ConnectX-4 technology. The adapter
supports the InfiniBand Trade Association (IBTA) specification version
2.

The two 100Gb ports have QSFP+ connections which support EDR
cables, either EDR DAC or EDR optical. One adapter can support either
or both types of cable. The user can choose to cable up just one port
if they desire. Transceivers are included in the cables. IBM cable
features EB50-EB54 (copper shorter distance) and #EB5A-EB5H (optical
longer distance) are supported or their copper or optical Mellanox
equivalents are supported. Other cables are not supported.

#EC3E and #EC3F adapters are electronically and functionally
identical with the same CCIN of 2CEA. #EC3E has a low profile
tailstock bracket. #EC3F has a full high tailstock bracket. See also
#EC3T and #EC3U for a 1-port version of this adapter.

Limitation: Adapter does not fit in x8 PCIe slot. Adapter is not
supported in a PCIe Gen3 I/O drawer.

Attributes provided: EDR InfiniBand PCIe Adapter

Attributes required: available x16 PCIe Gen3 slot

For 9223-42H: (#EC3F)

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.4, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.4, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.4, or later

AIX not supported

IBM i not supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EC3M) - PCIe3 2-port 100GbE (NIC&RoCE) QSFP28 Adapter x16

This PCIe Gen3 Ethernet x16 adapter provides two 100 Gb 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.

IBM offers either passive copper twinax cables up to 2 meter 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 chose to order an IBM qualified and supported QSFP28 optical
transceiver (feature #EB59) to put into the adapter and provide your
own 100GE optical cabling 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 #EC3L and #EC3M have identical electronics and
function and CCIN (2CEC), but have different tail stock brackets.
#EC3L is low profile and #EC3M is full high. The adapter is based on
a Mellanox ConnectX-4 adapter which uses a ConnectX-4 EN Network
Controller.

Backward compatible with 40Gb Ethernet when using compatible
cables/transceivers.

Attributes provided: 2-port 100Gb Ethernet Adapter

Attributes required: x16 PCIe Gen3 slot

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.3, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.3, or later

AIX supported

IBM i 7.3 TR4, or later

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EC3U) - PCIe3 1-port 100Gb EDR IB Adapter x16

The PCIe Gen3 x16 1-port InfiniBand EDR adapter provides high speed
connectivity with other servers or IB switches. The port's maximum of
100Gb assumes no other system and/or switch bottlenecks are present.
A PCIe Gen3 x16 PCIe slot is required. This adapter is sourced from
Mellanox Corporation based on ConnectX-4 technology. The adapter
supports the InfiniBand Trade Association (IBTA) specification version
2.

The 100Gb port has a QSFP+ connection which supports EDR cables,
either EDR DAC or EDR optical. Transceivers are included in the
cables. IBM cable features EB50-EB54 (copper shorter distance) and
#EB5A-EB5H (optical longer distance) are supported or their copper or
optical Mellanox equivalents are supported. Other cables are not
supported.

#EC3T and #EC3U adapters are electronically and functionally
identical with the same CCIN of 2CEB. Feature #EC3T has a low profile
tailstock bracket and feature #EC3U has a full high tailstock bracket.
See also #EC3E and #EC3F for a 2-port version of this adapter.

Limitation: Adapter does not fit in x8 PCIe slot. Adapter is not
supported in a PCIe Gen3 I/O drawer.

Attributes provided: EDR InfiniBand PCIe Adapter

Attributes required: available x16 PCIe Gen3 slot

For 9223-42H: (#EC3U)

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.4, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.4, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.4, or later

AIX not supported

IBM i not supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EC46) - PCIe2 4-Port USB 3.0 Adapter

The PCIe Gen2 x8 short 4-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 #EC45 and #EC46 USB
adapters are electronically identical with the same 58F9 CCIN. They
differ physically in their tailstock. #EC45 is low profile and #EC46
is full high.

(#EC63) - PCIe4 1-port 100Gb EDR IB CAPI adapter

The PCIe Gen4 x16 1-port InfiniBand EDR adapter provides high speed
connectivity with other servers or IB switches. The port's maximum of
100Gb assumes no other system and/or switch bottlenecks are present.
A PCIe Gen4 x16 PCIe slot is required. This adapter is sourced from
Mellanox Corporation. based on ConnectX-5 technology. The adapter
supports the InfiniBand Trade Association (IBTA) specification version
2.

The 100Gb port has a QSFP+ connection which supports EDR cables,
either EDR DAC or EDR optical. Transceivers are included in the
cables. IBM cable features EB50-EB54 (copper shorter distance) and
#EB5A-EB5H (optical longer distance) are supported or their copper or
optical Mellanox equivalents are supported. Other cables are not
supported.

#EC62 and #EC63 adapters are electronically and functionally identical
with the same CCIN of 2CF1. #EC62 is low profile and #EC63 is full high.

Limitation: Adapter does not fit in x8 PCIe slot. Adapter is not
supported in a PCIe Gen3 I/O drawer.

Attributes provided: EDR InfiniBand PCIe Adapter

Attributes required: available x16 PCIe Gen4 slot

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.3, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.3, or later

AIX not supported

IBM i not supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EC65) - PCIe4 2-port 100Gb EDR IB CAPI adapter

The PCIe Gen4 x16 2-port InfiniBand EDR adapter provides high speed
connectivity with other servers or IB switches. Each port maximum of
100Gb assumes no other system and/or switch bottlenecks are present.
A PCIe Gen4 x16 PCIe slot is required. This adapter is sourced from
Mellanox Corporation. based on ConnectX-5 technology. The adapter
supports the InfiniBand Trade Association (IBTA) specification version
2.

The two 100Gb ports have QSFP+ connections which support EDR
cables, either EDR DAC or EDR optical. One adapter can support either
or both types of cable. The user can choose to cable up just one port
if they desire. Transceivers are included in the cables. IBM cable
features EB50-EB54 (copper shorter distance) and #EB5A-EB5H (optical
longer distance) are supported or their copper or optical Mellanox
equivalents are supported. Other cables are not supported.

#EC64 and #EC65 adapters are electronically and functionally identical
with the same CCIN of 2CF2. #EC64 is low profile and #EC65 is full high.

Limitation: Adapter does not fit in x8 PCIe slot. Adapter is not
supported in a PCIe Gen3 I/O drawer.

Attributes provided: EDR InfiniBand PCIe Adapter

Attributes required: available x16 PCIe Gen4 slot

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
MLNX_OFED 4.3, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with MLNX_OFED 4.3, or later

Red Hat Enterprise Linux, with MLNX_OFED 4.3, or later

AIX not supported

IBM i not supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#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 20M in length (feature #EB2J
#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 20M in length (feature #EB2J
#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

Attributes provided: Dual-port 100 GbE Adapter with RoCE
capability

Attributes required: Available Gen4 PCIe Slot

For 9223-42H: (#EC66)

Minimum required: 0

Maximum allowed: 3 (Initial order maximum: 3)

OS level required:

Red Hat Enterprise Linux 7.5 for Power LE (p8compat) or later,
with Mellanox OFED 4.4, or later

Red Hat Enterprise Linux 7.5 for POWER9 or later, with Mellanox
OFED 4.4, or later

Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 7
for Power LE version 7.5, or later, with Mellanox OFED 4.4, or later

SUSE Linux Enterprise Server 12 Service Pack 3, or later, with
Mellanox OFED 4.4, or later

SUSE Linux Enterprise Server for SAP with SUSE Linux Enterprise
Server 12 Service Pack 3, or later, with Mellanox OFED 4.4, or later

SUSE Linux Enterprise Server 15, or later, with Mellanox OFED 4.4,
or later

AIX Version 7.2 with the 7200-02 Technology Level and Service Pack
7200-02-02-1832, or later

AIX Version 7.1 with the 7100-05 Technology Level and Service Pack
7100-05-02-1832, or later

AIX Version 7.2 with the 7200-03 Technology Level, or later

AIX Version 6.1 with the 6100-09 Technology Level and Service Pack
6100-09-12-1838, or later (planned availability September 14, 2018)

AIX Version 7.2 with the 7200-01 Technology Level and Service Pack
7200-01-05-1845, or later (planned availability January 31, 2019)

AIX Version 7.1 with the 7100-04 Technology Level and Service Pack
7100-04-07-1845, or later (planned availability January 31, 2019)

IBM i requires VIOS

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.6.23, or later

(#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.

(#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.

(#ECBL) - SAS X Cable 10m - 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.

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.

(#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.

(#ECBN) - 5m (16.4-ft), IBM Passive QSFP+ to QSFP+ Cable (DAC)

(No longer available as of January 18, 2019)

QSFP+ cable is used for 40Gb-to-40Gb Ethernet connectivity.
clients can use this QSFP+ Direct Attach Cable for Ethernet
connectivity. This copper cable has QSFP+ transceivers already
attached to each end.

Attributes provided: 5m QSFP+ to QSFP+ Cable

Attributes required: QSFP/QSFP+ ports

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: 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.

(#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.

(#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.

(#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.

(#ECBX) - SAS YO Cable 15m - HD Narrow 3Gb Adapter to Enclosure

This 15 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 #5887 EXP24S SAS
I/O drawer. This cable can support up to 3Gb 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 #3457 15m SAS YO cable,
except the #ECBX connector for the SAS adapters is more narrow
allowing it to fit onto the newer PCIe3 SAS adapters.

Limitation

Does not support 6Gb throughput.

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.

(#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 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: 250)

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ECC0) - SAS AA Cable 0.6m - HD Narrow 6Gb Adapter to Adapter

This 0.6m SAS cable connects a pair of PCIe SAS adapters with write
cache to each other. The pair can be two PCIe3 SAS adapters or can be
two PCIe2 SAS adapters. This AA cable has two Mini-SAS HD (High
Density) Narrow connectors which connect the top connectors of the two
PCIe adapters providing a high performance path of all the dual
controller communication including mirroring the write cache and
status awareness of each card. This cable can support up to 6Gb
throughput.

Two AA cables are always required between a pair of PCIe3 SAS
adapters with write cache such as #EJ0L unless six (three pair) of
ports or unless eight (four pair) are used to attach I/O drawers. One
AA cable is always required between a pair of PCIe2 SAS adapters with
write cache (pair of #5913 or a pair of #ESA3) unless all six (three
pair) of ports are used to attach I/O drawers. 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.

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

This cable is almost identical to the #5918 0.6m SAS AA cable,
except #ECC0 connectors for the SAS adapters are more narrow allowing
it to fit onto the newer PCIe3 SAS adapters.

Attributes provided: high speed connection between two PCIe2 or
two PCIe3 SAS adapters with write cache

Attributes required: available top connectors on pair of PCIe2 or
PCIe3 SAS adapters with write cache

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: No

(#ECC2) - SAS AA Cable 1.5m - HD Narrow 6Gb Adapter to Adapter

This 1.5m SAS cable connects a pair of PCIe SAS adapters with write
cache to each other. The pair can be two PCIe3 SAS adapters or can be
two PCIe2 SAS adapters. This AA cable has two Mini-SAS HD (High
Density) Narrow connectors which connect the top connectors of the two
PCIe adapters providing a high performance path of all the dual
controller communication including mirroring the write cache and
status awareness of each card. This cable can support up to 6Gb
throughput.

Two AA cables are always required between a pair of PCIe3 SAS
adapters with write cache such as #EJ0L unless six (three pair) of
ports or unless eight (four pair) are used to attach I/O drawers. One
AA cable is always required between a pair of PCIe2 SAS adapters with
write cache (pair of #5913 or a pair of #ESA3) unless all six (three
pair) of ports are used to attach I/O drawers. 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.

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

This cable is almost identical to the #5917 1.5m SAS AA cable,
except #ECC2 connectors for the SAS adapters are more narrow allowing
it to fit onto the newer PCIe3 SAS adapters.

Attributes provided: high speed connection between two PCIe2 or
two PCIe3 SAS adapters with write cache

Attributes required: available top connectors on pair of PCIe2 or
PCIe3 SAS adapters with write cache

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: No

(#ECC3) - SAS AA Cable 3m - HD Narrow 6Gb Adapter to Adapter

This 3m SAS cable connects a pair of PCIe SAS adapters with write
cache to each other. The pair can be two PCIe3 SAS adapters or can be
two PCIe2 SAS adapters. This AA cable has two Mini-SAS HD (High
Density) Narrow connectors which connect the top connectors of the two
PCIe adapters providing a high performance path of all the dual
controller communication including mirroring the write cache and
status awareness of each card. This cable can support up to 6Gb
throughput.

Two AA cables are always required between a pair of PCIe3 SAS
adapters with write cache such as #EJ0L unless six (three pair) of
ports or unless eight (four pair) are used to attach I/O drawers. One
AA cable is always required between a pair of PCIe2 SAS adapters with
write cache (pair of #5913 or a pair of #ESA3) unless all six (three
pair) of ports are used to attach I/O drawers. 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.

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

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

Attributes provided: high speed connection between two PCIe2 or
two PCIe3 SAS adapters with write cache

Attributes required: available top connectors on pair of PCIe2 or
PCIe3 SAS adapters with write cache

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: No

(#ECC4) - SAS AA Cable 6m - HD Narrow 6Gb Adapter to Adapter

This 6m SAS cable connects a pair of PCIe SAS adapters with write
cache to each other. The pair can be two PCIe3 SAS adapters or can be
two PCIe2 SAS adapters. This AA cable has two Mini-SAS HD (High
Density) Narrow connectors which connect the top connectors of the two
PCIe adapters providing a high performance path of all the dual
controller communication including mirroring the write cache and
status awareness of each card. This cable can support up to 6Gb
throughput.

Two AA cables are always required between a pair of PCIe3 SAS
adapters with write cache such as #EJ0L unless six (three pair) of
ports or unless eight (four pair) are used to attach I/O drawers. One
AA cable is always required between a pair of PCIe2 SAS adapters with
write cache (pair of #5913 or a pair of #ESA3) unless all six (three
pair) of ports are used to attach I/O drawers. 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.

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

This cable is almost identical to the #5916 6m SAS AA cable, except
#ECC4 connectors for the SAS adapters are more narrow allowing it to
fit onto the newer PCIe3 SAS adapters.

Attributes provided: high speed connection between two PCIe2 or
two PCIe3 SAS adapters with write cache

Attributes required: available top connectors on pair of PCIe2 or
PCIe3 SAS adapters with write cache

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: No

(#ECC7) - 3M 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. See also other AOC cable length options such
as the feature #ECC8 (10 meter).

(#ECC8) - 10M 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. See also other AOC cable length options such
as the feature #ECC6 (2 meter). The 10 meter length is suggested for
cabling to a different rack.

Attributes provided: Pair of 10 meter active optical cables

Attributes required: CXP ports on a PCIe3 Optical Cable Adapter
(#EJ07) and on a PCIe3 module such as a #EMXF in a PCIe Gen3 Expansion
Drawer (#EMX0)

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: No

Note: Only used with Solution machine type 5146

(#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: 250)

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: 250)

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 EXP12SX (#ESLL/#ELLL ) or 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.

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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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 EXP12SX (#ESLL/#ELLL ) or 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.

(#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
cache 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.

(#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:

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.

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: 250)

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
cache 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.

(#ECR0) - 2.0 Meter Slim Rack

Provides a 19-inch, 2.0 meter high rack with 42 EIA units of total
space for installing rack mounted CECs and/or expansion units. The
ECR0 rack does not come equipped with a standard front door, rear door
or side covers. The following features are required for every #ECR0
rack:

1x #ECRF (high-end appearance front door ) or ECRM (Basic Front
Door)

1x #ECRG (Rear Door)

2x ECRJ (Side Covers)

The following optional feature is also offered for the ECR0 rack:

ECRK - Rack Rear Extension.

Up to four vertically mounted Power Distribution Units (PDU) are
supported and every vertically mounted PDU requires #ELC0. Each PDU
beyond four will consume 1U of rack space.

Attributes provided: 19 inch, 2.0M, 42 EIA Rack

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

Note: One of feature #ECRF, and one of feature #ECRG and two of
feature #ECRJ are required per one #ECR0 ordered.

(#ECRF) - Rack Front Door High-End appearance

This feature provides a front door in High-End appearance with an
IBM logo for the S42 rack. A front door such as #ECRF is recommended
on the S42 rack. A front door is required on ECR0 rack. IBM ships
rack with the handle on the right and hinges on the left viewed facing
the front of the rack.

The door comes with a lock which is keyed the same as the rear door
or side panels. Uniquely keyed locks can be obtained by the client
directly from Southco, the vendor from whom IBM purchased the lock.

Attributes provided: Front Door with lock

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

(#ECRG) - Rack Rear Door Black

This feature provides a rear door in flat black color for the S42
rack. Feature number ECRF and ECR0 rack and ECRG are recommended on
the S42 rack. A front and rear door is required on the ECR0 rack.

The door is the full width of the rack and the hinges and lockplate
can be moved from side to side allowing the door to be opened on the
left or on the right. IBM ships rack with the handle on the right and
hinges on the left viewed facing the rear of the rack.

The front doors , rear doors and side panels come with a lock which
is keyed the same as the front door or side panels. Uniquely keyed
locks can be obtained by the client directly from Southco, the vendor
from whom IBM purchased the lock.

Attributes provided: Rear Door with lock

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

(#ECRJ) - Rack Side Cover

This feature provides one side panels in black color for the S42 or
feature #ECR0 rack. Each side panel can cover either the left or the
right side of the rack. These side covers are optional but
recommended on S42 rack. 2x ECRJ are required on every ECR0 for
optimal airflow through a rack and for physical security.

The front door, rear doors and side panels come with a lock which
is keyed the same as the front door or side panels. Uniquely keyed
locks can be obtained by the client directly from Southco, the vendor
from whom IBM purchased the lock.

Attributes provided: One side panel for rack.

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

(#ECRK) - Rack Rear Extension 5-In

Attributes provided: Rack Rear Extension

Attributes required: Maximum one per feature #ECR0 rack

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

(#ECRM) - Rack Front Door for Rack (Black/Flat)

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

(#ECS0) - Indicator Assembled and Tested in China

This is indicator that the product was assembled and tested in
China.

Attributes provided: None

Attributes required: None

Minimum required: 0000

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ECSF) - Custom Service Specify, Montpellier, France

Having #ECSF on the order, will cause the order to be routed to
France 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: No

(#ECSJ) - NeuCloud Indicator/Specify

This is a no-charge specify code for helping IBM track orders for
reporting purposes

Attributes provided: none

Attributes required: used in mainland China

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

(#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

(#ECSS) - Integrated Solution Packing

This is a routing indicator for Solution packing.

Attributes provided: Routing instruction for manufacturing

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: 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.

(#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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EJ08) - PCIe3 Optical Cable Adapter for PCIe3 Expansion Drawer

PCIe3 x16 adapter provides two CXP ports for the attachment of two
active optical CXP cables (AOC) or two CXP copper cables. One adapter
supports the attachment of one PCIe3 fan-out module in a PCIe Gen3 I/O
Expansion Drawer. CCIN is 2CE2

EJ08 is similar to EJ05 and EJ07, but has different packaging and
different CCIN.

Attributes provided: PCIe3 adapter with two CXP ports to attach
two active optical cables or two CXP copper cables.

(#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,
EXP12SX, 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/EXP12SX/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 POWER8/POWER9
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 EXP12SX 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.

(#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 EXP12SX 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/ EXP12SX/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 can not be mixed in the same array.

Limitations:

HDD and SSD can not 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 EXP12SX 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.

Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 7
for Power LE version 7.6, or later

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EJ0W) - SAS Ports/Cabling for Dual IOA BackPlane

Two SAS ports on the rear of the 4U server and SAS cables inside the
server to the dual IOA SAS controllers in the higher performance storage
backplane. An EXP24SX SAS storage drawer can be attached to SAS ports
using a pair of SAS-mini HD Narrow YO cables. Note that the SAS ports are
physically located in the same space as one of the PCIE x8 slots and
reduce the total number of PCIe adapter which can be used in the 4U
server.

Attributes provided: Two SAS ports, Internal SAS cables.

Attributes required: 4U server with high performance storage
backplane such as EJ1D or EJ1M. Available PCIe slot.

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

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.

(#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, EXP12SX, 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,
EXP12SX 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: 16 (Initial order maximum: 16)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.4.20 or later

(#EJ1C) - Base Storage Backplane 12 SFF-3 Bays/RDX Bay

Base Storage backplane with integrated SAS controller for SAS bays
in the system unit. SAS bays are 2.5-inch or Small Form Factor (SFF)
and used drives mounted on a carrier/tray specific to the system unit
(SFF-3).

The high performance SAS controller provides RAID-0, RAID-5, RAID-6
and RAID-10 support for either HDD or SSD. JBOD support for HDD is
also supported. Controller has no write cache.

For servers that support split backplane capability add #EJ1E
feature. For write cache performance use #EJ1D or #EJ1M Backplane
instead of this backplane.

Both 5xx and 4k byte sector HDD/SSD are supported. 5xx and 4k
drives cannot be mixed in the same array.

Attributes provided: Storage backplane with one integrated SAS
adapter with no cache running 12 SFF-3 SAS bays in the system unit and
one RDX bay in the system unit

Attributes required: Server without #EJ1D or #EJ1M backplane

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EJ1D) - Expanded Function Storage Backplane 18 SFF-3 Bays/Dual

IOA with Write Cache/Opt Ext SAS port

Expanded Function Storage backplane with dual integrated SAS
controllers with write cache and optional external SAS port. High
performance controllers run SFF-3 SAS bays in the system unit. Dual
controllers (also called dual I/O adapters or paired controllers) and
their write cache are placed in integrated slots and do not use PCIe
slots. Write cache augments controller's high performance for
workloads with writes, especially for HDD. 1.8 GB physical write
cache is leveraged with compression to provide up to 7.2 GB cache
capacity. The write cache contents are protected against power loss
with flash memory and super capacitors removing the need for battery
maintenance.

Both 5xx and 4k byte sector HDD/SSD are supported. 5xx and 4k
drives cannot be mixed in the same array.

Attributes provided: Storage backplane with a pair of integrated
SAS adapters with write cache and optional external SAS port running
up to: a) a set of 18 SFF-3 SAS bays in the system unit; b) two SAS
ports on the rear of the system unit to connect a single
EXP24S/EXP24SX I/O drawer.

Attributes required: Server without #EJ1C or #EJ1M backplane

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EJ1E) - Split #EJ1C to 6+6 SFF-3 Bays

Add 2nd SAS Controller

This feature modifies the base Storage backplane cabling and adds a
second, high performance SAS controller. The existing 12 SFF-3 SAS
bays are cabled to be split into two sets of six bays, each with one
SAS controller. Both SAS controllers are located in integrated slots
and do not use a PCIe slot.

The high performance SAS controllers each provides RAID-0, RAID-5,
RAID-6 and RAID-10 support. JBOD support for HDD is also supported.
There is no write cache on either controller.

Both 5xx and 4k byte sector HDD/SSD are supported. 5xx and 4k
drives cannot be mixed in the same array.

Attributes provided: A second integrated SAS adapter with no
cache and internal cables to provide two sets of six SFF-3 bays in the
system unit.

Expanded Function Storage backplane with dual integrated SAS
controllers with write cache and optional external SAS port. High
performance controllers run SFF-3 SAS bays and RDX bay in the system
unit. Dual controllers (also called dual I/O adapters or paired
controllers) and their write cache are placed in integrated slots and
do not use PCIe slots. Write cache augments controller's high
performance for workloads with writes, especially for HDD. 1.8 GB
physical write cache is leveraged with compression to provide up to
7.2 GB cache capacity. The write cache contents are protected against
power loss with flash memory and super capacitors removing the need
for battery maintenance.

Both 5xx and 4k byte sector HDD/SSD are supported. 5xx and 4k
drives cannot be mixed in the same array.

Attributes provided: Expanded Function Storage backplane with a
pair of integrated SAS adapters with write cache and optional external
SAS port running up to: a) a set of 12 SFF-3 SAS bays in the system
unit: b) one RDX bay in the system unit; c) two SAS ports on the rear
of the system unit to connect a single EXP24S/EXP24SX I/O drawer.

Attributes required: Server without #EJ1C or #EJ1D backplane

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EJ1P) - PCIe1 SAS Tape/DVD Dual-port 3Gb x8 Adapter

This is a PCIe Gen1 short x8 form factor adapter. It supports the
attachment of SAS tape and DVD using a pair of mini SAS 4x connectors.
The PCIe1 can be used for external tape drives which are not supported
on the newer and faster 4-port 6Gb PCIe3 adapter (see feature code
#EJ10/EJ11/EL60). The adapter supports external SAS tape drives such
as the DAT72, DAT160, LTO-4, LTO-5, LTO-6, and LTO-7 found in the IBM
multimedia drawers such as the 7226-1U3 or 7214-1U2 or tape units such
as the TS2240, TS2340, TS3100, TS3200, and TS3310. Other removable
media devices supported include IBM SAS/ SATA DVD-ROM/RAM drives.

SAS adapter-to-enclosure (AE) 3Gb cables with mini-SAS connectors
are used to attach these drives. See feature codes #3684 (3 meter)
and #3685 (6 meter). The same AE cables can often alternatively be
ordered under the tape enclosure or multimedia drawer.

Feature EJ1P and EJ1N are electrically and functionally identical
with the same CCIN of 57B3. EJ1P has a full-high tailstock bracket
and EJ1N has a low-profile tailstock bracket. Feature EJ1P/EJ1N is
the same adapter as #5901/5278 but designates to IBM configurator
tools that the usage will be tape/DVD and will not be used for disk.

Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 7 for
Power LE version 7.5, or later

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 1 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.

(#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 1 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.

Linux software support can be downloaded from the following location:
http://www-03.ibm.com/security/cryptocards/pciecc2/ordersoftware.shtml

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EJR1) - Specify Mode-1 1(1)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 1 and be using one PCIe3 RAID SAS adapter (#EJ0J/ EJ0M/EL3B ) and
one 6G YO SAS Cable.

(#EJR2) - Specify Mode-1 1(2)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 1 and be using two (one pair) PCIe3 RAID SAS adapters
(#EJ0J/EJ0M/EL3B) and two 6G YO SAS Cables.

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using two (one pair) RAID PCIe3 SAS adapters
(#EJ0J/EJ0M/EL3B) and two 6G X SAS Cables.

(#EJR4) - Specify Mode-2 1(4)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using four (two pair) PCIe3 RAID SAS adapters
(#EJ0J/EJ0M/EL3B) and two 6G X SAS Cables.

(#EJR5) - Specify Mode-4 1(4)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 4 and be using four (unpaired) PCIe3 RAID SAS adapters
(#EJ0J/EJ0M/EL3B) and two 6G X SAS Cables

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using one PCIe3 RAID SAS adapter (#EJ0J/ EJ0M/EL3B) and
two 6G YO SAS Cables.

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using two (nonpaired) PCIe3 RAID SAS adapters
(#EJ0J/EJ0M/EL3B) and two 6G YO SAS Cables.

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using one PCIe3 RAID SAS adapter (#EJ0J/ EJ0M/EL3B) and
one 6G YO SAS Cables.

This indicates a "partial" configuration where there are not enough
adapters/cables to run all the SAS bays in the EXP24S. 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 #EJR7.

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using two PCIe3 RAID SAS adapters (#EJ0J ) and one 6G X
SAS Cable.

This indicates a "partial" configuration where there are not enough
adapters/cables to run all the SAS bays in the EXP24S. 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 #EJR4.

(#EJRC) - Specify Mode-4 1(1)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 4 and be using one PCIe3 RAID SAS adapter (#EJ0J/ EJ0M/EL3B) and
one 6G X 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 EXP24S. 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 #EJR5, #EJRD or #EJRE.

(#EJRD) - Specify Mode-4 1(2)EJ0J/EJ0M/EL3B for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 4 and be using two (nonpaired) PCIe RAID SAS adapters
(#EJ0J/EJ0M/EL3B) and one 6G X SAS Cables.

This indicates a "partial" configuration where there are not enough
adapters/cables to run all the SAS bays in the EXP24S. 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 #EJR5 or #EJRE.

(#EJRE) - Specify Mode-4 1(3)EJ0J/EJ0M/EL3B for EXP24S (#5888/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 4 and be using three (nonpaired) PCIe3 RAID SAS adapter
(#EJ0J/EJ0M/EL3B) and two 6G X SAS Cables. One leg of one 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 EXP24S. 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 #EJR5.

(#EJRF) - Specify Mode-1 1(2)EJ14 for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 1 and be using two PCIe3 12GB Cache RAID PLUS SAS Adapter
Quad-port 6Gb x8 (#EJ14) and two 6G YO SAS Cables.

(#EJRG) - Specify Mode-2 1(2)EJ14 1(2) X for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using two PCIe3 12GB Cache RAID PLUS SAS Adapter
Quad-port 6Gb x8 (#EJ14) and two 6G X SAS Cables.

(#EJRH) - Specify Mode-2 1(2)EJ14 1(1) X for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using two PCIe3 12GB Cache RAID PLUS SAS Adapter
Quad-port 6Gb x8 (#EJ14) and one 6G X SAS Cable.

This indicates a "partial" configuration where there are not enough
adapters/cables to run all the SAS bays in the EXP24S. 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.

(#EJRJ) - Specify Mode-2 1(4)EJ14 for EXP24S (#5887/EL1S)

This feature does not order or ship any hardware, but indicates to
IBM config tools and to IBM Manufacturing that in this configuration
one EXP24S SFF Gen2-bay Drawer (#5887/#EL1S) should be configured in
Mode 2 and be using four PCIe3 12GB Cache RAID PLUS SAS Adapter
Quad-port 6Gb x8 (#EJ14) and two 6G X SAS Cable.

(#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.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 1 (one group of
12 drive bays). It will be connected to the two SAS ports on the rear
of the system unit run by the integrated SAS controllers of the high
performance/function storage backplane.

Two YO12 cables connect the SAS Storage Enclosure to the systems
SAS 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.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 1 (one group 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 #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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 1 (one group of
12 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 4 (four groups
of 3 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 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 with a subset of adapters
and cables is used.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 #EJV7.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 2 (two groups
of 6 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 #EJV4.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 4 (four groups
of 3 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 #EJV5, #EJVD or #EJVE. This feature
does not order or ship any hardware, but indicates to IBM config tools
and to IBM Manufacturing that in this configuration one EXP12SX Drawer
(#ESLL/ELLL) 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 EXP12SX. 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 #EJV5, #EJVD or #EJVE.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 4 (four groups
of 3 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 #EJV5 or #EJVE.

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 4 (four groups
of 3 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 #EJV5.

(#EJVF) - Specify Mode-1 1(2)EJ14 1(2)YO12 for EXP12SX #ESLL/ELLL

Feature indicates that EXP12SX SAS Storage Enclosure (#ESLL or
#ELLL) will be configured by IBM Manufacturing in Mode 1 (one group of
12 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 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 with a subset of adapters
and cables is used.

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 the two SAS ports on the rear
of the system unit run by the integrated SAS controllers of the high
performance/function storage backplane.

Two YO12 cables connect the SAS Storage Enclosure to the systems
SAS 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.

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.

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.

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.

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.

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.

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.

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.

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.

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 "partioal" 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.

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.

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.

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.

(#EJWF) - Specify Mode-1 1(2)EJ14 1(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.

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 1(2)EJ14 1(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.

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 1(2)EJ14 1(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.

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 1(4)EJ14 1(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.

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

(#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 #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.

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-T42 or #0553.

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

(#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.

(#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
(#EMXF or #EMXG) 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 required: One or two PCIe Optical Cable Adapters
(#EJ07/#EJ05/#EJ08), one or two PCIe3 fanout modules (#EMXF), one or
two CXP cable pairs (such as #ECC6 or #ECC8 or #ECCS), one power
supply conduit (such as #EMXA).

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#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.

(#EMXF) - PCIe3 6-Slot Fanout Module for PCIe3 Expansion Drawer

The module has two CXP ports which are connected two CXP ports on a
PCIe Optical Cable Adapter #EJ05 or #EJ07 or #EJ08 depending on the
server selected. 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.

(#EMXG) - 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. With firmware 8.4 or later, the fanout
module supports concurrent maintenance, though obviously while off-
line all its PCIe slots are also off-line. Blind swap cassettes (BSC)
are used for the PCIe slots. The BSC are interchangeable with the
#5802/5877/5803/5873 12X PCIe I/O Drawer BSC.

The module has two CXP ports which are connected two CXP ports on a
PCIe Optical Cable Adapter #EJ05 or #EJ07 or #EJ08 depending on the
server selected. 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.

EMXG is a follow-on to the original EMXF fanout module. EMXG and
EMXF are functionally identical but EMXG implements a small physical
change to enable a larger set of potential PCIe adapters to be housed.
EMXG and EMXF can be intermixed in the same drawer. There is no
difference in firmware or software prerequisites for the EMXF and
EMXG. EMXG and for EMXF use the same BSC.

(#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: 250)

OS level required: None

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: 250)

OS level required: None

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EN0A) - PCIe3 16Gb 2-port Fibre Channel Adapter

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 POWER8/POWER9 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:

(#EN0G) - PCIe2 8Gb 2-Port Fibre Channel Adapter

This feature ships a two-port, 8 Gb PCIe Gen2 Fibre Channel Adapter
based on the QLogic QLE2562 Host Bus Adapter (HBA). Each port
provides single initiator capability over a fibre link. The ports
have LC type connectors and utilize shortwave laser optics. The
adapter operates at link speeds of 2, 4, and 8 Gbps and will
automatically negotiates 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 or can directly attach
to a Fibre Channel port on a supported storage unit. N_Port ID
Virtualization (NPIV) capability is supported through VIOS. Cables
are the responsibility of the customer. Use multimode fibre optic
cables with short-wave lasers that adhere to the following
specifications:

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

Because core sizes are different, OM1 cables can only be connected
to other OM1 cables. For best results, OM2 cables should not be
connected to OM3 cables. However, if an OM2 cable is connected to an
OM3 cable, the characteristics of the OM2 cable apply to the entire
length of the cables. The following table shows the supported
distances for the three different cable types at the three different
link speeds.

Red Hat Enterprise Linux for SAP with Red Hat Enterprise Linux 7 for
Power LE version 7.5, or later

Red Hat Enterprise Linux 7 for Power LE, version 7.5, for POWER9, or
later

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EN0H) - PCIe3 4-port (10Gb FCoE & 1GbE) SR&RJ45

This PCIe Gen3 Converged Network Adapter (CNA) supports both
Ethernet NIC (Network Interface Card) traffic and Fibre Channel
traffic over Ethernet (FCoE). 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 have CNA functionality. The 1Gb ports have Ethernet
capability. The adapter was initially announced as PCIe Gen2, but
upgrades to the adapter firmware and introduction of POWER8/POWER9
servers have enabled PCIe Gen3.

NPIV capability is provided through VIOS

SR-IOV capability for the NIC function is supported on specific
servers with the appropriate firmware and OS level for any of the four
ports.

The 10Gb ports are SFP+ and include an optical SR transceiver. 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. Note that an FCoE
switch is required for any FCoE traffic.

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.

#EN0H and #EN0J adapters are electronically identical. They are
physically identical except #EN0H has a tail stock for full high PCIe
slots and #EN0J has a tail stock for low profile slots. The CCIN is
2B93 for both features.

(#EN0K) - PCIe3 4-port (10Gb FCoE & 1GbE) SFP+Copper&RJ45

This PCIe Gen3 Converged Network Adapter (CNA) supports both
Ethernet NIC (Network Interface Card) traffic and Fibre Channel
traffic over Ethernet (FCoE). The adapter provides two 10 Gb ports
for active copper twinax cables and two 1 Gb RJ45 ports in a PCIe 8x
short form adapter. The 10Gb ports have CNA (both NIC and FCoE)
functionality. The 1Gb ports have Ethernet capability. The adapter
was initially announced as PCIe Gen2, but upgrades to the adapter
firmware and introduction of POWER8/POWER9 servers have enabled PCIe
Gen3.

NPIV capability is provided through VIOS

SR-IOV capability for the NIC function is supported on specific
servers with the appropriate firmware and OS level for any of the four
ports.

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. Note that an FCoE switch is required for any FCoE traffic.

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.

#EN0K and #EN0L adapters are electronically identical. They are
physically identical except #EN0K has a tail stock for full high PCIe
slots and #EN0L has a tail stock for low profile slots. The CCIN is
2CC1 for both features.

#EN0K/EN0L are very similar to the #EN0H/#EN0J adapters except the
#EN0H/EN0K use SR optical cabling and has a different CCIN.

(#EN0S) - PCIe2 4-Port (10Gb+1GbE) SR+RJ45 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.

(#EN0U) - PCIe2 4-port (10Gb+1GbE) Copper SFP+RJ45 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.

(#EN12) - PCIe2 8Gb 4-port Fibre Channel Adapter

PCIe Gen2 8 Gigabit quad port Fibre Channel Adapter is a high-
performance 8x short form Host Bus Adapter (HBA). Each port provides
single initiator capability over a fiber link or with NPIV, multiple
initiator capability is provided. The ports have LC type connectors
and use shortwave laser optics. The adapter operates at link speeds
of 2, 4, and 8 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. This adapter based on the QLogic QLE2564
PCIe Host Bus Adapter (HBA).

The adapter connects to a Fibre Channel switch. Direct device
attachment has not been tested and is not supported.

N_Port ID Virtualization (NPIV) capability is supported through
VIOS.

Cables are the responsibility of the customer. Use multimode
fibre optic cables with short-wave lasers that adhere to the following
specifications:

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

Because core sizes are different, OM1 cables can only be connected
to other OM1 cables. For best results, OM2 cables should not be
connected to OM3 cables. However, if an OM2 cable is connected to an
OM3 cable, the characteristics of the OM2 cable apply to the entire
length of the cables.

The following table shows the supported distances for the three
different cable types at the three different link speeds.

(#EN13) - PCIe 1-port Bisync Adapter

(No longer available as of April 24, 2018)

The #EN13 is a full high PCIe adapter which provides 1 RVX port for
Bisync capability. This RVX port is labeled "Port 1". Its CCIN =
576C Bisync functionality identical to #2893 PCIe adapter is provided.

Select one of the following cables to attach to port 1 (RVX port):

#0348 - V.24/EIA232 20-Ft PCI Cable

#0353 - V.35 20-Ft PCI Cable

#0359 - X.21 20-Ft PCI Cable

Limitations

The #2893 does not support the remote ring indicate function.

There is a second port on the card with an integrated modem, but
Bisync is not supported on this port (labeled "Port 0").

Attributes required: PCIe full high slot, external modem, cable
for the modem.

Minimum required: 0

Maximum allowed: 7 (Initial order maximum: 0)

OS level required:

Red Hat Enterprise Linux supported

SUSE Linux Enterprise Server supported

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EN15) - PCIe3 4-port 10GbE SR Adapter

This PCIe Gen3 supports Ethernet NIC (Network Interface Card)
traffic and also supports SR-IOV capability. The adapter provides
four 10 Gb SR optical ports in a PCIe 8x short form adapter. SR-IOV
capability for the NIC function is supported with the appropriate
firmware and OS level for any of the four ports. Enabling SR-IOV
function requires an HMC.

The four 10Gb ports are SFP+ and include four 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.

#EN15 and #EN16 adapters are electronically identical. They are
physically identical except #EN15 has a tail stock for full high PCIe
slots and #EN16 has a tail stock allowing it to fit in a Power
E870/E880 or Power E870C/E880C system node PCIe slot. The CCIN is
2CE3 for both features.

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.

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.

Cables:

Cables are the responsibility of the customer. Use multimode fibre
optic cables with short-wave lasers that adhere to the following
specifications:

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.

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.

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.

Cables are the responsibility of the customer. Use multimode fibre
optic cables with short-wave lasers that adhere to the following
specifications:

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.

(#EP1V) - 8-core Typical 3.8 to 4.0 GHz (max) POWER9 Processor

8-core Typical 3.8 to 4.0 GHz (max) POWER9 Processor card.
Available in quantity of one or two.

Attributes provided: 8-core processor card

Attributes required: One processor card slot

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i 7.3 TR4 or later

IBM i 7.2 TR8 or later

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EP1W) - 10-core 3.5 to 3.9 GHz (max) POWER9 Processor

10-core Typical 3.5 to 3.9 Ghz (max) POWER9 Processor card.
Available in quantity of one or two.

Attributes provided: 10-core processor card

Attributes required: One processor card slot

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i 7.3 TR4 or later

IBM i 7.2 TR8 or later

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EP1X) - 12-core Typical 3.4 to 3.9 GHz (max) POWER9 Processor

12-core Typical 3.4 to 3.9 GHz (max) POWER9 Processor card.
Available in quantity of one or two.

Attributes provided: 12-core processor card

Attributes required: One processor card slot

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i 7.3 TR4 or later

IBM i 7.2 TR8 or later

Initial Order/MES/Both/Supported: Both

CSU: No

Return parts MES: No

(#EP4E) - One Processor Core Activation for #EP1E

(No longer available as of June 12, 2018)

Entitlement for one processor core activation

Attributes provided:

Processor core activation for #EP1E.

Attributes required:

Feature #EP1E.

Minimum required: 0

Maximum allowed: 16 (Initial order maximum: 16)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EP4F) - One Processor Core Activation for #EP1F

(No longer available as of June 12, 2018)

Entitlement for one processor core activation

Attributes provided: Processor core activation for #EP1F.

Attributes required: Feature #EP1F.

Minimum required: 0

Maximum allowed: 20 (Initial order maximum: 20)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EP4G) - One Processor Core Activation for #EP1G

(No longer available as of June 12, 2018)

Entitlement for one processor core activation.

Attributes provided: Processor core activation for #EP1G.

Attributes required: Feature #EP1G.

Minimum required: 0

Maximum allowed: 24 (Initial order maximum: 24)

OS level required: None

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EP4V) - One Processor Core Activation for #EP1V

Entitlement for one processor core activation.

Attributes provided: Processor core activation for #EP1V.

Attributes required: Feature #EP1V.

Minimum required: 0

Maximum allowed: 16 (Initial order maximum: 16)

OS level required: See feature EP1V

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EP4W) - One Processor Core Activation for #EP1W

Entitlement for one processor core activation.

Attributes provided: Processor core activation for #EP1W.

Attributes required: Feature #EP1W.

Minimum required: 0

Maximum allowed: 20 (Initial order maximum: 20)

OS level required: See feature EP1W

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EP4X) - One Processor Core Activation for #EP1X

Entitlement for one processor core activation.

Attributes provided: Processor core activation for #EP1X.

Attributes required: Feature #EP1X.

Minimum required: 0

Maximum allowed: 24 (Initial order maximum: 24)

OS level required: See feature EP1X

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.

(#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, and #6667.

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

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.

(#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, and #6667.

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: 250)

OS level required: None

Initial Order/MES/Both/Supported: Both

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.

(#EQ62) - Quantity 150 of #ES62 3.86-4.0 TB 7200 rpm 4k LFF-1 Disk

This feature ships a quantity of 150 #ES62 drives. The
configurator may either generate this feature or allow users to select
this feature as they would any other single drive feature. This
feature remains on the inventory records.

(#EQ0Q) - Quantity 150 of #ES0Q 387GB SFF-2 4k SSD (AIX/Linux)

This feature ships a quantity 150 of #ES0Q SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk unit feature. This feature
remains on the inventory records

Attributes provided: Quantity of 150 #ES0Q

Attributes required: See #ES0Q

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES0Q

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ0R) - Quantity 150 of #ES0R 387GB SFF-2 4k SSD (IBM i)

This feature ships a quantity 150 of #ES0R SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk unit feature. This feature
remains on the inventory records.

Attributes provided: Quantity of 150 #ES0R

Attributes required: See #ES0R

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES0R

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ0S) - Quantity 150 of #ES0S 775GB SFF-2 4k SSD (AIX/Linux)

This feature ships a quantity 150 of #ES0S SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk unit feature. This feature
remains on the inventory records.

Attributes provided: Quantity of 150 #ES0S

Attributes required: See #ES0S

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES0S

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ0T) - Quantity 150 of #ES0T 775GB SFF-2 4k SSD (IBM i)

This feature ships a quantity 150 of #ES0T SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk unit feature. This feature
remains on the inventory records.

Attributes provided: Quantity of 150 #ES0T

Attributes required: See #ES0T

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES0T

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ64) - Quantity 150 of #ES64 7.72-8.0 TB 7200 rpm 4k LFF-1 Disk

This feature ships a quantity of 150 #ES64 drives. The
configurator may either generate this feature or allow users to select
this feature as they would any other single drive feature. This
feature remains on the inventory records.

(#EQ78) - Quantity 150 of #ES78 387GB SFF-2 SSD 5xx

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES78 solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES78

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES78

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ79) - Quantity 150 of #ES79 387GB SFF-2 SSD 5xx

This feature ships a quantity of 150 #ES79 solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES79

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES79

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ7E) - Quantity 150 of #ES7E 775GB SFF-2 SSD 5xx

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES7E solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES7E

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES7E

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ7F) - Quantity 150 of #ES7F 775GB SFF-2 SSD 5xx

This feature ships a quantity of 150 #ES7F solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES7F

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES7F

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ80) - Quantity 150 of #ES80 1.9TB SFF-2 SSD 4k

This feature ships a quantity of 150 #ES80 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: see feature #ES80

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES80

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ81) - Quantity 150 of ES81 1.9TB SFF-2 SSD 4k

This feature ships a quantity of 150 #ES81 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: see feature #ES81

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ES81

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQ85) - Quantity 150 of #ES85 387GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES85 solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES85

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES85

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ86) - Quantity 150 of #ES86 387GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES86 solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES86

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES86

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8C) - Quantity 150 of #ES8C 775GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8C solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES8C

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES8C

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8D) - Quantity 150 of #ES8D 775GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8D solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES8D

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES8D

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8F) - Quantity 150 of #ES8F 1.55TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8F solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES8F

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES8F

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8G) - Quantity 150 of #ES8G 1.55TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8G solid state drives
(SSDs). The configurator may either generate this feature or allow
users to select this feature as they would any other single SSD
feature. This feature remains on the inventory records.

Attributes provided: Ships 150 SSDs

Attributes required: See feat #ES8G

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ES8G

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8Y) - Quantity 150 of #ES8Y 931GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8Y SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ES8Y

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ES8Y

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ8Z) - Quantity 150 of ES8Z 931GB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES8Z SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ES8Z

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ES8Z

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ96) - Quantity 150 of ES96 1.86TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES96 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ES96

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ES96

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQ97) - Quantity 150 of ES97 1.86TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ES97 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ES97

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ES97

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQD2) - Quantity 150 of #ESD2 (1.1TB 10k SFF-2)

This feature ships a quantity of 150 #ESD2 disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESD2

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 0)

OS level required: See feature ESD2

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQD3) - Quantity 150 of #ESD3 (1.2TB 10k SFF-2)

This feature ships a quantity of 150 #ESD3 1.2TB SAS 10K SFF-2 disk
units. The configurator may either generate this feature or allow
users to select this feature as they would any other single disk unit
feature. This feature remains on the inventory records.

Attributes provided: See feature#ESD3

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 0)

OS level required: See feature ESD3

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQDN) - Quantity 150 of #ESDN (571GB 15K RPM SAS SFF-2 for IBM i)

This feature ships a quantity 150 of #ESDN drive. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk drive feature. This feature
remains on the inventory records.

This feature ships a quantity 150 of #ESDP drive. The configurator
may either generate this feature or allow users to select this feature
as they would any other single disk drive feature. This feature
remains on the inventory records.

Attributes provided: Quantity 150 of #ESDP

Attributes required: See #ESDP

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 0)

OS level required: See feature ESDP

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQE7) - Quantity 150 of #ESE7 3.72TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ESE7 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESE7

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ESE7

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQE8) - Quantity 150 of ESE8 3.72TB SFF-2 SSD 4k

(No longer available as of January 18, 2019)

This feature ships a quantity of 150 #ESE8 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESE8

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ESE8

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQEU) - Quantity 150 of #ESEU (571GB 10k SFF-2)

This feature ships a quantity of 150 #ESEU 571GB 10K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESEU

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESEU

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQEV) - Quantity 150 of #ESEV (600GB 10k SFF-2)

This feature ships a quantity of 150 #ESEV, 600GB 10K RPM 4K SAS
SFF-2 Disk, units. The configurator may either generate this feature
or allow users to select this feature as they would any other single
disk unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESEV

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESEV

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQEY) - Quantity 150 of #ESEY (283 GB SFF-2)

(No longer available as of November 9, 2018)

This feature ships a quantity 150 of #ESEY disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records

Attributes provided: Quantity 150 of #ESEY

Attributes required: See #ESEY

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESEY

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQEZ) - Quantity 150 of #ESEZ (300GB SFF-2)

(No longer available as of November 9, 2018)

This feature ships a quantity of 150 #ESEZ disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records

Attributes provided: Quantity of 150 #ESEZ

Attributes required: See #ESEZ

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESEZ

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQF2) - Quantity 150 of #ESF2 (1.1TB 10k SFF-2)

This feature ships a quantity of 150 #ESF2 1.14TB 10K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESF2

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESF2

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQF3) - Quantity 150 of #ESF3 (1.2TB 10k SFF-2)

This feature ships a quantity of 150 #ESF3, 1.2TB 10K RPM 4K SAS
SFF-2 Disk, units. The configurator may either generate this feature
or allow users to select this feature as they would any other single
disk unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESF3

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESF3

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQFN) - Quantity 150 of #ESFN (571GB SFF-2)

(No longer available as of November 9, 2018)

This feature ships a quantity 150 of #ESFN disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records

Attributes provided: Quantity 150 of #ESFN

Attributes required: See #ESFN

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESFN

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQFP) - Quantity 150 of #ESFP (600GB SFF-2)

(No longer available as of November 9, 2018)

This feature ships a quantity 150 of #ESFP disk units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records

Attributes provided: Quantity 150 of #ESFP

Attributes required: See #ESFP

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESFP

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQFS) - Quantity 150 of #ESFS (1.7TB 10k SFF-2)

This feature ships a quantity of 150 #ESFS 1.71TB 10K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESFS

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESFS

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQFT) - Quantity 150 of #ESFT (1.8TB 10k SFF-2)

This feature ships a quantity of 150 #ESFT 1.8TB 10K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Attributes provided: See feature #ESFT

Attributes required: 150 SFF-2 SAS bays in EXP24S drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: See feature ESFT

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQG5) - Quantity 150 of #ESG5 (387GB SAS 5xx)

This feature ships a quantity of 150 #ESG5 387 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESG5

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESG5

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQG6) - Quantity 150 of #ESG6 (387GB SAS 5xx)

This feature ships a quantity of 150 #ESG6 387GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature#ESG6

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ESG6

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQGG) - Quantity 150 of #ESGG (775GB SAS 5xx)

This feature ships a quantity of 150 #ESGG 775 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature#ESGG

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 0)

OS level required: See feature ESGG

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ESG6) - 387GB Enterprise SAS 5xx SFF-2 SSD for IBM i

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.

Features #ESG5 and #ESG6 are physically identical drives with the
same CCIN of 5B16. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESG5 indicates
usage by AIX, Linux or VIOS. ESG6 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 POWER8 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
can not 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: SFF-2 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 0)

OS level required:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQGB) - Quantity 150 of #ESGB (387GB SAS 4k)

This feature ships a quantity of 150 #ESGB 387 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGB

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGB

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQGC) - Quantity 150 of #ESGC (387GB SAS 4k)

This feature ships a quantity of 150 #ESGC 387 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGC

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGC

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQGF) - Quantity 150 of #ESGF (775GB SAS 5xx)

This feature ships a quantity of 150 #ESGF 775 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGF

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGF

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGG) - 775GB Enterprise SAS 5xx SFF-2 SSD for IBM i

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.

Features #ESGF and #ESGG are physically identical drives with the
same CCIN of 5B17. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGF indicates
usage by AIX, Linux or VIOS. ESGG 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 POWER8 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
can not 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:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EQGK) - Quantity 150 of #ESGK (775GB SAS 4k)

This feature ships a quantity of 150 #ESGK 775 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGK

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGK

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQGL) - Quantity 150 of #ESGL (775GB SAS 4k)

This feature ships a quantity of 150 #ESGL 775 GB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGL

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGL

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQGP) - Quantity 150 of #ESGP (1.55TB SAS 4k)

This feature ships a quantity of 150 #ESGP 1.55 TB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGP

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGP

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EQGQ) - Quantity 150 of #ESGQ (1.55TB SAS 4k)

This feature ships a quantity of 150 #ESGQ 1.55 TB, units. The
configurator may either generate this feature or allow users to select
this feature as they would any other single disk unit feature. This
feature remains on the inventory records.

Attributes provided: See feature #ESGQ

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESGQ

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ER05) - 42U Slim Rack

Provides a 19-inch, 2.0 meter high rack with 42 EIA units of total
space for installing rack mounted CECs and/or expansion units. The
600mm wide rack fits within a data center's 24" floor tiles and
provides better thermal and cable management capabilities. The ER05
rack does not come equipped with a standard front door, rear door or
side covers.

Power Distribution Units (PDU) on the rack are optional. Each PDU
consumes one of six vertical mounting bays and every vertically
mounted PDU requires #ELC0. Each PDU beyond six will consume 1U of
rack space.

The specify feature attaches one Radio Frequency Identification
Device (RFID) tag to a Server CEC, rack, HMC, compute node, or chassis
enclosure. This can be used with MTM (machine type model) rack such
as a 7953-94X or 7014-T42, not a feature code rack such as a #0553.
It applies to newly shipped MTM servers, racks, HMCs, compute nodes,
and chassis enclosures, not MES orders with one exception. POWER5
CECs being upgraded to a POWER6 CEC or POWER6 CECs being upgraded to a
POWER 7 CEC can order this feature. The RFID tag meets the Financial
Services Technology Consortium (FSTC) specifications for IT Data
Center Asset Tracking.

(#ERG0) - Rear rack extension

Extends the rear of a 2.0M enterprise rack (#0553) eight inches or
20.3 cm. The extra depth provides extra space for cable management
helping to keep the center of the rack more open for airflow and
access to the rear of the equipment mounted in the rack. This rear
extension does not increase or decrease the rack's 42 EIA (42U)
vertical size. The extension does increase the floor footprint.

Attributes provided: Adds eight inches or 20.3 cm to the rear of
a 2.0M rack.

Attributes required: 42U 2m enterprise rack such as #0553

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

(#ERHJ) - Quantity 150 of #ESHJ 931 GB SSD 4k SFF-2

This feature ships a quantity of 150 #ESHJ SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESHJ

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESHJ

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERHK) - Quantity 150 of #ESHK 931 GB SSD 4k SFF-2

This feature ships a quantity of 150 #ESHK SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESHK

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ESHK

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERHL) - Quantity 150 of #ESHL 1.86 TB SSD 4k SFF-2

This feature ships a quantity of 150 #ESHL SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESHL

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESHL

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERHM) - Quantity 150 of #ESHM 1.86 TB SSD 4k SFF-2

This feature ships a quantity of 150 #ESHM SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESHM

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: See feature ESHM

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERHN) - Quantity 150 of #ESHN 7.45 TB SSD 4k SFF-2

This feature ships a quantity of 150 #ESHN SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESHN

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ESHN

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERM8) - Quantity 150 of #ESM8 3.72 TB SSD 4k SFF-2

This feature ships a quantity of 150 #ESM8 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

Attributes provided: see feature #ESM8

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 2 (Initial order maximum: 2)

OS level required: see feature ESM8

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ERM9) - Quantity 150 of #ESM9 3.72 TB SSD 4k SFF-2

This feature ships a quantity of 150 #ESM9 SSD. The configurator
may either generate this feature or allow users to select this feature
as they would any other single SSD feature. This feature remains on
the inventory records.

#ES0S (for AIX/LInux/VIOS) and #ES0T (for IBM i) are identical and
have the same CCIN, but have different feature numbers to help IBM
configuration tools understand their planned usage.

Limitations: This drive can not be placed in the same array with a
drive formatted with 528 byte sectors. Also JBOD mode (4096 byte
sectors) is not supported.

Attributes provided: 4K byte formatted 775GB SFF Gen2 SSD eMLC

Attributes required: One GEN2 SFF SAS disk drive bay slot

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 0)

OS level required:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES14) - Mainstream 400GB SSD NVMe M.2 module

400 GB Mainstream solid state drive (SSD) formatted in 4096 byte
sectors (4k). The drive is mounted on the PCIE NVME CARRIER CARD W/ 2
M.2 SOCKETS (feature EC59). DWPD (Drive Write Per Day) rating is 1
calculated over a 5 year period. Approximately 1,095 TB of data can
be written over the life of the drive, but depending on the nature of
the workload may be somewhat larger. Recommend to be used for boot
support and non-intensive workloads. Boot supported.

Note: Must order, at a minimum, quantity of one feature #ES14 module
with each feature #EC59 ordered. Maximum quantity of 2 of feature
#ES14 per feature #EC59.

Attributes provided: Mainstream SSD module

Attributes required: Feature #EC59; Usage beyond boot support and
non-intensive workload could result in throttled performance and/or
high temperatures that lead to time-outs and critical thermal warnings

IBM Manufacturing ships the drive formatted with 4224 byte sectors
for additional data integrity protection which results in 3.86 TB
capacity. The drive can be reformatted to 4096 byte sectors by the
client which results in 4 TB capacity, but with less protection.

IBM Manufacturing ships the drive formatted with 4224 byte sectors
for additional data integrity protection which results in 7.72 TB
capacity. The drive can be reformatted to 4096 byte sectors by the
client which results in 8 TB capacity, but with less protection.

(#ES78) - 387GB SFF-2 SSD 5xx eMLC4 for AIX/Linux

This SFF (2.5") 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. CCIN is 5B16

ES78 and ES79 are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES78 indicates usage by AIX, Linux or VIOS. ES79
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887 EXP24S or #ESLS
EXP24SX drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers
(SFF-1) or in POWER7 system units (SFF-1) or POWER8/POWER9 system
units (SFF-3) SAS bays. Also the drive was not tested with 512 byte
sectors and thus JBOD mode for AIX/Linux is not supported. Note 4k
and 5xx byte sector drives cannot be mixed in the same array. 4k
drives cannot be reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-2 5xx SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES79) - 387GB SFF-2 SSD 5xx eMLC4 for IBM i

This SFF (2.5") 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. CCIN is 5B16

ES78 and ES79 are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES78 indicates usage by AIX, Linux or VIOS. ES79
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8 system units (SFF-3) SAS
bays. Also the drive was not tested with 512 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives can not be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-2 5xx SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 0)

OS level required:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES7E) - 775GB SFF-2 SSD 5xx eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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. CCIN is 5B17

ES7E and ES7F are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7E indicates usage by AIX, Linux or VIOS. ES7F
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887 EXP24S or #ESLS
EXP24SX drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers
(SFF-1) or in POWER7 system units (SFF-1) or POWER8/POWER9 system
units (SFF-3) SAS bays. Also the drive was not tested with 512 byte
sectors and thus JBOD mode for AIX/Linux is not supported. Note 4k
and 5xx byte sector drives cannot be mixed in the same array. 4k
drives cannot be reformatted to 5xx drives (or vice versa).

Attributes provided: one 775GB SFF-2 5xx SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES7F) - 775GB SFF-2 SSD 5xx eMLC4 for IBM i

This SFF (2.5") 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. CCIN is 5B17

ES7E and ES7F are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7E indicates usage by AIX, Linux or VIOS. ES7F
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8 system units (SFF-3) SAS
bays. Also the drive was not tested with 512 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives can not be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 775GB SFF-2 5xx SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 0)

OS level required:

IBM i supported

AIX not supported

Linux not supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES7K) - 387GB SFF-3 SSD 5xx eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B19

ES7K and ES7L are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7K indicates usage by AIX, Linux or VIOS. ES7L
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8/POWER9 system
unit SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1)
SAS bays. Also the drive was not tested with 512 byte sectors and
thus JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte
sector drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-3 5xx SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES7L) - 387GB SFF-3 SSD 5xx eMLC4 for IBM i

This SFF (2.5") 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-3 SAS bays. CCIN is 5B19

ES7K and ES7L are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7K indicates usage by AIX, Linux or VIOS. ES7L
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8 system unit
SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1) SAS
bays. Also the drive was not tested with 512 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-3 5xx SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES7P) - 775GB SFF-3 SSD 5xx eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B1A

ES7P and ES7Q are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7P indicates usage by AIX, Linux or VIOS. ES7Q
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8/POWER9 system
unit SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1)
SAS bays. Also the drive was not tested with 512 byte sectors and
thus JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte
sector drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 775GB SFF-3 5xx SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES7Q) - 775GB SFF-3 SSD 5xx eMLC4 for IBM i

This SFF (2.5") 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-3 SAS bays. CCIN is 5B1A

ES7P and ES7Q are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES7P indicates usage by AIX, Linux or VIOS. ES7Q
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8 system unit
SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1) SAS
bays. Also the drive was not tested with 512 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 775GB SFF-3 5xx SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES80) - 1.9TB Read Intensive SAS 4k SFF-2 SSD for AIX/Linux

1.9 TB SAS 2.5-inch (SFF) read intensive 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
EXP24S. Drive is rated at 6Gb/s though actual performance is
dependent upon multiple factors. CCIN is 5B21. Actual capacity is
1.86 TB but is rounded up for convenience.

Drive is designed for read intensive workloads with light write
activity. Approximately 3,394 TB of data can be written over the life
of the drive, but depending on the nature of the workload may be
somewhat larger. After the warranty period, if the maximum write
capability is achieved, the drive's replacement is not covered under
IBM maintenance.

#ES80 and #ES81 are physically identical drives which have
different feature codes to help the IBM configuration tools understand
how the SSD is used. #ES80 indicates usage by AIX, Linux or VIOS.
#ES81 indicates usage by IBM i.

Limitations: The drive is mounted on a SFF-2 carrier/tray and does
not physically fit into a POWER8/POWER9 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.

(#ES81) - 1.9TB Read Intensive SAS 4k SFF-2 SSD for IBM i

1.9 TB SAS 2.5-inch (SFF) read intensive 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
EXP24S. Drive is rated at 6Gb/s though actual performance is
dependent upon multiple factors. CCIN is 5B21. Actual capacity is
1.86 TB but is rounded up for convenience.

Drive is designed for read intensive workloads with light write
activity. Approximately 3,394 TB of data can be written over the life
of the drive, but depending on the nature of the workload may be
somewhat larger. After the warranty period, if the maximum write
capability is achieved, the drive's replacement is not covered under
IBM maintenance.

#ES80 and #ES81 are physically identical drives which have
different feature codes to help the IBM configuration tools understand
how the SSD is used. #ES80 indicates usage by AIX, Linux or VIOS.
#ES81 indicates usage by IBM i.

Limitations: The drive is mounted on a SFF-2 carrier/tray and does
not physically fit into a POWER8 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES83 and #ES84 are physically identical drives with the
same 5B28 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES83 indicates usage by AIX,
Linux or VIOS. #ES84 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES83 and #ES84 are physically identical drives with the
same 5B28 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES83 indicates usage by AIX,
Linux or VIOS. #ES84 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-3 carrier/tray to fit into a POWER8
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.

(#ES85) - 387GB SFF-2 SSD 4k eMLC4 for AIX/Linux

This SFF (2.5") 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. CCIN is 5B10

ES85 and ES86 are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES85 indicates usage by AIX, Linux or VIOS. ES86
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8/POWER9 system units
(SFF-3) SAS bays. Also the drive was not tested with 4096 byte
sectors and thus JBOD mode for AIX/Linux is not supported. Note 4k
and 5xx byte sector drives cannot be mixed in the same array. 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 387GB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES86) - 387GB SFF-2 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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. CCIN is 5B10

ES85 and ES86 are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES85 indicates usage by AIX, Linux or VIOS. ES86
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8 system units (SFF-3) SAS
bays. Also the drive was not tested with 4096 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8C) - 775GB SFF-2 SSD 4k eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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. CCIN is 5B11

ES8C and ES8D are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8C indicates usage by AIX, Linux or VIOS. ES8D
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8/POWER9 system units
(SFF-3) SAS bays. Also the drive was not tested with 4096 byte
sectors and thus JBOD mode for AIX/Linux is not supported. Note 4k
and 5xx byte sector drives cannot be mixed in the same array. 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 775GB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES8D) - 775GB SFF-2 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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. CCIN is 5B11

ES8C and ES8D are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8C indicates usage by AIX, Linux or VIOS. ES8D
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in #5887/#EL1S EXP24S
drawers (SFF-2). It does not fit in #5802/#5803 I/O drawers (SFF-1)
or in POWER7 system units (SFF-1) or POWER8 system units (SFF-3) SAS
bays. Also the drive was not tested with 4096 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 775GB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8F) - 1.55TB SFF-2 SSD 4k eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") SAS Solid State Drive (SSD) is shipped from IBM
with 1.55TB capacity formatted with 4k (4224) byte sectors. The drive
is supported in SFF-2 SAS bays in the EXP24S (#5887) I/O drawer. CCIN
is 5B12

ES8G and ES8F are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8F indicates usage by AIX, Linux or VIOS. ES8G
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in the EXP24S drawers
(SFF-2 SAS bays). It cannot be used in POWER8/POWER9 system units
(SFF-3) or in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system
units (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.55TB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES8G) - 1.55TB SFF-2 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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) I/O drawer.
CCIN is 5B12

ES8G and ES8F are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8F indicates usage by AIX, Linux or VIOS. ES8G
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in the EXP24S drawer
(SFF-2 SAS bays). It cannot be used in POWER8 system units (SFF-3) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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).

Attributes provided: one 1.55TB SFF-2 4k SSD

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 336 (Initial order maximum: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8J) - 1.9TB Read Intensive SAS 4k SFF-3 SSD for AIX/Linux

1.9 TB SAS 2.5-inch (SFF) read intensive solid state drive (SSD)
formatted in 4224 byte sectors (4k). The drive is mounted on a
2.5-inch SFF-3 carrier/tray to fit in a POWER8/POWER9 system unit.
Drive is rated at 6Gb/s though actual performance is dependent upon
multiple factors. CCIN is 5B20. Actual capacity is 1.86 TB but is
rounded up for convenience.

Drive is designed for read intensive workloads with light write
activity. Approximately 3,394 TB of data can be written over the life
of the drive, but depending on the nature of the workload may be
somewhat larger. After the warranty period, if the maximum write
capability is achieved, the drive's replacement is not covered under
IBM maintenance.

#ES8J and #ES8K are physically identical drives which have
different feature codes to help the IBM configuration tools understand
how the SSD is used. #ES8J indicates usage by AIX, Linux or VIOS.
#ES8K indicates usage by IBM i.

Limitations: The drive is mounted on a SFF-3 carrier/tray and does
not physically fit into an expansion unit such as the EXP24S's SFF-2
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.

Attributes provided: 1.9 TB Read Intensive SSD

Attributes required: Open SFF-3 SAS bay in a POWER8/POWER9 system
unit and controlled by the internal SAS control unit.

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

Note: AIX - Assignment to the VIOS requires VIOS 2.2.4.2 or later

(#ES8K) - 1.9TB Read Intensive SAS 4k SFF-3 SSD for IBM i

1.9 TB SAS 2.5-inch (SFF) read intensive solid state drive (SSD)
formatted in 4224 byte sectors (4k). The drive is mounted on a
2.5-inch SFF-3 carrier/tray to fit in a POWER8 system unit. Drive is
rated at 6Gb/s though actual performance is dependent upon multiple
factors. CCIN is 5B20. Actual capacity is 1.86 TB but is rounded up
for convenience.

Drive is designed for read intensive workloads with light write
activity. Approximately 3,394 TB of data can be written over the life
of the drive, but depending on the nature of the workload may be
somewhat larger. After the warranty period, if the maximum write
capability is achieved, the drive's replacement is not covered under
IBM maintenance.

#ES8J and #ES8K are physically identical drives which have
different feature codes to help the IBM configuration tools understand
how the SSD is used. #ES8J indicates usage by AIX, Linux or VIOS.
#ES8K indicates usage by IBM i.

Limitations: The drive is mounted on a SFF-3 carrier/tray and does
not physically fit into an expansion unit such as the EXP24S's SFF-2
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.

Attributes provided: 1.9 TB Read Intensive SSD

Attributes required: Open SFF-3 SAS bay in a POWER8 system unit
and controlled by the internal SAS control unit.

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ES8N) - 387GB SFF-3 SSD 4k eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B13

ES8N and ES8P are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8N indicates usage by AIX, Linux or VIOS. ES8P
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8/POWER9 system
unit SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1)
SAS bays. Also the drive was not tested with 4096 byte sectors and
thus JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte
sector drives cannot be mixed in the same array. 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 387GB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES8P) - 387GB SFF-3 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B13

ES8N and ES8P are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8N indicates usage by AIX, Linux or VIOS. ES8P
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8 system unit
SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1) SAS
bays. Also the drive was not tested with 4096 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 387GB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8Q) - 775GB SFF-3 SSD 4k eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B14

ES8Q and ES8R are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8Q indicates usage by AIX, Linux or VIOS. ES8R
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8/POWER9 system
unit SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1)
SAS bays. Also the drive was not tested with 4096 byte sectors and
thus JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte
sector drives cannot be mixed in the same array. 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 775GB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES8R) - 775GB SFF-3 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B14

ES8Q and ES8R are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8Q indicates usage by AIX, Linux or VIOS. ES8R
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8 system unit
SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1) SAS
bays. Also the drive was not tested with 4096 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array.

Attributes provided: one 775GB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8V) - 1.55TB SFF-3 SSD 4k eMLC4 for AIX/Linux

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B15

ES8V and ES8W are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8V indicates usage by AIX, Linux or VIOS. ES8W
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8/POWER9 system
unit SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or
in #5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1)
SAS bays. Also the drive was not tested with 4096 byte sectors and
thus JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte
sector drives cannot be mixed in the same array. 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.55TB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Attachment to the VIOS requires VIOS 2.2.3.3 or later, VIOS
2.2.4.0 or later

(#ES8W) - 1.55TB SFF-3 SSD 4k eMLC4 for IBM i

(No longer available as of January 18, 2019)

This SFF (2.5") 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-3 SAS bays. CCIN is 5B15

ES8V and ES8W are physically identical drives which have different
feature codes to help the IBM configuration tools understand how the
SSD is used. ES8V indicates usage by AIX, Linux or VIOS. ES8W
indicates usage by IBM i.

Limitation: Due to physical differences in the carrier/tray on
which the drive is mounted, the SSD only fits in POWER8 system unit
SAS bays (SFF-3). It does not fit in EXP24S drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (SFF-1) SAS
bays. Also the drive was not tested with 4096 byte sectors and thus
JBOD mode for AIX/Linux is not supported. Note 4k and 5xx byte sector
drives cannot be mixed in the same array. 4k drives cannot be
reformatted to 5xx drives (or vice versa).

Attributes provided: one 1.55TB SFF-3 4k SSD

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ES8Y) - 931GB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES8Y and #ES8Z are physically identical drives with the
same 5B29 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES8Y indicates usage by AIX,
Linux or VIOS. #ES8Z 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 POWER8/POWER9 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.

(#ES8Z) - 931GB Mainstream SAS 4k SFF-2 SSD for IBM i

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES8Y and #ES8Z are physically identical drives with the
same 5B29 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES8Y indicates usage by AIX,
Linux or VIOS. #ES8Z 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 POWER8 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES92 and #ES93 are physically identical drives with the
same 5B20 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES92 indicates usage by AIX,
Linux or VIOS. #ES93 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ES92 and #ES93 are physically identical drives with the
same 5B20 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ES92 indicates usage by AIX,
Linux or VIOS. #ES93 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-3 carrier/tray to fit into a POWER8
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.

(#ES96) - 1.86TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

#ES96 and #ES97 are physically identical drives with the same 5B21
CCIN. Different feature codes help the IBM configuration tools
understand how the SSD is used. #ES96 indicates usage by AIX, Linux
or VIOS. #ES97 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 POWER8/POWER9 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.

(#ES97) - 1.86TB Mainstream SAS 4k SFF-2 SSD for IBM i

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

#ES96 and #ES97 are physically identical drives with the same 5B21
CCIN. Different feature codes help the IBM configuration tools
understand how the SSD is used. #ES96 indicates usage by AIX, Linux
or VIOS. #ES97 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 POWER8 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.

Limitation: cannot be used in EXP24S SFF Gen2-bay Drawer because
of physical difference of carrier/tray.

Limitation: Cannot be combined in the same array as a drive of the
same capacity, but using different sector size.

Attributes provided: 300 GB Disk Drive - SFF-3

Attributes required: one SFF-3 drive bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESDN) - 571GB 15K RPM SAS SFF-2 Disk Drive - 528 Block (IBM i)

2.5-inch (Small Form Factor (SFF)) 15k RPM SAS disk drive mounted
in a Gen-2 carrier and supported in SAS SFF-2 bays. With 512 byte
sectors (JBOD) drive capacity is 600GB. With 528 byte sectors (RAID)
drive capacity is 571GB and the drive has additional data integrity
protection. #ESDN and #ESDP are physically identical drives with the
same CCIN. However, IBM Manufacturing always formats the #ESDN with
528 byte sectors. Depending on how the drive is ordered, IBM
Manufacturing will ship #ESDP with either 512 or 528 byte formatting.
Reformatting a disk drive can take significant time, especially on
larger capacity disk drives.

(#ESDP) - 600GB 15K RPM SAS SFF-2 Disk Drive - 5xx Block (AIX/Linux)

2.5-inch (Small Form Factor (SFF)) 15k RPM SAS disk drive mounted
in a Gen-2 carrier and supported in SAS SFF-2 bays. With 512 byte
sectors (JBOD) drive capacity is 600GB. With 528 byte sectors (RAID)
drive capacity is 571GB and the drive has additional data integrity
protection. #ESDN and #ESDP are physically identical drives with the
same CCIN. However, IBM Manufacturing always formats the #ESDN with
528 byte sectors. Depending on how the drive is ordered, IBM
Manufacturing will ship #ESDP with either 512 or 528 byte formatting.
Reformatting a disk drive can take significant time, especially on
larger capacity disk drives.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESE1 and #ESE2 are physically identical drives with the
same 5B2C CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESE1 indicates usage by AIX,
Linux or VIOS. #ESE2 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESE1 and #ESE2 are physically identical drives with the
same 5B2C CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESE1 indicates usage by AIX,
Linux or VIOS. #ESE2 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

(#ESE7) - 3.72TB Mainstream SAS 4k SFF-2 SSD for AIX/Linux

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

#ESE7 and #ESE8 are physically identical drives with the same 5B2D
CCIN. Different feature codes help the IBM configuration tools
understand how the SSD is used. #ESE7 indicates usage by AIX, Linux
or VIOS. #ESE8 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 POWER8/POWER9 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.

(#ESE8) - 3.72TB Mainstream SAS 4k SFF-2 SSD for IBM i

(No longer available as of January 18, 2019)

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

#ESE7 and #ESE8 are physically identical drives with the same 5B2D
CCIN. Different feature codes help the IBM configuration tools
understand how the SSD is used. #ESE7 indicates usage by AIX, Linux
or VIOS. #ESE8 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 POWER8 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.

(#ESEU) - 571GB 10K RPM SAS SFF-2 Disk Drive 4K Block - 4224

571 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. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 500 GB and it
would not have the 4224 byte additional data integrity protection.
Reformatting large drives takes significant time. Limitations: - Can
not 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

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.

Cannot be used in POWER8/POWER9 System unit SFF Gen3-bay Drawer
because of physical difference of carrier/tray.

Cannot be combined in the same array as a drive of the same
capacity, but using different sector size.

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: 300 GB Disk Drive - SFF-2 4K block

Attributes required: one SFF-2 drive bay

Minimum required: 0

Maximum allowed: 672 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESF2) - 1.1TB 10K RPM SAS SFF-2 Disk Drive 4K Block - 4224

1.14 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. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 1.2 TB and it
would not have the 4224 byte additional data integrity protection.
Reformatting large drives takes significant time. Limitations: - Can
not 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

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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.3.3 or later

(#ESF4) - 571GB 10K RPM SAS SFF-3 Disk Drive 4K Block - 4224

571 GB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive on
Gen-3 carrier/tray. Supported in SFF-3 SAS bays such as found in
POWER8 servers. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 600 GB and it
would not have the 4224 byte additional data integrity protection.
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-2
bay due to carrier/ tray differences

Cannot be combined in the same array as a drive using different
sector size.

Physically does not fit in a SFF-1 or SFF-2 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: 600GB 10K RPM SFF-3 Disk 4K

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.3.3 or late

(#ESF8) - 1.1TB 10K RPM SAS SFF-3 Disk Drive 4K Block - 4224

1.14 TB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive
on Gen-3 carrier/tray. Supported in SFF-3 SAS bays such as found in
POWER8 servers. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 1.2 TB and it
would not have the 4224 byte additional data integrity protection.
Reformatting large drives takes significant time. Limitations: - Can
not be combined in the same array as a drive using different sector
size - Physically does not fit in a SFF-1 or SFF-2 bay due to carrier/
tray differences

Cannot be combined in the same array as a drive using different
sector size

Physically does not fit in a SFF-1 or SFF-2 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.

Cannot be used in EXP24S SFF Gen2-bay Drawer because of physical
difference of carrier/tray.

Cannot be combined in the same array as a drive of the same
capacity, but using different sector size.

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.

Cannot be used in EXP24S SFF Gen2-bay Drawer because of physical
difference of carrier/tray.

Cannot be combined in the same array as a drive of the same
capacity, but using different sector size.

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.

Cannot be used in POWER8/POWER9 System unit SFF Gen3-bay Drawer
because of physical difference of carrier/tray.

Cannot be combined in the same array as a drive of the same
capacity, but using different sector size.

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: 600 GB Disk Drive - SFF-2 4K block

Attributes required: one SFF-2 SAS bay

Minimum required: 0

Maximum allowed: 672 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: Requires VIOS 2.2.3.3 or later when assigned to the VIOS.

(#ESFS) - 1.7TB 10K RPM SAS SFF-2 Disk Drive 4K Block - 4224

1.71 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. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 1.8 TB and it
would not have the 4224 byte additional data integrity protection.
Reformatting large drives takes significant time. Limitations: - Can
not 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

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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.3.3 or later

(#ESFU) - 1.7TB 10K RPM SAS SFF-3 Disk Drive 4K Block - 4224

1.71 TB 2.5-inch (Small Form Factor (SFF)) 10k rpm SAS disk drive
on Gen-3 carrier/tray. Supported in SFF-3 SAS bays such as found in
POWER8 system. Disk is formatted for 4224 byte sectors. If
reformatted to 4096 byte sectors, its capacity would be 1.8 TB and it
would not have the 4224 byte additional data integrity protection.
Reformatting large drives takes significant time. Limitations: - Can
not 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

Cannot be combined in the same array as a drive using different
sector size

Physically does not fit in a SFF-1 or SFF-2 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-3 Disk 4K

Attributes required: one SFF-3 SAS bay

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: VIOS 2.2.3.3 or later

(#ESG5) - 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.

Features #ESG5 and #ESG6 are physically identical drives with the
same CCIN of 5B16. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESG5 indicates
usage by AIX, Linux or VIOS. ESG6 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 POWER8/POWER9 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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESG9) - 387GB Enterprise SAS 5xx SFF-3 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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESG9 and #ESGA are physically identical drives with the
same CCIN of 5B19. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESG9 indicates
usage by AIX, Linux or VIOS. ESGA 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 POWER8/POWER9 system unit SAS bays
(SFF-3). It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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-3 5xx SSD

Attributes required: SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGA) - 387GB Enterprise SAS 5xx SFF-3 SSD for IBM i

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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESG9 and #ESGA are physically identical drives with the
same CCIN of 5B19. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESG9 indicates
usage by AIX, Linux or VIOS. ESGA 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 POWER8 system unit SAS bays (SFF-3).
It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in #5802/#5803
I/O drawers (SFF-1) or in POWER7 system units (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-3 5xx SSD

Attributes required: SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ESGB) - 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.

Features #ESGB and #ESGC 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. ESGB indicates
usage by AIX, Linux or VIOS. ESGC 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 POWER8/POWER9 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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGC) - 387GB Enterprise SAS 4k SFF-2 SSD for IBM i

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.

Features #ESGB and #ESGC 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. ESGB indicates
usage by AIX, Linux or VIOS. ESGC 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 POWER8 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: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGD) - 387GB Enterprise SAS 4k SFF-3 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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGD and #ESGE are physically identical drives with the
same CCIN of 5B13. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGD indicates
usage by AIX, Linux or VIOS. ESGE 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 POWER8/POWER9 system unit SAS bays
(SFF-3). It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGE) - 387GB Enterprise SAS 4k SFF-3 SSD for IBM i

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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGD and #ESGE are physically identical drives with the
same CCIN of 5B13. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGD indicates
usage by AIX, Linux or VIOS. ESGE 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 POWER8 system unit SAS bays (SFF-3).
It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in #5802/#5803
I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGF) - 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.

Features #ESGF and #ESGG are physically identical drives with the
same CCIN of 5B17. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGF indicates
usage by AIX, Linux or VIOS. ESGG 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 POWER8/POWER9 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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGH) - 775GB Enterprise SAS 5xx SFF-3 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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGH and #ESGJ are physically identical drives with the
same CCIN of 5B1A. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGH indicates
usage by AIX, Linux or VIOS. ESGJ 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 POWER8/POWER9 system unit SAS bays
(SFF-3). It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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-3 5xx SSD

Attributes required: SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGJ) - 775GB Enterprise SAS 5xx SFF-3 SSD for IBM i

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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGH and #ESGJ are physically identical drives with the
same CCIN of 5B1A. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGH indicates
usage by AIX, Linux or VIOS. ESGJ 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 POWER8 system unit SAS bays (SFF-3).
It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in #5802/#5803
I/O drawers (SFF-1) or in POWER7 system units (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-3 5xx SSD

Attributes required: SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 0)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#ESGK) - 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.

Features #ESGK and #ESGL 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. ESGK indicates
usage by AIX, Linux or VIOS. ESGL 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 POWER8/POWER9 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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGL) - 775GB Enterprise SAS 4k SFF-2 SSD for IBM i

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.

Features #ESGK and #ESGL 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. ESGK indicates
usage by AIX, Linux or VIOS. ESGL 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 POWER8 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: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGM) - 775GB Enterprise SAS 4k SFF-3 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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGM and #ESGN are physically identical drives with the
same CCIN of 5B14. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGM indicates
usage by AIX, Linux or VIOS. ESGN 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 POWER8/POWER9 system unit SAS bays
(SFF-3). It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGN) - 775GB Enterprise SAS 4k SFF-3 SSD for IBM i

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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGM and #ESGN are physically identical drives with the
same CCIN of 5B14. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGM indicates
usage by AIX, Linux or VIOS. ESGN 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 POWER8 system unit SAS bays (SFF-3).
It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in #5802/#5803
I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGP) - 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.

Features #ESGP and #ESGQ 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. ESGP indicates
usage by AIX, Linux or VIOS. ESGQ 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 POWER8/POWER9 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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGQ) - 1.55TB Enterprise SAS 4k SFF-2 SSD for IBM i

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.

Features #ESGP and #ESGQ 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. ESGP indicates
usage by AIX, Linux or VIOS. ESGQ 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 POWER8 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: 250)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGR) - 1.55TB Enterprise SAS 4k SFF-3 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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGR and #ESGS are physically identical drives with the
same CCIN of 5B15. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGR indicates
usage by AIX, Linux or VIOS. ESGS 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 POWER8/POWER9 system unit SAS bays
(SFF-3). It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in
#5802/#5803 I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESGS) - 1.55TB Enterprise SAS 4k SFF-3 SSD for IBM i

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-3 SAS bays. This drive is rated at 10
DWPD (Drive Writes Per Day) calculated over a 5-year period.

Features #ESGR and #ESGS are physically identical drives with the
same CCIN of 5B15. Different feature codes to help the IBM
configuration tools understand how the SSD is used. ESGR indicates
usage by AIX, Linux or VIOS. ESGS 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 POWER8 system unit SAS bays (SFF-3).
It does not fit in EXP24S or EXP24SX drawers (SFF-2) or in #5802/#5803
I/O drawers (SFF-1) or in POWER7 system units (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-3 4k SSD

Attributes required: one SFF-3 SAS bay, PCIe3 SAS controller

Minimum required: 0

Maximum allowed: 18 (Initial order maximum: 18)

OS level required:

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESH2) - SAP HANA Identifier for 9223-42H

SAP HANA tracking feature that defines manufacturing routing.

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

(#ESHJ) - 931 GB 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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHJ and #ESHK are physically identical drives with the
same 5B29 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHJ indicates usage by AIX,
Linux or VIOS. #ESHK 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

(#ESHK) - 931 GB Mainstream SAS 4k SFF-2 SSD for IBM i

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHJ and #ESHK are physically identical drives with the
same 5B29 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHJ indicates usage by AIX,
Linux or VIOS. #ESHK 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

(#ESHL) - 1.86 TB 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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHL and #ESHM are physically identical drives with the
same 5B21 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHL indicates usage by AIX,
Linux or VIOS. #ESHM 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

(#ESHM) - 1.86 TB Mainstream SAS 4k SFF-2 SSD for IBM i

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHL and #ESHM are physically identical drives with the
same 5B21 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHL indicates usage by AIX,
Linux or VIOS. #ESHM 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

(#ESHN) - 7.45 TB 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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

#ESHN has 5B2F CCIN. Different feature codes help the IBM
configuration tools understand how the SSD is used. #ESHN indicates
usage by AIX, Linux or VIOS.

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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHS and #ESHT are physically identical drives with the
same 5B2B CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHS indicates usage by AIX,
Linux or VIOS. #ESHT 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHS and #ESHT are physically identical drives with the
same 5B2B CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHS indicates usage by AIX,
Linux or VIOS. #ESHT 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHU and #ESHV are physically identical drives with the
same 5B20 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHU indicates usage by AIX,
Linux or VIOS. #ESHV 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHU and #ESHV are physically identical drives with the
same 5B20 CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESHU indicates usage by AIX,
Linux or VIOS. #ESHV 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESHW has 5B2E CCIN. Different feature codes help the IBM
configuration tools understand how the SSD is used. #ESHW indicates
usage by AIX, Linux or VIOS.

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-3 carrier/tray to fit into a
POWER8/POWER9 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 can not be mixed in the same
array. Older SAS adapters such as PCIe2 or earlier do not support 4k
drives.

(#ESLL) - EXP12SX SAS Storage Enclosure

The EXP12SX is a storage expansion enclosure with twelve 3.5-inch
large form factor (LFF) SAS bays. It supports up to 12 hot-swap Hard
Disk Drives (HDD) in only 2 EIA of space in a 19-inch rack. The
EXP12SX SFF bays use LFF gen1 (LFF-1) carriers/trays. 4k byte sector
drives (4096 or 4224) are supported.

With AIX/Linux/VIOS, the EXP12SX can be ordered with four sets of 3
bays (mode 4), two sets of 6 bays (mode 2) or one set of 12 bays (mode
1). The mode setting can be changed in the field using software
commands along with a specifically 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 EXP12SX 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 EXP12SX has
been designed to support up to 12Gb throughput if future SAS adapters
support that capability.

The EXP12SX 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.

See also the 24-bay Small Form Factor (SFF) EXP24SX SAS Storage
Enclosure (feature #ESLS) for higher performance drives with lower
capacity.

(#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 specifically 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.

See also the 12-bay Large Form Factor (LFF) EXP12SX SAS Storage
Enclosure (feature #ESLL) for higher capacity drives with lower
performance.

(#ESM8) - 3.72 TB 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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESM8 and #ESM9 are physically identical drives with the
same 5B2D CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESM8 indicates usage by AIX,
Linux or VIOS. #ESM9 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

(#ESM9) - 3.72 TB Mainstream SAS 4k SFF-2 SSD for IBM i

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:

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESM8 and #ESM9 are physically identical drives with the
same 5B2D CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESM8 indicates usage by AIX,
Linux or VIOS. #ESM9 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 POWER8/POWER9 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 can not be
mixed in the same array. Older SAS adapters such as PCIe2 or earlier
do not support 4k drives.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESMQ and #ESMR are physically identical drives with the
same 5B2C CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESMQ indicates usage by AIX,
Linux or VIOS. #ESMR 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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 POWER8 and POWER9 servers, see the Terms and
Conditions section or IBM Knowledge Center for additional detail.

Features #ESMQ and #ESMR are physically identical drives with the
same 5B2C CCIN. Different feature codes help the IBM configuration
tools understand how the SSD is used. #ESMQ indicates usage by AIX,
Linux or VIOS. #ESMR 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-3 carrier/tray to fit into a
POWER8/POWER9 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.

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: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESPL) - Quantity 150 of #ESNL (283GB 15k SFF-2)

This feature ships a quantity of 150 #ESNL 283GB 15K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Limitation: This HDD feature is not supported in the EXP24S drawer
(#5887 or #EL1S).

Attributes provided: See feature #ESNL

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: see feature ESNL

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESPM) - Quantity 150 of #ESNM (300GB 15k SFF-2)

This feature ships a quantity of 150 #ESNM 300GB 15K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Limitation: This HDD feature is not supported in the EXP24S drawer
(#5887 or #EL1S).

Attributes provided: See feature #ESNM

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: see feature ESNM

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESPQ) - Quantity 150 of #ESNQ (571GB 15k SFF-2)

This feature ships a quantity of 150 #ESNQ 571GB 15K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Limitation: This HDD feature is not supported in the EXP24S drawer
(#5887 or #EL1S).

Attributes provided: See feature #ESNQ

Attributes required: 150 SFF-2 SAS bays in EXP24S or EXP24SX
drawers

Minimum required: 0

Maximum allowed: 4 (Initial order maximum: 4)

OS level required: see feature ESNQ

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#ESPR) - Quantity 150 of #ESNR (600GB 15k SFF-2)

This feature ships a quantity of 150 #ESNR 600GB 15K RPM 4K SAS
SFF-2, units. The configurator may either generate this feature or
allow users to select this feature as they would any other single disk
unit feature. This feature remains on the inventory records.

Limitation: This HDD feature is not supported in the EXP24S drawer
(#5887 or #EL1S).

USB Internal Docking Station accommodates RDX removable disk
cartridge of any capacity. The disk are in a protective rugged
cartridge enclosure that plug into the docking station. The docking
station holds one removable rugged disk drive/cartridge at a time.
The rugged removable disk cartridge and docking station provides
saves, restores and backs up similar to tape drive. This can be an
excellent alternative to DAT72, DAT160, 8mm, and VXA-2 and VXA-320
tapes. The drive is controlled by an internal USB port in the system
unit. CCIN: 632C-0D4

#EU00 is a follow on product to the #EU03 RDX docking station.
#EU00 has identical function and performance to the external #EUA4 RDX
docking station.

#EU00 is controlled by an internal USB port in the system unit.

Attributes provided: USB RDX Internal Docking Station

Attributes required: Available RDX bay and at least one Removable
Disk Drive Cartridge such as the #EU01, #1107 or #EU08.

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EU01) - 1TB Removable Disk Drive Cartridge

1TB Removable Disk Drive Cartridge (#EU01) provides a RDX disk
drive in a rugged cartridge to be used in an RDX Internal and External
Docking Station such as the (#1103, #1104 or #1123, #EU03, #EU04
,#EU23, or #EU07 1TB is uncompressed. docking station. 1TB is
uncompressed. Compression/decompression is provided by the operating
system, not the drive itself. Feature EU01 is not entitled under the
IBM Maintenance Agreement, if one is purchased.

USB Eternal Docking Station accommodates RDX removable disk
cartridge of any capacity. The disk are in a protective rugged
cartridge enclosure that plug into the docking station. The docking
station holds one removable rugged disk drive/cartridge at a time.
The rugged removable disk cartridge and docking station backs up
similar to tape drive. This can be an excellent alternative to DAT72,
DAT160, 8mm, and VXA-2 and VXA-320 tapes. CCIN: 632C-0D4

#EU04 is a follow on product to the #1104 RDX docking station.
#EU04 has identical function and performance to the internal #EU03 RDX
docking station.

(#EU08) - RDX 320 GB Removable Disk Drive

Provides a RDX disk drive in a rugged cartridge to be used in an
RDX docking station such as #EU03, #EU04, #EU23, #1123, #1103, #1104
or #EU07. Capacity is 320 GB is uncompressed. Compression/
decompression is provided by the operating system, not the drive
itself. Feature EU08 is not entitled under the IBM Maintenance
Agreement, if one is purchased.

Attributes provided: 320 GB RDX rugged disk/cartridge

Attributes required: One docking station

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 0)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EU0B) - Operator Panel LCD Display

This feature provides a cable that connects the system's Operator
Panel to the DASD backplane. Used on a Rack-mount drawer with 3.5"
DASD.

Attributes provided: LCD Display

Attributes required: None

Minimum required: 0

Maximum allowed: 1 (Initial order maximum: 1)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EU15) - 1.5TB Removable Disk Drive Cartridge

The 1.5 TB Removable Disk Drive Cartridge provides a RDX disk drive
in a rugged cartridge to be used in an RDX Internal and External
Docking Station such as (#1103, #1104 or #1123, #EU03, #EU04 ,#EU23,
or #EU07. 1.5TB is uncompressed. Compression/ decompression is
provided by the operating system, not the drive itself. Feature EU015
is not entitled under the IBM Maintenance Agreement, if one is
purchased.

Attributes provided: 1.5TB RDX rugged disk cartridge

Attributes required: RDX docking station

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 0)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Supported

CSU: Yes

Return parts MES: No

(#EU19) - Cable Ties & Labels

Set of 10 hook and loop fabric, often called VELCRO(R) ties 35.5 cm
(14-inch) in length to conveniently attach cables or cords to rack or
other cables. Set of 16 labels 2x4 inches (5x10 cm) in size to
identify cables when installing or moving or servicing equipment.

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: No

(#EU2T) - 2TB Removable Disk Drive Cartridge (RDX)

The 2.0TB Removable Disk Drive Cartridge provides a RDX disk drive
in a rugged cartridge to be used in an RDX Internal and External
Docking Station such as (#1103, #1104 or #1123, #EU03, #EU04 ,#EU23,
or #EU07. 2.0TB is uncompressed. Compression/ decompression is
provided by the operating system, not the drive itself. Feature EU2T
is not entitled under the IBM Maintenance Agreement, if one is
purchased.

Attributes provided: 2.0TB RDX rugged disk cartridge

Attributes required: None.

Minimum required: 0

Maximum allowed: 9999 (Initial order maximum: 250)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

(#EUA4) - RDX USB External Docking Station

USB External Docking Station which accommodates RDX removable disk
cartridge of any capacity. The disk is in a protective rugged
cartridge enclosure that plug into the docking station. The docking
station holds one removable rugged disk drive/cartridge at a time.
The rugged removable disk cartridge and docking station can be used
similar to a tape drive. This can be an excellent entry system save/
restore option and a good alternative to DAT72, DAT160, 8mm, and VXA-2
and VXA-320 tapes. CCIN: 63B8-005.

#EUA4 attaches to a Power server via a USB cable which carries data
and control information. It is not powered by the USB port on the
Power System or Power System USB adapter, but has a separate
electrical line cord. Physically the #EUA4 docking station is a
standalone enclosure about 2.0 x 7.0 x 4.25 inches in size which can
sit on a shelf or on top of equipment in a rack.

#EUA4 is a follow on product to the #EU04 RDX docking station.
#EUA4 has identical performance and identical application function to:

Previously announced #EU04 and #1104 USB external docking stations

Top mount #EUA3 USB docking station used in the Power S814 tower
configuration

#EU03 USB internal docking stations used in Power 720 system units

#EU03 USB docking station available in the rack mounted IBM
7226-1U3 Multimedia Drawer

The RDX USB External Docking Station (Feature EUA4) is only
orderable in the following countries/regions:

CAN--->

Canada and Caribbean North.

LA--->

Mexico.

Attributes provided:

USB 3.0 RDX External Docking Station

USB 3.0 Cable (2.7 meter or 8.8 foot)

Four line cords (1.85 meter or 6 foot) with type A, G, F or I plug
(see http://www.iec.ch/worldplugs for type definition and country-
specific usage)

One power jumper cord as an alternative to using one of the four
power line cords above. This would draw power from a PDU in a rack.

Power Adapter using single phase 110-250V 50-60Hz power source

Attributes required:

One USB port on server or server's USB adapter

At least one Removable Disk Drive Cartridge such as #EU01 or #1107

Firmware version 860.20, or higher

Minimum required: 0

Maximum allowed: 5 (Initial order maximum: 5)

OS level required:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

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, and 9223-42H systems.

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:

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

AIX supported

IBM i supported

Initial Order/MES/Both/Supported: Both

CSU: Yes

Return parts MES: No

Note: If using #EUA5 on this system's integrated USB 3.0 ports, it
must be connected to the front USB 3.0 port. #EUA5 is not supported
on the rear USB 3.0 ports.

(#EUC6) - Core Use HW Feature

A Service Provider (SP) under a "revenue payment" contract with IBM
pays IBM a percentage of revenue generated on their infrastructure
used to deliver cloud services. The contract stipulates that each
quarter the service provider calculates the amount due IBM and then
purchases a quantity of features that satisfies the required payment.
Each occurrence of this feature represents one billing unit.

Attributes provided: None

Attributes required: None

Minimum required: 0

Maximum allowed: 250 (Initial order maximum: 0)

OS level required: None

Initial Order/MES/Both/Supported: MES

CSU: Yes

Return parts MES: No

(#EUC7) - Core Use HW Feature 10X

A Service Provider (SP) under a "revenue payment" contract with IBM
pays IBM a percentage of revenue generated on their infrastructure
used to deliver cloud services. The contract stipulates that each
quarter the service provider calculates the amount due IBM and then
purchases a quantity of features that satisfies the required payment.
Each occurrence of this feature represents ten billing units.