Family 3906+02 IBM Emperor II

IBM United States Sales Manual
Revised:  April 10, 2018.

Table of contents
TOC Link Product life cycle dates TOC Link Technical description
TOC Link Abstract TOC Link Publications
TOC Link Highlights TOC Link Features
TOC Link Description TOC Link Accessories
TOC Link Product positioning TOC Link Supplies
TOC Link Models  

 
Product life cycle dates
Type Model Announced Available Marketing Withdrawn Service Discontinued
3906-LM1 2017/09/122017/09/13 - -
3906-LM2 2017/09/122017/09/13 - -
3906-LM3 2017/09/122017/09/13 - -
3906-LM4 2017/09/122017/09/13 - -
3906-LM5 2017/09/122017/09/13 - -

Back to topBack to top
 
Abstract

The 3906 IBM Emperor II is a highly engineered system designed to thoroughly protect data, the new business currency, with speed and agility at scale.

The world is in the middle of a transformation which is having a profound effect on us as individuals, on how businesses are run, and on how business is transacted. In this ever-more-digital world, the new currency is data and the insights that data can provide. It is a world that requires ultimate trust in the data that businesses collect, create, and store.

As a natural evolution of the digital transformation, the complexity of the data value chain has also expanded. The expectations of consumers, suppliers, and business partners have grown. They demand security, transparency, and greater value in every interaction and transaction as this new currency is exchanged. Securing data from both internal and external threats is of utmost importance, yet only a portion of data is adequately protected today. Failure to secure such data has both financial and reputational consequences.

Digital experiences are no longer hosted entirely on premises through data centers but are delivered in combination with hybrid clouds. This is by design as businesses must be open and connected to drive innovation at speed. They must accelerate development and delivery of secure, scalable services to address new opportunities and challenges before a competitor steals the advantage.

IBM Emperor II is designed to provide highly securable data for businesses looking to thrive in a data-centric economy.

IBM Emperor II, machine type 3906, provides the infrastructure to meet the demands of a digital business. Emperor II is a highly engineered system designed to thoroughly protect data, the new business currency, with speed and agility at scale. Emperor II extends IBM LinuxONE high end data serving leadership with the performance and scale needed to address today's business demands, with more cores, more memory, and more FCP I/O throughput as compared to the inaugural IBM Emperor. The Emperor II offers Industry-leading Java performance; vertical scale to 170 cores with the equivalent capacity to consolidate many x86 data serving cores; simplification to make the most of your Linux skill base and improve time to value; Single Instruction, Multiple Data (SIMD) enhancements to accelerate analytic workloads and decimal computations critical to financial applications; and pause-less garbage collection to enable vertical scaling of Java workloads. Emperor II continues in the same footprint as its predecessor the original LinuxONE Emperor, 42u in height with a 38u height reduction. It runs at 5.2GHz processor frequency, offers 8TB memory/drawer for up to 32TB per machine, and 85 partitions. Emperor II also offers Dynamic Partition Manager (DPM), and enhanced computing for TKE and HMC. The use of high performance and highly pervasive encryption on Emperor II for data that flows to and from IBM's Secure Service Container framework allows nearly all data to be encrypted.

Model abstract 3906-LM1

The IBM 3906 Model LM1 supports 256 to 8000 GB of memory, from 1 to 33 processor units (PUs), and up to 10 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 80 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), and compression (zEDC Express).

Model abstract 3906-LM2

The IBM 3906 Model LM2 supports 256 to 16192 GB of memory, from 1 to 69 processor units (PUs), and up to 20 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+) the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), and compression (zEDC Express).

Model abstract 3906-LM3

The IBM 3906 model LM3 supports 256 to 24384 GB of memory, from 1 to 105 processor units (PUs), and up to 30 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), and compression (zEDC Express).

Model abstract 3906-LM4

The IBM 3906 model LM4 supports 256 to 32576 GB of memory, from 1 to 141 processor units (PUs), and up to 40 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+) the Ethernet local area network (OSA-Express6S, and 10GbE RoCE Express2), and compression (zEDC Express).

Model abstract 3906-LM5

The IBM 3906 model LM5 supports 256 to 32576 GB of memory, from 1 to 170 processor units (PUs), and up to 40 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), and compression (zEDC Express).
Back to topBack to top
 

Highlights

The IBM Emperor II extends IBM LinuxONE high-end data-serving leadership with:

  • Unmatched performance and vertical scale

    The Emperor II delivers the performance and scale needed to address today's business demands, with 20% more cores, 2.2 times more memory, and 25% more FCP I/O throughput as compared to the inaugural IBM Emperor. It provides a platform that can manage your data as a real-time single source of truth, and one that can respond to business needs with uninterrupted growth and speed while providing a richer user experience. The Emperor II offers:

    • Industry-leading Java performance, up to 50% faster than on x86 alternatives
    • Vertical scale to 170 cores with the equivalent capacity to consolidate hundreds of x86 data-serving cores
    • Simplification to make the most of your Linux skill base and improve time to value
    • Single Instruction, Multiple Data (SIMD) enhancements to accelerate analytic workloads and decimal computations critical to financial applications
    • Pause-less garbage collection to enable vertical scaling of Java workloads while maintaining predictable response times
  • Efficient and powerful security

    With Emperor II you can protect your valued data, whether in flight or at rest, with low overhead, without changing your applications and with minimal impact to service level agreements (SLAs). It features:

    • Encryption for your data at rest, with no changes to your applications, and with better performance than x86 alternatives
    • Protected key CPACF support where encryption keys are cryptographically protected to help secure your encryption key on disk and in memory, mitigating risk of compromise
    • Industry-leading secure Java performance delivering TLS transactions 2 to 3 times faster than on typical x86 alternatives
    • Protection of data in flight over the network with full end-to-end network security
    • IBM's intention to expand the use of its industry-exclusive IBM Secure Service Container framework to enable the development of container-based applications with industry-leading orchestration enabling users to seamlessly integrate their LinuxONE with their enterprise-wide DevOps container strategy
  • Foundational capabilities for data serving and next-generation apps

    With Emperor II you have the flexibility to modernize your data and transactional systems and take advantage of the ever-growing open source movement. You can:

    • Add performance, scale, and security without trade-offs to new DB2 and open source database as a service (DBaaS) deployments
    • Develop new Blockchain applications based on the proven IBM Blockchain Platform
    • Consolidate databases for software license and operational savings
    • Support data-in-memory applications and new workloads using 32 TB of memory
    • Take advantage of very fast I/O capable of over 190K 8K read IOPs per FCP link or 380 8K read IOPs per FCP card

Back to topBack to top
 
Description

IBM LinuxONE is an all-Linux enterprise platform for open innovation that combines the best of Linux and open technology with the best of enterprise computing in ONE platform. It delivers a single system built on one of the industry's fastest commercially available server processors and is built to be the backbone of the interconnected data-driven era, setting new standards in transaction volume, speed, and trust.

This member of the IBM LinuxONE family, the IBM Emperor II (Emperor II), (TM), is designed to provide a secure, scalable data foundation. IBM Emperor II provides a scalable, highly available infrastructure that delivers differentiated value to enable business growth, reduce cost, and protect existing investments.

Today's announcement continues IBM's Linux enterprise server leadership with IBM Emperor II, offering:

  • More total system capacity as compared to the original LinuxONE Emperor for exceptional scale in a single footprint.
  • Faster uniprocessor performance as compared to the original LinuxONE Emperor.
  • 170 cores to configure (versus 141 on the original LinuxONE Emperor).
  • Up to 32 terabytes (TB) of available Redundant Array of Independent Memory (RAIM) real memory per server to help improve transaction response times, lower CPU costs, simplify capacity planning, enlarge in-memory buffer pools, and ease deploying memory-intensive workloads.
  • 2x more on-chip cache per core, compared to the original LinuxONE Emperor, to minimize memory waits while maximizing the throughput of concurrent workloads -- perfectly optimized for data serving.
  • A design for pervasive encryption allowing you to encrypt many new data sets transparently, which can help you to provide an envelope of protection around data placed on IBM LinuxONE Emperor II. This includes cryptographic performance improvements with the Crypto Express6S (#0893) and the Emperor II processor-based cryptography with the CP Assist for Cryptographic Functions that helps enable the protection of data in flight or at rest.
  • Hardware accelerated encryption on every core with the Central Processor Assist for Cryptographic Function (CPACF) feature which is designed to provide faster encryption and decryption than previous servers.
  • Economies of scale with next-generation multithreading (SMT) for Linux workloads, new support for the I/O System Assist Processor (SAP), 2x AES performance over the original LinuxONE Emperor, a True Random Number Generator, SHA3 support, and RSA/ECC acceleration.
  • Instructions in Single Instruction, Multiple Data (SIMD) which are designed to give a performance boost for traditional workloads using COBOL and new applications like analytics.
  • FICON Express16S+ (#0427, 0428) which is designed with a boost in I/O rates and a reduction in single stream latency to help absorb large application and transaction spikes driven by large unpredictable analytic and mobile workloads.
  • Improved compression ratio (using Huffman coding) and order-preserving compression for the on-chip compression coprocessor which results in fewer CPU cycles to enable further compression of data, improving memory, transfer, and disk efficiency.
  • 10 GbE RoCE Express2 (#0412) with 4x more virtual functions per adapter and a performance improvement.
  • IBM Hardware Management Console (HMC) 2.14 with simplification updates to improve workspace and manage system time. Security features include Multifactor Authentication and an HMC Mobile application for monitor and recover action controls.
  • IBM Secure Service Container which can be used to create isolated partitions helping to protect data and applications automatically --helping to keep them safe from insider threats as well as external cybercriminals.
  • IBM Dynamic Partition Manager enhancements which provide a simplified, consumable, enhanced IBM LinuxONE experience, reducing the barriers of adoption for new and existing Linux, KVM for IBM Z Systems, and z/VM clients.
  • Trusted Key Entry (TKE) 9.0 License Internal Code (LIC).
  • Improved Java performance through support for reducing program pauses during Java garbage collection.
  • Nonraised floor option, offering flexible possibilities for the data center.
  • Optional water cooling, providing the ability to cool systems with user-chilled water.
  • Optional high-voltage dc power, which can help IBM LinuxONE clients save on their power bills.
  • Optional top exit power and I/O cabling designed to provide increased flexibility.
  • ASHRAE class A3 for robustness, data center flexibility, and energy savings.
  • Upgradability within the IBM LinuxONE Emperor II family, and into the z14 family.

The performance advantage

IBM Emperor II is available with up to 170 configurable cores using one of the world's fastest commercial processors running at 5.2 GHz, for impressive performance and massive scaling. It can support up to 8,000 virtual Linux servers on a single footprint.

Next-generation availability

The IBM Emperor II processor builds upon the Reliability, Availability and Serviceability (RAS) of the original LinuxONE Emperor, with the following RAS improvements:

  • IBM Emperor II Level 3 cache enhancements using powerful symbol ECC that now spreads cache data over multiple physical cache arrays. This enables the detection and correction of multibit errors, making the Level 3 cache more resilient and fault tolerant.
  • Preemptive DRAM marking added to main memory to isolate and recover failures more quickly.
  • Improved small array error handling in the processor cores.
  • Additional error thresholding to the processor core to isolate "sick but not dead" failure scenarios.
  • An increase in the number of "Resource Groups" (from 2 to 4) to help reduce the impact of firmware updates and failures.

Common Criteria Evaluation Assurance Level 5+ (EAL 5+) certification

The IBM Emperor II is designed for Common Criteria Evaluation Assurance Level 5+ (EAL5+) certification for security of logical partitions. This means that the IBM Emperor II is designed to prevent an application running on one operating system image on one LPAR from accessing application data running on a different operating system image on another LPAR on the server.

Common Cryptographic Architecture (CCA) enhancements

PCI PTS HSM compliance

The Crypto Express6S coprocessor with CCA 6.0 is designed to comply with the Payment Card Industry (PCI) PIN Transaction Security (PTS) Hardware Security Module (HSM) Standard. PCI security standards are developed by the Payment Card Industry Security Standards Council to help ensure security in the payment card industry with guidance and direction to HSM vendors to help meet the security needs of the financial payments industry.

The requirements in PCI PTS HSM standards are intended to enhance security for operations that process sensitive data with requirements in key management, HSM API functions, device physical security, controls during manufacturing and delivery, device administration, and a number of other areas.

The Crypto Express6S manufacturing and delivery processes are enhanced with Emperor II to comply with PCI PTS HSM and, with CCA 6.0, introduce several new capabilities both for PCI PTS HSM compliance mode and for general use:

  1. A derived key hierarchy so that PCI PTS HSM compliance-tagged key tokens may be used alongside existing keys and services in a nondisruptive fashion -- with existing master keys.

  2. Nondisruptive transition to PCI PTS HSM mode: Using TKE 9.0, a domain of the Crypto Express6S coprocessor with CCA 6.0 may be placed in PCI PTS HSM compliant mode with no disruption to other domains or to normal or legacy services using the domain that is moved to PCI PTS HSM compliant mode.

  3. Secure Audit Log hosted from the Crypto Express6S coprocessor with CCA 6.0. Required by the PCI PTS HSM standard, this audit log covers all administrative actions and is managed by TKE 9.0. The audit log is nondisruptive to normal application processing for domains where it is active.

  4. Secure public key infrastructure: The Crypto Express6S coprocessor with CCA 6.0 adds native X.509 certificate support including PKCS #10 certificate request generation through a PKI hosted from the coprocessor. Trust chain certificates are managed via TKE 9.0.

  5. Migration planning assistance through active application reporting. The Crypto Express6S coprocessor with CCA 6.0 can report in real time what operations and keys will need attention if they are planned for use with PCI PTS HSM compliant-tagged keys. Report details and activity depend on host access library/operating system configuration.

  6. CPACF exportable AES cipher key support added for AES cipher keys created using new options in CCA 6.0.

Trusted Key Entry (TKE) 9.0 Licensed Internal Code (LIC)

The following functions are planned to be supported in the TKE 9.0 level of LIC:

  • Crypto Express6S Coprocessor support: TKE 9.0 is required for managing Crypto Express6S cryptographic coprocessors and manages them through the same Crypto Module notebook functions as previous generations of Cryptographic modules.
  • Key material copy to alternate zone: TKE 9.0 allows you to copy key material from smart cards in one TKE zone to smart cards in another zone. You might have old 1024 bit strength TKE zones, and may wish to move or copy the key material in those zones into a new, stronger TKE zone. To use this new feature you create new TKE and/or EP11 smart cards on your TKE 9.0 system. You enroll the new TKE and/or EP11 smart cards in an alternate zone. This allows you to copy smart card content from a smart card enrolled in the alternate zone.
  • Save TKE data directory structure with files to USB: TKE data can be saved to, or restored from, removable media in the same directory structure they were found on the TKE.
  • Create key parts without opening a host: The TKE application now has the ability for administrators to create key parts without opening a host. This allows the key administrator to create key parts while being offline or before any hosts are defined. This feature can be found in the TKE application under the Utilities > Create CCA key parts pull-down menu.
  • TKE Audit Log application: There is a TKE Audit Log application available for the Privileged Mode Access ID of AUDITOR. This application provides an easy-to-use interface to view the TKE workstation security audit records from the TKE workstation.
  • Heartbeat audit record: TKE workstations cut an audit record when the TKE boots or when no audit events have occurred during a client-configured duration of time. The record shows the serial number of the TKE local crypto adapter and indicates if the local crypto adapter has been changed since the last check.
  • Performance improvements for domain groups: With CCA 5.3 and later firmware levels, and TKE 9.0, performance may be improved for operations performed with large domain groups. For example, consider a domain group of 85 domains and a Clear New Master Key Register operation is performed from the TKE. The number of TKE commands issued to the Crypto Express coprocessor from the TKE will be reduced from 85 to 1, thereby reducing the time to complete the operation.
  • Master key part entry on EP11: Known master key parts can now be entered and saved on smart cards for coprocessors configured in EP11 mode using TKE 9.0. This enables key custodians to manage EP11 master key parts in a fashion that is consistent with coprocessors configured in CCA mode.
  • Smart card readers: With TKE 9.0, if you have HID/OMNIKEY smart card readers you may continue to use them. See the TKE User's Guide for more detailed smart card reader information.
  • Certificate manager for domains: Every domain will now have the ability to manage a set of parent X.509 certificates for validating operating X.509 certificates used by applications running in the domain. The Crypto Express6S with CCA 6.0 is designed to meet the PCI-HSM PIN Transaction Security v3.0, 2016 standard.

The following features are related to support for the Crypto Express6S with CCA 6.0.

  • Domain mode management: With CCA 6.0, individual domains are in one of the following modes:
    • Normal mode
    • Imprint mode
    • Compliant mode

    Imprint and compliant modes were added to help customers migrate to a PCI-HSM compliant mode and meet PCI-HSM PIN Transaction Security v3.0, 2016 requirements. TKE is required to manage Host Crypto Module domains in imprint and compliant mode.

  • Set clock: With TKE 9.0, you now have the ability to set the host crypto module's clock. The clock must be set before a domain can be placed in imprint mode.
  • Domain-specific Host Crypto Module Audit Log management: Domains in imprint mode or compliant mode on a Crypto Express6S maintain a domain-specific module audit log. The TKE provides a feature for downloading the audit records so they can be viewed.
  • Domain-specific roles and authorities: Domains in imprint mode or compliant mode on a Crypto Express6S must be managed using domain-specific roles and authorities. The TKE provides new management features for the domain-specific roles and authorities. The roles are subject to forced dual control policies which prevent roles from being able to both issue and cosign a command. Refer to the TKE User's Guide for detailed information on how to manage imprint and compliant mode domains.
  • Setup PCI Environment Wizard: To help simplify the management of a PCI compliant domain, the TKE now provides a setup wizard that will create a minimum set of required dual control roles and authorities needed to manage a PCI compliant domain. Refer to the TKE User's Guide for detailed information on how to manage imprint and compliant mode domains.

FICON Express16S

With the introduction of FICON Express16S+ on the IBM Emperor II, you now have additional growth opportunities for your storage area network (SAN).

FICON Express16S+ supports a link data rate of 16 gigabits per second (Gbps) and autonegotiation to 4 or 8 Gbps for synergy with existing switches, directors, and storage devices. With support for native FICON, High Performance FICON for z Systems (zHPF), and Fibre Channel Protocol (FCP), the Emperor II server enables you to position your SAN for even higher performance -- helping you to prepare for an end-to-end 16 Gbps infrastructure to meet the lower latency and increased bandwidth demands of your applications.

The FICON Express16S+ adapter will work with your existing fiber optic cabling environment, both single-mode and multimode optical cables. The FICON Express16S+ feature running at end-to-end 16 Gbps link speeds will provide reduced latency for large read/write operations and increased bandwidth compared to the FICON Express8S feature.

Increased throughput for the FCP protocol: A FICON Express16S+ feature, when defined as CHPID type FCP, conforms to the Fibre Channel Protocol (FCP) standard to support attachment of SCSI devices, to complement the classical storage attachment supported by FICON and zHPF channels. In laboratory measurements, using FICON Express16S+ in an IBM Emperor II with the FCP protocol for small data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum of 380,000 IOs/sec, compared to the maximum of 110,000 IOs/sec achieved with FICON Express16S operating at 16 Gbps. In laboratory measurements, using FICON Express16S+ in an IBM Emperor II with the FCP protocol and FICON Express16S+ operating at 16 Gbps, FICON Express16S+ achieved a maximum throughput of 3200 MB/sec (reads + writes). This represents approximately a 25% increase in throughput. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.

On IBM Emperor II the FCP protocol is supported by z/VM, KVM for IBM Z Systems, and Linux on z Systems. Refer to the Software requirements section.

Increased throughput for the zHPF protocol: In laboratory measurements using FICON Express16S+ in an IBM Emperor II with the zHPF protocol and small data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum of 300,000 IOs/sec. In laboratory measurements, using FICON Express16S+ in an IBM Emperor II with the zHPF protocol and a mix of large sequential read and write data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum throughput of 3200 MB/sec (reads + writes) compared to a maximum of 2560 MB/sec (reads + writes) achieved with FICON Express16S operating at 16 Gbps. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.

Cleaning discipline for FICON Express16S+ fiber optic cabling: With the introduction of 16 Gbps link data rates, it is even more critical to ensure your fiber optic cabling infrastructure performs as expected. Proper fiber optic cleaning and maintenance is required to help ensure that the "data gets through." With 16 Gbps link data rates over multimode fiber optic cabling, link loss budgets and distances are reduced. Single-mode fiber optic cabling is more "reflection sensitive." With high link data rates and single-mode fiber optic cabling there is also less margin for error. The cabling is no longer scratch-tolerant and contaminants such as dust and oil can present a problem. To keep the data flowing, proper handling of fiber trunks and jumper cables is critical as well as thorough cleaning of fiber optic connectors. Work with your data center personnel or IBM personnel to ensure you have fiber optic cleaning procedures in place.

Channel subsystem (CSS) scalability: The Emperor II server, like the original LinuxONE Emperor server, has support for six logical channel subsystems (LCSSs) which are required to support the 85 LPARs for Emperor II, and four subchannel sets.

OSA-Express6S - an Ethernet technology refresh

A new generation of Ethernet features is being introduced for use in the PCIe I/O drawer and continues to be supported by the 16 GBps PCIe Gen3 host bus. This is an introduction of the full family of features - 1000BASE-T Ethernet for copper environments, in addition to 10 Gigabit Ethernet (10 GbE) and Gigabit Ethernet (GbE) for single-mode and multimode fiber optic environments. The performance characteristics are comparable to the OSA-Express5S features. They also retain the same form factor and port granularity - two ports per feature for the 1000BASE-T Ethernet and Gigabit Ethernet features, and one port per feature for the 10 Gigabit Ethernet features.

The OSA-Express6S family of features (#0422, #0423, #0424, #0425, #0426) is exclusive to the z14 and IBM Emperor II. On IBM Emperor II they are supported by z/VM, Linux on z Systems, and KVM for IBM Z Systems hypervisor. Refer to the Software requirements section.

Dynamic Partition Manager (DPM)

Dynamic Partition Manager (DPM) provides simplified hardware and virtual infrastructure management, including partition lifecycle and integrated dynamic I/O management for Linux running in an LPAR, under KVM for IBM Z Systems, and under z/VM V6.4. z/VM Single System Image (SSI) clusters are not currently supported within the existing DPM environment.

Using DPM, an environment can be created, provisioned, and modified without disrupting running workloads, and monitored for troubleshooting. Currently, DPM supports FCP storage. Enhancements to DPM simplify the installation of the Linux operating system, and support additional hardware adapters. These enhancements include:

  • Support for autoconfiguration of devices to simplify Linux operating system installation, where Linux distribution installers exploit function
  • Secure FTP through HMC for booting and installing an operating system via FTP
  • Support for OSA-Express6S, FICON Express 16S+, Crypto Express6S, and RoCE Express2 adapters

A CPC can be configured in either the Dynamic Partition Manager mode or PR/SM mode. The mode is enabled prior to the CPC power-on reset (POR).

Dynamic Partition Manager mode requires two OSA-Express6S 1000BASE-T Ethernet features (#0426) for primary and backup connectivity, along with associated cabling (HW for DPM, #0016).

The IBM Secure Service Container

The IBM Secure Service Container is a framework for securely deploying software appliances on IBM LinuxONE. Following are the offerings that exploit the Secure Service Container on LinuxONE:

  • IBM Blockchain Platform
  • IBM Operations Analytics for z Systems - zAware

The Secure Service Container consists of both a firmware framework and a software framework.

The following is an enhancement to the IBM Emperor II IBM Secure Service Container firmware framework:

  • Simplification - Dynamic Partition Manager support for dynamic resource management and creation of Secure Service Container LPARs without needing to re-IML.

The following are enhancements that have recently been made to the IBM Secure Service Container software framework:

  • Security
    • Help enable secure boot of appliance via system unique key smart card access such that the Secure Service Container or system administrator cannot utilize privileged credentials to see or access the key.
    • Runtime and tamper protection via BTRFS Filesystems for root and data volumes.
  • Appliance management
    • Support the addition of FCP (and ECKD) storage to different disk pools via the appliance UI.
    • Support network configurations managed by IPv4, IPv6, and VLAN configurations from the appliance UI.
    • Enable appliance updates including import from a prior, saved and exported configuration -- avoid losing configuration data (going back to a "Factory Install"--like state); particularly useful for Blockchain, which typically utilizes many concurrently running instances.
    • Support different users and groups via Local LDAP server and UI management.
    • Support starting appliance installer from a running appliance without having to interface with the HMC.
  • Usability
    • Avoid appliance spoofs by ensuring that a trusted and uniquely signed instance of an appliance is booted only in one LPAR, not multiple LPARs.

z/Architecture mode: Beginning with IBM z14, all IBM Z and IBM LinuxONE systems will only support operating systems running in z/Architecture mode. This applies to operating systems running native on PR/SM as well as operating systems running as second-level guests. IBM operating systems that run in ESA/390 mode are either no longer in service or only currently available with extended service contracts, and they are not usable on systems beginning with IBM z14. However, IBM z14 and IBM LinuxONE do provide ESA/390-compatibility mode, an environment supporting a subset of DAT-off ESA/390 applications in a hybrid architectural mode.

All 24-bit and 31-bit problem state application programs originally written to run on the ESA/390 architecture will be unaffected by this change.

z/VM support for the IBM Emperor II

With the available PTF for APAR VM65942, z/VM V6.3 and V6.4 provide support that will enable guests to exploit function supported by z/VM on IBM Emperor II, which includes:

  • z/Architecture support: The z/VM Stand-Alone Program Loader (SAPL) utility, DASD Dump Restore (DDR), and the Stand-Alone Dump utility have been enhanced to run entirely in z/Architecture mode. z/Architecture support for these utilities is in the base of z/VM V6.4 and provided for z/VM V6.3 with the available PTF for APAR VM65856. z/Architecture support for the Stand-Alone Dump utility is in the base of z/VM V6.4 and provided for z/VM V6.3 with the available PTFs for APARs VM65921 and VM65922.
  • Hardware facilities: z/VM will enable guest use of new instructions and capabilities available on IBM Emperor II.
  • ESA/390-compatibility mode for guests: IBM Emperor II does not support the full ESA/390 architectural mode. However, IBM Emperor II does provide ESA/390-compatibility mode, an environment supporting a subset of DAT-off ESA/390 applications in a hybrid architectural mode. z/VM will provide the support necessary for DAT-off guests to run in this new compatibility mode, which allows guests such as CMS, GCS, and those that start in ESA/390 mode briefly before switching to z/Architecture mode to continue to run on IBM Emperor II.

    The available PTF for APAR VM65976 provides infrastructure support for ESA/390 compatibility mode within z/VM V6.2, V6.3, and V6.4, and must be installed on all members of an SSI cluster before any z/VM V6.3 or V6.4 member of the cluster is run on an IBM Emperor II server.

  • Support for Crypto Express6S: z/VM support for the new Crypto Express6S (CEX6S) adapter is included for both shared and dedicated guest use. As with the prior crypto adapter support, the CEX6S adapter can be configured as an accelerator or as an IBM Common Cryptographic Architecture (CCA) coprocessor for shared or dedicated use by z/Architecture guests. When the CEX6S adapter is configured as an IBM Enterprise Public-Key Cryptography Standards (PKCS) #11 (EP11) coprocessor, the domains on the adapter can be dedicated to z/Architecture guests, but not shared. With Crypto Express6S support and support for the new and enhanced CPACF functions, z/VM V6.3 and V6.4 provide the prerequisite IBM Emperor II encryption support to enable exploitation by guests in support of pervasive encryption of data in flight and at rest.
  • Crypto Clear Key ECC operations: Clear Key Elliptic Curve Cryptographic (ECC) operations are supported for guests enrolled in the z/VM-managed shared-crypto queue (APVIRT). The shared-crypto queue must be configured with CCA coprocessor domains in order for the function to be virtualized for guest use.
  • Dynamic I/O support: Dynamic I/O support is provided for managing the configuration of OSA-Express6S OSD CHPIDs, FICON Express16S+ FC and FCP CHPIDs, and RoCE Express2 functions. z/VM supports the definition and dynamic activation of I/O configurations for Emperor II using HCD.
  • RoCE Express2 support: Guest exploitation support for RoCE Express2 allows the adapters to be brought online and attached to supporting guests for exploitation.
  • Improved memory management support: The IBM Emperor II processor design allows greater concurrency in address translation. This improvement may increase z/VM workloads' performance compared to the original Emperor, particularly when z/VM is configured to exploit multithreading.

Installing z/VM on the IBM Emperor II:

z/VM V6.4 can be installed directly on an Emperor II server with an image obtained from IBM after August 25, 2017. The PTF for APAR VM65942 must be applied immediately after installing z/VM V6.4.

Current LinuxONE or IBM Z clients using z/VM V6.3, who are interested in running z/VM V6.3 on Emperor II, should first consider moving to z/VM V6.4. If moving to z/VM V6.4 is not a viable option, z/VM V6.3 must be installed on a prior IBM Z server and the PTFs for APARs VM65942, VM65921, and VM65922 must be applied prior to moving the image to Emperor II. After applying all required service and before IPLing z/VM V6.3 on an Emperor II server, an updated SAPL must be installed by using the updated SALIPL MODULE provided by the PTF for APAR VM65856. Otherwise, z/VM V6.3 will not successfully IPL on an Emperor II server. In addition, after applying the PTFs for APARs VM65921 and VM65922, the stand-alone dump program must be re-installed using the updated SDINST utility.

Guest exploitation support for the Instruction Execution Protection Facility:

With the PTF for APAR VM65986, planned to be available December 15, 2017, z/VM V6.4 will provide support for guest exploitation of the IBM Emperor II Instruction Execution Protection Facility. This facility provides functionality to help improve the security of programs running on IBM LinuxONE by allowing virtual memory elements to be identified as containing only data. If an attempt is made to fetch an instruction from an address in such an element or if an address in such an element is the target of an execute-type instruction, a Protection Exception will occur.

Guest exploitation support for pause-less garbage collection:

With the PTF for APAR VM65987, planned to be available December 15, 2017, z/VM V6.4 will provide support for guest exploitation of the Emperor II Guarded Storage Facility. This facility is designed to improve the performance of garbage-collection processing by various languages, in particular Java.

Encrypted paging support:

With the PTF for APAR VM65993, planned to be available December 15, 2017, z/VM V6.4 will provide support for encrypted paging, in support of the Emperor II pervasive encryption philosophy of encrypting data in flight and at rest. Ciphering will occur as data moves between active memory and a paging volume owned by z/VM. Included in the support is the ability to dynamically control whether a running z/VM system is encrypting this data.

Processor scalability efficiency improvements:

With the PTF for APAR VM65988, the z/VM hypervisor will be enhanced to manage its spinlocks more efficiently and thereby reduce system overhead. This enhancement will contribute to improved performance and throughput, and thereby help to improve overall system capacity by allowing additional work to be performed. While most workload configurations will benefit to some extent, the improvements are greatest for workloads using large numbers of logical CPUs. The shared-exclusive spinlock manager was replaced with a more cache-efficient design providing greater scalability for the Scheduler Lock (SRMSLOCK). SRMSLOCK reporting in Monitor D0R23 MRSYTLCK was corrected to include time spinning in HCPDSP's internal spin loop that was previously unreported. The support is available on all hardware supported by z/VM V6.4, including the LinuxONE Emperor II and IBM z14. However, the design for some spinlocks takes advantage of efficiencies unique to the LinuxONE Emperor II and z14.

Sub-capacity pricing terms for z/VM and select z/VM-based programs:

Sub-capacity pricing for the z/VM V6 operating environment is available to clients running z/VM Version 6 Release 3 or higher. Software pricing at less than full machine capacity can provide more flexibility and improved cost of computing as a client manages the volatility and growth of new workloads.

z/VM continuous delivery philosophy:

IBM has adopted a new practice for z/VM, known as the continuous delivery (CD) support model, for delivering new function via PTFs to help enterprises receive function more quickly. IBM will deliver new function via PTFs, while continuing to recognize that base stability is a critical attribute. Clients will continue to receive the same world-class support and assistance from IBM to which they are accustomed as part of the standard Software Subscription and Support (S&S) offering. The z/VM service page provides details on new z/VM functions that have been or will be provided using this continuous delivery model and allows subscribing in order to be alerted when new functions have been made available.

Additional z/VM V6.4 enhancements during 2017:

The following enhancements for z/VM V6.4 are planned during 2017:

  • Concurrent I/O support for the IBM XIV Storage System: With the available PTF for APAR VM65929, the z/VM SCSI container enables multiple I/O requests to be issued concurrently to EDEVICEs backed by IBM XIV Storage System hardware, which may improve performance. This support particularly benefits EDEVICE paging I/O or volumes containing multiple minidisks.
  • Distributed IUCV enhancements: With the available PTF for APAR VM65872, the rules for Distributed IUCV CONNECT in a single system image (SSI) environment are revised. This support allows IUCV CONNECT to work in cases that were originally restricted, primarily because they involved a Multiconfiguration Virtual Machine (IDENTITY) user.

    This support also makes it easier for an administrator to change the Distributed IUCV policy for an SSI cluster. Previously, the Distributed IUCV policy within an active SSI cluster could be changed only by shutting down all members at the same time. As this new support is applied to each system, it will be possible for that member to join the cluster regardless of its Distributed IUCV configuration.

  • NICDEF security control enhancements: With the available PTFs for APARs VM65925, VM65926, and VM65931, the NICDEF directory statement is enhanced to provide a set of new operands referred to as Directory Network Authorization (DNA). With DNA, a system administrator can configure and consolidate a virtual NIC device and its network properties in a centralized location - z/VM's User Directory. Operational differences between PORTBASED and USERBASED VSwitches have been eliminated with this support. A system administrator has the option to manage a VSwitch by user, by port number, or using a combination of the two methods. While the management of USERBASED and PORTBASED VSwitches is simplified, Live Guest Relocation of a guest connected to a VSwitch still requires the destination system to have a VSwitch with a PORTBASED or USERBASED designation matching that of the source system.
  • RACF security policy enhancements: With the available PTFs for APARs VM65930 and VM65982, the z/VM RACF Security Server feature supports the following security policy enhancements:
    • Read-Only Auditor (ROAUDIT): This new user role allows many of the common auditing tasks to be performed without the ability to modify settings or manipulate audit logs.
    • XAUTOLOG..ON control: This enhancement introduces new security policy requirements for the ON operand of the CP XAUTOLOG command. This changes default behavior of this operand when an ESM is installed on your system.
    • List the current VMXEVENT profile: This enhancement updates the SETEVENT LIST command to provide an authorized user with the names of the VMXEVENT profiles activated and in use by RACF.

      Note: The PTF for APAR VM65923 provides infrastructure support in z/VM V6.2, V6.3, and V6.4 and must be installed on all the members of an SSI cluster before any V6.4 member is running with the PTF for APAR VM65930.

  • Crypto Express APVIRT support for the z/VM TLS/SSL server and LDAP/VM: With the available PTF for APAR PI72106, the z/VM System SSL cryptographic library is updated to offload cryptographic operations to Crypto Express hardware associated with your IBM LinuxONE hardware, which may improve performance. This support is intended for clear-key RSA operations. To enable this support, add the CRYPTO APVIRTUAL statement to the pertinent service virtual machine entries in the z/VM User Directory.
  • EAV minidisk support: With the PTFs for APARs VM65943, VM65945, and PI85943, enhanced EAV support for 3390-A DASD devices supporting 28-bit cylinder addresses is provided. This support will allow non-fullpack minidisks to reside anywhere on the volume, including beyond the current restriction of the 64K cylinder boundary (0-65519), and up to the one terabyte limit currently supported.
  • Dump processing enhancements: With the available PTF for APAR VM65989, the amount of time it takes for z/VM to write a hard abend or snap dump to 3390 DASD may be reduced. The improvements were achieved via changes to the I/O channel program used to write central memory to z/VM spool space located on 3390 DASD. This APAR also provides support for reducing dump size by excluding PGMBKs from snap dumps.
  • Alternate Subchannel Set Dynamic I/O support: With the available PTF for APAR VM65942, z/VM V6.4 provides dynamic I/O commands within the z/VM hypervisor for supporting define, modify, and delete of a device within either the default or alternate subchannel sets. HCD support is currently not available.

STP - Time synchronization

Server Time Protocol (STP) is designed to allow events occurring in different servers to be properly sequenced in time. STP is for servers which need time synchronization. STP is a server-wide facility that is implemented in the Licensed Internal Code (LIC), presenting a single view of time to Processor Resource/Systems Manager (PR/SM). The STP design introduced a concept called Coordinated Timing Network (CTN), a collection of servers that are time-synchronized to a time value called Coordinated Server Time.

STP enhancements: IBM z14 introduced an additional stratum level 4 for Server Time Protocol (STP) synchronization which is also available on IBM Emperor II. With the additional stratum level, STP can synchronize systems up to 3 steps away from the Current Time Server (CTS). Prior systems allowed synchronization only up to level 3, or up to 2 steps from the CTS. This additional stratum level is not intended for long-term use; rather, it is specifically intended for short-term use during configuration changes for large timing networks, to avoid some of the cost and complexity caused by being constrained to a 3-stratum timing configuration. IBM z14 also introduced a new Graphical User Display for the STP network and configuration, which is also available on IBM Emperor II. The new user interface has been revamped for a quick, intuitive view of the various pieces of the STP relationship network map, including the status of the components of the timing network. The new support allows the new level of HMC to manage older systems using the same new interface.

Hardware Management Console (HMC)

HMC/SE user interface: The Emperor II Hardware Management Console and Support Element will support only the Tree Style user interface. The Classic Style user interface is no longer supported.

The following enhancements have been made to the Tree Style user interface to aid with new users of Tree Style as well as address pain points of existing users.

  • A Masthead with Favorites and Search controls will help users quickly find and launch tasks.
  • Tasks will now open in tabs within the user interface (instead of separate browser windows) to make finding and managing running tasks easier.
  • There is also the ability to have the task tab 'pop-out' into a separate window, giving users the ability to have a similar parallel task display window as on previous Tree Style controls and allowing the task displays to be viewed on other physical displays.

Manage System Time: The Manage System Time task replaces the System Time task on HMC. The new Manage System Time task provides a simplified workflow for system time management including:

  • Improved help tools to complement and improve system administrator skills:
    • Inline definition of technical terms.
  • Improved user experience with visual representation of configuration panels:
    • Guidance provided within the workflows.
    • Topology displays of system time networks.
    • Errors surfaced in visualization for easier problem resolution of setup errors.
  • Single point of system time management for multiple systems.

IBM Hardware Management Console (HMC) 2.14.0 security enhancements: Security features in the Hardware Management Console (HMC) 2.14.0 available with IBM Emperor II include Multifactor Authentication, Firmware Integrity Monitoring in support of NIST Standard 800-147B, Crypto Compliance Levels, FTP through HMC, Secure Console to Console Communication Enhancements, Remote Browser IP Address Limiting, and more.

  • Multifactor Authentication : The Hardware Management Console will now offer an optional control of Multifactor Authentication in addition to the userid/password controls provided today. If the Multifactor option is selected for a given user, that user will now be required to enter a second authentication factor using a TOTP (Time-based One-Time Password) defined by RFC 6238. RFC 6238 is implemented by freely available smartphone and web apps utilizing a secret key provided per HMC user.
  • HMC Mobile for Z and LinuxONE: New iOS and Android mobile apps are planned to be available for the HMC 2.14.0 supporting Emperor II, z14, z13, LinuxONE Emperor, and LinuxONE Rockhopper systems. HMC Mobile will help enable HMC users to securely monitor and manage systems from anywhere. The apps provide system and partition views, status monitoring, hardware messages, operating system messages, and the ability to receive push notifications from the HMC using the existing zRSF (IBM Z Remote Support Facility) connection. HMC Mobile is disabled by default and, once enabled, provides a robust set of security controls. Administrators can restrict usage to specific HMC users and IP addresses, require the use of app passwords, enable Multifactor Authentication, restrict the app to read-only access, and more.
  • Firmware integrity monitoring : Emperor II will also offer an enhancement on the Support Element that provides notification if tampering with booting of firmware on the server (CPC) is detected. This enhancement is designed to meet the BIOS Protection Guidelines recommended and published by the National Institute of Standards and Technology (NIST) in Special Publication 800-147B. If tampering is detected, the Support Element will issue a customer alert via a warning or a lock of the Support Element, depending on the configuration. If "call home" support is enabled on an Emperor II Hardware Management Console managing the Support Element, additional analysis of the Support Element will be performed and displayed by IBM Resource Link.

    In addition to this support, the Hardware Management Console also has been enhanced to provide attempted tamper monitoring and reporting. A newly manufactured Hardware Management Console directly ordered with Emperor II, or at a later time, is required for this protection. Any detected events of attempted tampering will be logged and will issue a customer alert via a warning or a lock of the Hardware Management Console, depending on setup configuration. In addition, if "call home" support is enabled on the Hardware Management Console, supplementary analysis of events logged by the Hardware Management Console will be available on IBM Resource Link.

    Although customers can carry forward their Hardware Management Consoles on Emperor II, these tamper protection capabilities will be delivered only on newly manufactured Hardware Management Consoles. The Emperor II environment can contain both Hardware Management Consoles that have been carried forward and newly manufactured Hardware Management Consoles.

IBM Enhanced Remote Support Facility: The IBM Enhanced Remote Support Facility was first introduced on zEC12/zBC12 systems and for those systems, z13/z13s, and LinuxONE Emperor/LinuxONE Rockhopper, both the Enhanced and Legacy Remote Support Facility support could be utilized. The Enhanced support provided improved problem data uploads and fix data downloads. z14 and Emperor II processors will no longer connect to the legacy IBM Support Facility.

  • z14 and Emperor II HMCs supporting older z10EC/z10BC - z13 systems will still require connections to the legacy IBM Support Facility.
  • z14 and Emperor II HMCs supporting only z14 or Emperor II systems only require IBM Enhanced Support Facility connections.
  • A connection to the IBM Enhanced Support Facility is required to support z14 and Emperor II HMCs regardless of the CPC they are supporting.

If you had not previously configured firewalls and proxy support with the ability to connect to the Enhanced Support Facility, this will be required for Emperor II and z14 HMC and CPC connections per above rules.

Global OSA/SF: The HMC Global OSA/SF will now provide a global view of all OSA PCHIDs and the monitoring and diagnostic information previously available in the Query Host command.

New characters supported for Load parms: Starting with z14 and Emperor II the Load parameter for Load task, Activation Load, and Image Profiles will now allow three new characters: @#$. z13/z13s or older systems support a character set of A-Z, 0-9, "." (period), and " " (blanks). Emperor II systems will support a character set of A-Z, 0-9, "." (period), " " (blanks), "@", "#", and "$".

FTP through HMC: To maximize security features, IBM recommends that customers keep their IBM LinuxONE server on a dedicated network with one HMC network used for that network and the second HMC network used for outward communication (IBM Support Facility, remote browsing, automation). However, for systems prior to z14, this created a security challenge for FTP operations originating from the SE. Customers have to either put their FTP server on the IBM LinuxONE dedicated network or put their IBM LinuxONE on their intranet network.

Starting with z14 and Emperor II, all FTP operations originating from the SE will be proxied through a managing HMC. This now allows the FTP SE originated operations to follow IBM security recommendations. In addition, all HMC/SE tasks that support FTP will provide three options of FTP: FTP, FTPS, and SFTP.

  • FTPS is SSL based and uses certificates to authenticate servers.
  • SFTP is SSH based and uses SSH keys to authenticate servers.
  • Username and passwords are required for client authentication in all three protocols.

Console to console communications: HMC consoles have used anonymous cipher suites for some inter-console communication purposes. These cipher suites, while providing encryption and integrity validation, do not provide cryptographic authentication. Network security scanners can detect this, and anonymous cipher suites may not be acceptable to some customers' security policies. Starting with z14 and Emperor II HMC/SE, the console to console communications solution, when security is enabled, will no longer use anonymous cipher suites and will begin using an industry standard based password driven cryptography system. This system provides cryptographic encryption, integrity validation, and authentication.

Removal of Common Infrastructure Module (CIM) Management Interface: The HMC 2.14.0 will no longer support the Hardware Console Common Infrastructure Module (CIM) Management Interface. The Hardware Management Console Simple Network Management Protocol (SNMP), and Web Services Application Programming Interfaces (APIs) will continue to be supported.

Accessibility by people with disabilities

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

Section 508 of the US Rehabilitation Act

IBM Emperor II servers are capable on delivery, when used in accordance with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act of 1973, 29 U.S.C. Section 794d, as implemented by 36 C.F.R. Part 1194, provided that any Assistive Technology used with the Product properly interoperates with it.

IBM makes no representation about the Section 508 status of these third party products included in this offering. Contact the vendor for specific, current information on the Section 508 status of these products.
Back to topBack to top
 

Product positioning

Commonly referred to as the oil of our era, data has become the new global currency. IT today is experiencing a time of exponential growth in the sheer volumes of data, fueled by the digital transformation of systems, services, and interconnected devices that all require strong data serving capabilities. Businesses must be able to manage, store, and protect this information, and, most important, use it for competitive advantage. This is creating the demand to apply intelligence and insight to the data to build new services wrapped for a customized user experience. From a user perspective, IT must create an environment where users have confidence that data is protected yet available from anywhere and any device. This ability to be fast and flexible in delivery of new services, with insight and security, will differentiate a business. The IBM Emperor II delivers unique capabilities to help with that differentiation.

At the core of every enterprise lies core business data, assets which if lost or compromised could cause irreparable damage. Core business data is often governed by regulatory requirements designed to protect data and safeguard privacy, with high penalties in the event of loss or inadvertent disclosure. Internal and external pressures to protect customer data have changed the perspective around how core business data should be handled and protected. Establishing a "perimeter" around core data using encryption is one of the most impactful ways to protect data and prevent against loss. The objective is to create a fortified perimeter around core business data, wherever it may physically reside. The Emperor II platform provides pervasive encryption capabilities designed to enable you to protect data efficiently, and without requiring application changes, making it the world's premier system for enabling encryption of data as the new perimeter across the value chain.

The security capabilities of Emperor II are unmatched in the industry. The Emperor II platform provides the hardware infrastructure, in a balanced system design, with the encryption capabilities that now make it possible to create a fortified perimeter around critical business data. Security is built into the Emperor II hardware, enabling lightning fast hardware encryption of all data whether it is in use, in flight, or at rest. This is achieved without having to make changes to applications. IBM's unique Secure Service Container technology helps protect client data from both external and internal threats and is designed to offer the highest security level available for protected key management (FIPS 140-2 level 4). Ultimate workload isolation and encryption though the IBM Secure Service Container provides a virtual lock box for each workload. The use of protected keys helps to secure data without giving up performance and industry-leading secure Java performance via SSL is 2 to 3 times faster than x86 alternatives. Instead of only protecting a selective 4% of data as is common with x86 clouds, Emperor II protects 100% through pervasive encryption, all with zero application changes, and minimal operational overhead, which help improve efforts to meet various regulatory requirements. Pervasive encryption allows application development to focus on innovation rather than application-level encryption.This leading innovation in security and other technologies is a reason why the 10 largest global insurers, 70 percent of the world's largest retailers, 23 of the 25 largest airlines, and 92 of the top 100 banks worldwide have placed their trust in IBM.

The Emperor II provides the infrastructure to meet the demands of a digital business. With up to 170 configurable cores, Emperor II has performance and scaling advantages over prior generations, and more capacity than the original Emperor 141-way. With capacity to do the work of hundreds or in many cases thousands of x86 servers in a single footprint, Emperor II has a 3-year running cost below x86 (3). Massive memory and I/O bandwidth has been built into the system to support fast in-memory workloads and real-time analytics that bring more insights and new business value.

Emperor II provides unrivaled performance and vertical scale to support larger workloads with less latency and less admin complexity. Vertical scale allows Emperor II to scale up to 2 million Docker containers in a single system(1). As a system engineered for data-serving workloads, Emperor II can move data faster than alternative platforms(2). It has a 2.1x higher throughput, can serve up to 30 billion web data requests a day, and has the ability to host 20x larger databases without the added cost and latency of fragmenting data across server farms(2). There are 640 additional processors that are not part of the general processor count. These additional processors are solely dedicated to I/O processing to help increase I/O speeds and to help assure data integrity, all with zero additional licensing costs. On x86 this work is done with standard processors that drive incremental hardware, software, and administrative costs. Emperor II is the only Linux system that offers this built-in fast I/O subsystem capable of over 190K 8K read IOPs per FCP link.

With up to 32 TB of real memory, Emperor II can open opportunities such as in-memory data marts, large buffer pools for data access, and in-memory analytics while giving you the necessary room to tune applications for optimal performance. More data in memory means more efficient, cost-effective vertical scaling while maintaining a real-time single source of the truth. Advancements such as SIMD accelerate analytic workloads and decimal compute, which are vital to financial applications. Java improvements such as pause-less garbage collection enable vertical scaling while maintaining predictable results. The use of crypto acceleration will deliver additional improvements in throughput per core, which gives a natural boost to Java processes.

As a shared, immutable ledger for recording the history of transactions, Blockchain is a revolutionary technology that is transforming business around the globe. It allows all members of a supply chain to share a digital ledger that is updated every time a transaction occurs. Members can view ledger progress in a common, transparent, and accessible record. Cryptographic privacy ensures that members only see the parts of the ledger relevant to them, and that transactions are secure, authenticated, and verifiable. Businesses and customers around the globe need to interface with each other to exchange assets such as currency, services, and information. Experts believe that Blockchain will do for transactions what the internet did for information. As a highly engineered platform designed for secure, data-serving workloads, IBM chose Emperor II to run the IBM Blockchain Platform. Blockchain is expected to radically improve the operational effectiveness of businesses around the globe by enabling more data points, quicker responses, increased trust, and tamper-proof records. Emperor II is the cornerstone of the IBM Blockchain offering.

IBM has been committed to Linux for decades and continues to invest in the Linux ecosystem. Emperor II provides a unique platform for any Linux solution requiring high availability, security features, or scalability and supports a wealth of new open source products such as Go, Python, Scala, Node.js, Docker, Spark, MongoDB, PostgreSQL, and MariaDB. Emperor II adds to IBM's commitment by allowing clients to take advantage of transformative technologies like Blockchain, gain cognitive insights through the use of Spark analytics, scale vertically with unmatched speed, provide highly secure data-serving capabilities, and leverage the use of application programming interfaces (APIs) to help create and deliver innovative, new customer services.

Note: (1) Performance result is extrapolated from IBM internal tests running in a z14 LPAR with 10 dedicated IFLs and 16 GB memory 1000 BusyBox Docker containers with ApacheHTTP. Results may vary. Operating system was SLES 12 SP2 (SMT mode). Docker 1.12 was used.

Note: (2) Performance comparison based on IBM internal tests comparing IBM z13s with one comparably configured x86 environment and one comparably configured public cloud running general purpose virtual machines designed to replicate typical IBM customer workload usage in the marketplace. System configurations are based on equivalence ratios derived from IBM internal studies and are as follows: Public Cloud configuration: total of 24 general purpose instances; x86 configuration: total of two x86 systems each with 24 Intel E5-2690 v3 cores, 192 GB memory, and 2x400 GB SSDs; z13s configuration: total of 8 cores, 384 GB memory, and Storwize v7000 with 4x400 GB SSDs.

Note: (3) Price comparison estimates based on a 3-year Total Cost of Ownership (TCO) using publicly available US prices (current as of January 1, 2016). Public Cloud TCO estimate includes costs (US East Region) of infrastructure (instances, data out, storage, support, free tier/reserved tier discounts), middleware, and labor. z13s and x86 TCO estimates include costs of infrastructure (system, memory, storage, virtualization, OS), middleware, and labor. Results may vary based on actual workloads, system configurations, customer applications, queries, and other variables in a production environment and may produce different results. Users of this document should verify the applicable data for their specific environment.
Back to topBack to top
 

Models

Model summary matrix

Model summary matrix:

Model PU Memory (Note 1) PCIe Fanouts PCIe IO Drawer (Note 2)
LM1 1 to 33 256 to 8000 GB 2 to 10 0 to 3 (Note 3)
LM2 1 to 69 8512 to 16912 GB 2 to 20 0 to 5
LM3 1 to 105 16704 to 24384 GB 2 to 30 0 to 5
LM4 1 to 141 24896 to 32576 GB 2 to 40 0 to 5
LM5 1 to 170 24896 to 32576 GB 2 to 40 0 to 5

Notes:

  1. An additional 192 GB of memory is shipped and reserved for HSA. One additional memory channel is dedicated for RAIM. Every fifth DIMM configured is reserved for this purpose.

  2. Offerings are the same for both air cooled machines and water cooled machines.

  3. Three physical drawers, 2.5 accessible drawers

Processor Unit Summary

Listed below are the minimums and maximums of processor units (PUs) that may be purchased permanently. The feature codes affected are listed in parentheses.

Model Total PUs Available for Use CP4s (#1929) Min/Max IFLs (#1933) Min/Max uIFLs (#1937) Min/Max Optional SAPs (#1935) Min/Max
LM1 33 0 to 1 1 to 33 0 to 32 0 to 4
LM2 69 0 to 1 1 to 69 0 to 68 0 to 8
LM3 105 0 to 1 1 to 105 0 to 104 0 to 12
LM4 141 0 to 1 1 to 141 0 to 140 0 to 16
LM5 170 0 to 1 1 to 170 0 to 169 0 to 16

Notes:

  1. An Emperor II supports 1 sub-capacity general purpose processor (#1929): 401. Active capacity must always equal the purchased capacity.

  2. General purpose processors cannot be used with CBU CP features.

  3. CBU IFL and CBU SAP features are allowed.

  4. At least one Integrate Facility for Linux (IFL) (#1933) and at most one CP (#1929) is required for any LM1, LM2, LM3, LM4, or LM5 model.

  5. One CP or one IFL (#1933) must be installed with the installation of any uIFLs or prior to the installation of any uIFLs.

  6. The total number of PUs purchased cannot exceed the total number available for that model.

  7. There are two Spares per system.

  8. The number of SAPs provided to the customer as standard PUs are as follows:
    • Model LM1 = four SAPs
    • Model LM2 = eight SAPs
    • Model LM3 = twelve SAPs
    • Model LM4 = sixteen SAPs
    • Model LM5 = sixteen SAPs

Customer setup (CSU)

Customer setup is not available on this machine.

Devices supported

The hardware requirements for IBM Z Systems and their features and functions are identified. A new driver level is required. HMC (V2.14.0) plus MCLs and the Support Element (V2.14.0) are available on September 13, 2017 .

You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

Peripheral hardware and device attachments

IBM devices previously attached to IBM System z10, z196, zEC12, z13 and zSeries servers are supported for attachment to IBM Emperor II channels, unless otherwise noted. The subject I/O devices must meet the FICON and Fibre Channel Protocol (FCP) architectures to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.

While the Emperor II supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.

Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.

Information on switches and directors qualified for IBM z Systems FICON and FCP channels can be found in the Library section of Resource Link.

  • https://www.ibm.com/servers/resourcelink

Model conversions

From    From  To      To
------- ----- ------- ----- --- -----------
Machine Model Machine Model     Description
type          type
------- ----- ------- ----- --- -----------
3906    LM1   3906    LM2   (4) LM1 to LM2
3906    LM1   3906    LM3   (4) LM1 to LM3
3906    LM1   3906    LM4   (4) LM1 to LM4
3906    LM1   3906    M01   (4) LM1 to M01
3906    LM1   3906    M02   (4) LM1 to M02
3906    LM1   3906    M03   (4) LM1 to M03
3906    LM1   3906    M04   (4) LM1 to M04
3906    LM2   3906    LM3   (4) LM2 to LM3
3906    LM2   3906    LM4   (4) LM2 to LM4
3906    LM2   3906    M02   (4) LM2 to M02
3906    LM2   3906    M03   (4) LM2 to M03
3906    LM2   3906    M04   (4) LM2 to M04
3906    LM3   3906    LM4   (4) LM3 to LM4
3906    LM3   3906    M03   (4) LM3 to M03
3906    LM3   3906    M04   (4) LM3 to M04
3906    LM4   3906    M04   (4) LM4 to M04
3906    LM5   3906    M05   (4) LM5 to M05

Note: (4) Parts removed as a result of model conversions become the property of IBM.

Feature conversions

From    From To      To
------- ---- ------- ---- --- ------------
Machine FC   Machine FC       Description
type         type
------- ---- ------- ---- --- ------------
3906    1107 3906    1108 (5) LM1 air to
                              LM2 air
3906    1107 3906    1109 (5) LM1 air to
                              LM3 air
3906    1107 3906    1110 (5) LM1 air to
                              LM4 air
3906    1107 3906    1023 (5) LM1 air to
                              M01 air
3906    1107 3906    1024 (5) LM1 air to
                              M02 air
3906    1107 3906    1025 (5) LM1 air to
                              M03 air
3906    1107 3906    1026 (5) LM1 air to
                              M04 air
3906    1108 3906    1109 (5) LM2 air to
                              LM3 air
3906    1108 3906    1110 (5) LM2 air to
                              LM4 air
3906    1108 3906    1024 (5) LM2 air to
                              M02 air
3906    1108 3906    1025 (5) LM2 air to
                              M03 air
3906    1108 3906    1026 (5) LM2 air to
                              M04 air
3906    1109 3906    1110 (5) LM3 air to
                              LM4 air
3906    1109 3906    1025 (5) LM3 air to
                              M03 air
3906    1109 3906    1026 (5) LM3 air to
                              M04 air
3906    1110 3906    1026 (5) LM4 air to
                              M04 air
3906    1111 3906    1027 (5) LM5 air to
                              M05 air
3906    1112 3906    1113 (5) LM1 water to
                              LM2 water
3906    1112 3906    1114 (5) LM1 water to
                              LM3 water
3906    1112 3906    1115 (5) LM1 water to
                              LM4 water
3906    1112 3906    1028 (5) LM1 water to
                              M01 water
3906    1112 3906    1029 (5) LM1 water to
                              M02 water
3906    1112 3906    1030 (5) LM1 water to
                              M03 water
3906    1112 3906    1031 (5) LM1 water to
                              M04 water
3906    1113 3906    1114 (5) LM2 water to
                              LM3 water
3906    1113 3906    1115 (5) LM2 water to
                              LM4 water
3906    1113 3906    1029 (5) LM2 water to
                              M02 water
3906    1113 3906    1030 (5) LM2 water to
                              M03 water
3906    1113 3906    1031 (5) LM2 water to
                              M04 water
3906    1114 3906    1115 (5) LM3 water to
                              LM4 water
3906    1114 3906    1030 (5) LM3 water to
                              M03 water
3906    1114 3906    1031 (5) LM3 water to
                              M04 water
3906    1115 3906    1031 (5) LM4 water to
                              M04 water
3906    1116 3906    1032 (5) LM5 water to
                              M05 water
3906    1933 3906    1935 (5) IFL to SAP
                              (opt)
3906    1933 3906    1937 (5) IFL to uIFL
3906    1935 3906    1933 (5) SAP(opt) to
                              IFL
3906    1935 3906    1937 (5) SAP(opt) to
                              uIFL
3906    1937 3906    1933 (5) uIFL to IFL
3906    1937 3906    1935 (5) uIFL to SAP
                              (opt)
3906    1990 3906    1898 (5) 32GBPreplnd
                              Mem to
                              32GBCptyIncr
3906    1990 3906    1938 (5) 32GBPreplnd
                              Mem to
                              32GBCptyIncr
                              >1TB
3906    1991 3906    1893 (5) 64GBPreplnd
                              Mem to
                              64GBCptyIncr
3906    1991 3906    1939 (5) 64GBPreplnd
                              Mem to
                              64GBCptyIncr
                              >1TB

Note: (5) Parts removed as a result of feature conversions become the property of IBM.
Back to topBack to top
 

Technical description
TOC Link Physical specifications TOC Link Operating environment TOC Link Limitations
TOC Link Hardware requirements TOC Link Software requirements


Physical specifications

IBM Emperor II Air Cooled Machine

Dimensions (rounded to the nearest 0.1" or 0.1 cm):

Systems with all covers

                               Depth Width Height
------------------------------ ----- ----- ------
Inches                         73.5  63.6  79.3
Centimeter                     186.7 156.5 201.3
Inches (O/H IO cable exit)     73.5  72.7  84.8(6)
Centimeter (O/H IO cable exit) 186.7 184.7 215.3

Note: (6) The height with overhead I/O cable exit differs from the standard height only with the optional optical cable organizer feature installed.

Systems with all covers and height reduction

           Depth Width Height
---------- ----- ----- ------
Inches     73.5  61.6  70.3
Centimeter 186.7 156.5 178.5

Each frame with one side cover and without packaging

           Depth Width Height
---------- ----- ----- ------
Inches     50.0  30.7  79.3
Centimeter 127.0 78.0  201.3

Each frame on casters with one side cover and with packaging (domestic)

           Depth Width Height
---------- ----- ----- ------
Inches     57.4  32.4  79.8
Centimeter 145.8 82.2  202.6

Each frame with one side cover and with packaging (ARBO crate)

           Depth Width Height
---------- ----- ----- ------
Inches     63.4  36.5  87.6
Centimeter 161.0 92.7  222.5

Approximate weight:

System with IBF feature

                       Newbuild Newbuild
                       Minimum  Maximum
                       System   System
                       Model    Model
                       LM1 No   LM5 Max
                       I/O      # of I/O
                       drawer   drawers
---------------------- -------- --------
kg                     1512     2714
lb                     3333     5983
kg (O/H IO cable exit) 1566     2768
lb (O/H IO cable exit) 3453     6103

System without IBF feature

                       Newbuild Newbuild
                       Minimum  Maximum
                       System   System
                       Model    Model
                       LM1 No   LM5 Max
                       I/O      # of I/O
                       drawer   drawers
---------------------- -------- --------
kg                     1309     2410
lb                     2886     5312
kg (O/H IO cable exit) 1364     2464
lb (O/H IO cable exit) 3006     5432

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

The dc power feature has no effect on the machine dimensions and weight.

IBM Emperor II Water Cooled Machine

Dimensions (rounded to the nearest 0.1" or 0.1 cm):

Systems with all covers

                               Depth Width Height
------------------------------ ----- ----- ------
Inches                         77.5  61.6  79.3
Centimeter                     196.9 156.5 201.3
Inches (O/H IO cable exit)     77.5  72.7  84.8(7)
Centimeter (O/H IO cable exit) 196.9 184.7 215.3

Note: (7) The height with overhead I/O cable exit differs from the standard height only with the optional optical cable organizer feature installed.

Systems with all covers and height reduction

           Depth Width Height
---------- ----- ----- ------
Inches     77.5  61.6  70.3
Centimeter 196.9 156.5 178.5

Each frame with one side cover and without packaging

           Depth Width Height
---------- ----- ----- ------
Inches     54.0  30.7  79.3
Centimeter 137.2 78.0  201.3

Each frame on casters with one side cover and with packaging (domestic)

           Depth Width Height
---------- ----- ----- ------
Inches     61.4  32.4  79.8
Centimeter 156.0 82.2  202.6

Each frame with one side cover and with packaging (ARBO crate)

           Depth Width Height
---------- ----- ----- ------
Inches     68.   36.5  87.6
Centimeter 171.7 92.7  222.5

Approximate weight:

System with IBF feature

                       Newbuild Newbuild
                       Minimum  Maximum
                       System   System
                       Model    Model
                       LM1 No   LM5 Max
                       I/O      # of I/O
                       drawer   drawers
---------------------- -------- --------
kg                     1546     2737
lb                     3408     6034
kg (O/H IO cable exit) 1600     2791
lb (O/H IO cable exit) 3528     6154

System without IBF feature

                       Newbuild Newbuild
                       Minimum  Maximum
                       System   System
                       Model    Model
                       LM1 No   LM5 Max
                       I/O      # of I/O
                       drawer   drawers
---------------------- -------- --------
kg                     1343     2433
lb                     2961     5363
kg (O/H IO cable exit) 1398     2487
lb (O/H IO cable exit) 3081     5483

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

The dc power feature has no effect on the machine dimensions and weight.

Operating environment

Operating environment - IBM Emperor II Air Cooled Machine

Environmental class - ASHRAE 3

Temperature: 5 to 40 degrees C (41 to 104 degrees F) for all models up to 900 meters above sea level; maximum ambient reduces 1 degree C per 300 meters above 900 meters

Relative Humidity: 8 to 85 (percent) Wet Bulb (Caloric Value): 25 degrees C (77 degrees F)

Operating Mode Max Dew Point: 24 degrees C (75.2 degrees F) - Operating Mode

Electrical Power (maximum)

Utility      LM1      LM2      LM3      LM4      LM5      Power
                                                          Factor
------------ -------- -------- -------- -------- -------- ------
200-240 V ac 10.4 kVA 19.0 kVA 23.3 kVA 28.3 kVA 29.9 kVA 0.996
380-415 V ac 10.6 kVA 19.3 kVA 23.8 kVA 28.9 kVA 30.6 kVA 0,978
480 V ac     10.9 kVA 20.0 kVA 24.7 kVA 29.9 kVA 31.6 kVA 0.961
400 V dc     10.1 kW  18.3 kW  22.6 kW  27.4 kW  29.0 kW  -

Capacity of Exhaust: 6370 cubic meters / hour (3800 CFM)

Noise level:

  • Typical Configuration (Model LM2):
    • Declared A-Weighted Sound Power Level, LWAd(B) = 7.8
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 59
  • Maximum Configuration (Model LM5):
    • Declared A-Weighted Sound Power Level, LWAd(B) = 8.1
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 62

Leakage and Starting Current: 70 mA / 170 A (approximately 100 microseconds)

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

Operating environment - IBM Emperor II Water Cooled Machine

Environmental class - ASHRAE 3

Temperature: 5 to 40 degrees C (41 to 104 degrees F) for all models up to 900 meters above sea level; maximum ambient reduces 1 degree C per 300 meters above 900 meters

Relative Humidity: 8 to 85 (percent) Wet Bulb (Caloric Value): 25 degrees C (77 degrees F)

Operating Mode Max Dew Point: 24 degrees C (75.2 degrees F) - Operating Mode

Electrical Power (maximum)

Utility      LM1      LM2      LM3      LM4      LM5      Power
                                                          Factor
------------ -------- -------- -------- -------- -------- ------
200-240 V ac 10.0 kVA 18.1 kVA 22.3 kVA 26.4 kVA 27.9 kVA 0.996
380-415 V ac 10.2 kVA 18.6 kVA 22.9 kVA 27.1 kVA 28.6 kVA 0,978
480 V ac     10.5 kVA 19.3 kVA 23.7 kVA 28.1 kVA 29.6 kVA 0.958
400 V dc     9.7 kW   17.7 kW  21.6 kW  25.6 kW  27.6 kW  -

Capacity of Exhaust: 5950 cubic meters / hour (3500 CFM)

Noise level:

  • Typical Configuration (Model LM2)
    • Declared A-Weighted Sound Power Level, LWAd(B) = 7.9
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 60
  • Maximum Configuration (Model LM5)
    • Declared A-Weighted Sound Power Level, LWAd(B) = 8.0
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 61

Leakage and Starting Current: 70 mA / 170 A (approximately 100 microseconds)

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

Limitations

Not applicable.

Hardware requirements

The hardware requirements for the IBM LinuxONE servers, features, and functions are identified. A new driver level is required. HMC (V2.14.0) plus MCLs and the Support Element (V2.14.0) are planned to be available on September 13, 2017.

You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

HMC system support

The new functions available on the Hardware Management Console (HMC) version 2.14.0, as described, apply exclusively to IBM Emperor II, andz14. However, the HMC version 2.14.0 will also support the systems listed in the table below.

Family              Machine Type Firmware SE      Ensemble
                                 Driver   Version Node
                                                  Potential
------------------- ------------ -------- ------- ---------
z14 and Emperor II  3906         32       2.14.0  Yes
z13 and Emperor     2964         27       2.13.1  Yes
z13s and Rockhopper 2965         27       2.13.1  Yes
zBX Node            2458 Mod 004 22       2.13.0  Required
zBC12               2828         15       2.12.1  Yes
zEC12               2827         15       2.12.1  Yes
z114                2818         93       2.11.1  Yes
z196                2817         93       2.11.1  Yes
z10 BC              2098         79       2.10.2  No
z10 EC              2097         79       2.10.2  No

Peripheral hardware and device attachments

IBM devices previously attached to IBM System z196, z114, zEC12, zBC12, z13, Emperor, z13s, Rockhopper, and z14 servers are supported for attachment to IBM Emperor II channels, unless otherwise noted. The subject I/O devices must meet the FICON and Fibre Channel Protocol (FCP) architectures to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.

While the IBM Emperor II supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.

Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.

Information on switches and directors qualified for IBM Z FICON and FCP channels can be found in the Library section of Resource Link .

Software requirements

IBM Emperor II requires at a minimum:

  • z/VM V6.4 with PTFs (compatibility including Crypto Express6S and OSA-Express6S support, z/Architecture IPL).
  • z/VM V6.3 with PTFs (compatibility including Crypto Express6S and OSA-Express6S support, z/Architecture IPL).
  • Linux on z Systems - IBM plans to support running the following Linux on z Systems distributions on IBM Emperor II:
    • SUSE SLES 12 SP2 with service and SUSE SLES 11 SP4 with service.
    • Red Hat RHEL 7.3 with service and Red Hat RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

The following software requirements are listed for features and capabilities supported on IBM Emperor II:

FICON Express16S+ (CHPID type FC) when utilizing FICON or Channel-To-Channel (CTC), requires at a minimum:

  • z/VM V6.4.
  • z/VM V6.3.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FC) for support of zHPF single-track operations requires at a minimum:

  • z/VM V6.4.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FC) for support of zHPF multitrack operations requires at a minimum:

  • z/VM V6.4.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FCP) for support of SCSI devices requires at a minimum:

  • z/VM V6.4.
  • z/VM V6.3.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FCP) support of hardware data router requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

T10-DIF support by the FICON Express16S+ features when defined as CHPID type FCP requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service (DIF and DIX) and SLES 11 SP4 with service (DIF and DIX).
    • RHEL 7.3 with service (DIF and DIX) and RHEL 6.9 with service (DIF only).
    • Ubuntu 16.04 LTS (or higher) with service (DIF and DIX).
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S GbE LX (#0422) and GbE SX (#0423) require at a minimum: CHPID type OSD:

  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

CHPID type OSD without maximum port exploitation (one port on the PCIe adapter is available for use):

  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S 10 GbE LR (#0424) and 10 GbE SR (#0425) require at a minimum:

CHPID type OSD:

  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

CHPID type OSX for access control to the intraensemble data network (IEDN) from IBM Emperor II to Unified Resource Manager functions:

  • z/VM V6.4 to define, modify, and delete OSX CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 to define, modify, and delete OSX CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S 1000BASE-T Ethernet (#0426) requires at a minimum:

CHPID type OSD with exploitation of two ports per CHPID:

  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.

CHPID type OSD without maximum port exploitation (one port on the PCIe adapter is available for use):

  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

CHPID type OSM for intranode management network (INMN):

  • z/VM V6.4 to define, modify, and delete CHPID type OSM when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 to define, modify, and delete CHPID type OSM when z/VM is the controlling LPAR for dynamic I/O.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Crypto Express6S (#0893) Toleration, which treats Crypto Express6S cryptographic coprocessors and accelerators as Crypto Express5 coprocessors and accelerators, requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via maintenance or future distribution releases for:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Crypto Express6S (#0893) support of greater than 16 Domains requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via maintenance or future distribution releases for:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Crypto Express6S (#0893) Exploitation requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support future distribution releases.

10GbE RoCE Express2 (#0412) for Shared Memory Communications - Remote Direct Memory Access (SMC-R) requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via maintenance or future distribution releases for:
    • SLES 12 SP2.
    • RHEL 7.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

10GbE RoCE Express2 (#0412) for Ethernet communications (which does not require a peer OSA) including Single Root I/O Virtualization (SR-IOV) requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: Currently limited to experimental support in:
    • SLES 12 SP2.
    • RHEL 7.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

zEDC Express (#0420) requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service.
    • RHEL 7.3 with sevice.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Transactional memory requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM Z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

2 GB Large Pages requires at a minimum:

  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

Guarded Storage requires at a minumum:

  • z/VM V6.4 with PTFs for guest exploitation (December 15, 2017 availability).
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

Instruction Execution Protection Facility requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation (December 15, 2017 availability).
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

Back to topBack to top
 
Publications

The following publications are available now in the Library section of Resource Link (TM):

Title                                                     Order
                                                          number
--------------------------------------------------------- ---------
IBM 3906 Installation Manual for Physical Planning (IMPP) GC28-6965
PR/SM (TM) Planning Guide                                 SB10-7169
IOCP User's Guide for ICP                                 SB10-7172
Planning for Fiber Optic Links                            GA23-1408

The following publications are shipped with the product and will be available at planned availability in the Library section of Resource Link:

Title                                                          Order
                                                               number
-------------------------------------------------------------- ---------
IBM 3906 Installation Manual                                   GC28-6964
IBM 3906 Service Guide                                         GC28-6966
Service Guide for TKE Workstations (Version 7.0)               GC28-6980
Systems Safety Notices                                         G229-9054
IBM Important Notices                                          G229-9056
IBM 3906 Safety Inspection                                     GC28-6963
Systems Environmental Notices and User Guide                   Z125-5823
Statement of Limited Warranty                                  GC28-6979
License Agreement for Machine Code                             SC28-6872
License Agreement for Machine Code Addendum for Elliptic Curve GC27-2635
Cryptography

The following publications will be available at planned availability in the Library section of Resource Link:

Title                                                    Order
                                                         number
-------------------------------------------------------- ---------
IBM 3906 Parts Catalog                                   GC28-6967
Service Guide for 2461 HMC                               GC28-6981
Service Guide for 2461 Support Element                   GC28-6982
Service Guide for HMCs and SEs                           GC28-6983
Hardware Management Console Security                     SC28-6987
SNMP Application Programming Interfaces                  SB10-7171
Capacity on Demand User's Guide                          SC28-6985
CHPID Mapping Tool User's Guide                          GC28-6984
Hardware Management Console Web Services API (V2.14.0)   SC27-2636
IBM Dynamic Partition Manager (DPM) Guide                SB10-7170
Secure Service Container User's Guide                    SC28-6978
Integrating the HMC's Broadband RSF into your Enterprise SC28-6986
SCSI IPL - Machine Loader Messages                       SC28-6948
Stand-Alone IOCP User's Guide                            SB10-7173
Ensemble Workload Resource Group Management Guide        GC27-2633
Ensemble Planning Guide                                  GC27-2631
OSA-Express Customer Guide and Reference                 SA22-7935
OSA Integrated Console Controller User's Guide           SC27-9003
OSA/SF on the Hardware Management Console                SC14-7580
FICON CTC Reference                                      SB10-7174
Maintenance Information for Fiber Optic Links            SY27-7696

Resource Link: Publications for IBM Emperor II can be obtained at the Resource Link website.

Using the instructions on the Resource Link panels, obtain a user ID and password. Resource Link has been designed for easy access and navigation.

HMC and SE console documentation

At planned availability, the Hardware Management Console (HMC) and Support Element (SE) console documentation (Version 2.14.0) will be available from IBM Knowledge Center. IBM Knowledge 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.

The following Redbooks publications are available now. To order, contact your IBM representative.

Title         Order number
------------- ------------
z14           SG24-8450-00
z14           SG24-8451-00
z14           SG24-8460-00
IBM z Systems SG24-5444-17
IBM z Systems REDP-5157-02

To download these Redbooks publications, go to the IBM zEnterprise System Redbooks website.

For other IBM Redbooks publications, go to the main IBM Redbooks website.

IBM Knowledge 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 Knowledge Center website.

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

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

Features
TOC Link Features - No charge TOC Link Features - Chargeable TOC Link Feature descriptions


Features - No charge

COLOR: A specify code is not required.

VOLTAGE: A specify code for line cord feature codes is required and will be provided by the configurator based on the country code of the order.

LANGUAGE: A specify code for language is required and will be provided by the configurator based on the country code of the order.

Feature Code Title
------------ -----------------------------
0014         Migration Offering Machine
0099         WWPN Persistence
0186         Client Must Provide Mouse
0187         Client Must Provide HMC Keybd
0188         Client Must Provide HMC KMM
0189         Client Must Provide TKE Keybd
0190         Client Must Provide TKE KMM
0191         Client Must Provide Display

Features - Chargeable

Feature Code Title
------------ ----------------------------
0016         HW for DPM
0017         Customized MRReport
0018         Cost Analysis Sizing
0019         Manage FW Suite
0020         Automate FW Suite
0025         Ensemble membership
0032         Non RSF On/Off CoD
0034         OSA-ICC 3215 Enablement
0035         RFID Tag
0036         RFID Tag
0037         RFID Tag
0072         Air w/o TEIO & w/o HtrR
0073         Air w/o TEIO & w/HtR
0074         Air w/ TEIO & w/o HtR
0075         Air w/TEIO & w/HtR
0076         Wat w/o TEIO & w/o HtrR
0077         Wat w/o TEIO & w/ HtR
0078         Wat w/TEIO & w/o HtR
0079         Wat w/TEIO & w/HtR
0082         HMC
0083         HMC Rack Mount
0085         TKE Rack Mount w/4768
0086         TKE w/4768
0105         Air w/o TEIO & w/o HtrR
0106         Air w/o TEIO & w/HtR
0107         Air w/TEIO & w/o HtR
0108         Air w/TEIO & w/HtR
0109         Wat w/o TEIO & w/o HtrR
0110         Wat w/o TEIO & w/HtR
0111         Wat w/TEIO & w/o HtR
0112         Wat w/TEIO & w/HtR
0119         1 CPE Capacity Unit-IFL
0120         100 CPE Capacity Unit-IFL
0127         1 CPE Capacity Unit-SAP
0128         100 CPE Capacity Unit-SAP
0148         HMC Table Top KMM
0152         Mouse
0153         HMC Tower Keyboard
0154         HMC Rack Keybd/Monitor/Mouse
0155         TKE Tower Keyboard
0156         KE Rack Keybd/Monitor/Mouse
0157         TKE Table Top KMM
0412         10 GbE RoCE Express2
0420         zEDC Express
0422         OSA-Express6S GbE LX
0423         OSA-Express6S GbE SX
0424         OSA-Express6S 10 GbE LR
0425         OSA-Express6S 10 GbE SR
0426         OSA-Express 1000BASE-T
0427         FICON Express16S+ LX
0428         FICON Express16S+ SX
0431         zHyperLink Express
0604         IBM Virtual Flash Memory (VFM)
0848         32GB USB Backup Media
0879         TKE 9.0 LIC
0891         TKE Smart Card Reader
0893         Crypto Express6S
1021         STP Enablement
1750         LICCC Ship Via Net Ind
1929         CP4
1933         IFL
1935         SAP (optional)
1937         Unassigned IFL
1990         32GB Preplanned memory
1999         64GB VFM Preplanned memory
2000         Line Cord Plan Ahead
3003         Balanced Power Plan Ahead
3103         Universal Lift Tool Upg Kit
3105         Universal Lift Tool/Ladder
3216         Internal Battery IBF
3379         FDT Adapter Kit
3380         Fill and Drain Kit
3863         CPACF Enablement
4013         PCIe I/O Drawer
4029         A Fr Radiator
4030         A Fr Water
6096         Flat Panel Display
6805         Additional CBU Test
6817         Total CBU Years Ordered
6818         CBU Records Ordered
6822         Single CBU IFL Year
6823         25 CBU IFL Year
6830         Single CBU SAP Year
6831         25 CBU SAP Year
6832         CBU Replenishment
6833         Capacity for Planned Event
7801         14ft Water Hose
7923         FQC Bracket & Mounting Hdw
7924         LC Duplex 6.6 ft Harness
7925         LC Duplex 8.5ft Harness
7926         LC Duplex 12 ft Harness
7942         Top Exit I/O Cabling
7949         Side Covers
7998         Non Raised Floor Support
8003         4-in-1 Bolt Down Kit
8004         3-in-1 Bolt Down Kit-W
8005         Bolt Down Kit, NRF
9896         On/Off CoD authorization
9898         Perm upgr authorization
9900         On-Line CoD Buying (Flag)
9910         CBU authorization
9912         CPE authorization
9917         1 MSU day
9918         100 MSU days
9919         10000 MSU days
9920         1 IFL day
9921         100 IFL days
9928         1 SAP day
9929         100 SAP days
9970         Weight Distribution Kit
9975         Height Reduce Ship
9976         Height reduce for return

Feature descriptions

(#0148) HMC Table Top KMM

Feature code #0148 is a table top Monitor with a keyboard in the language of choice. There is a touchpad for pointing. Included is a country specific power cord.

  • Minimum: Zero
  • Maximum: One per Tower HMC #0082
  • Prerequisites: Tower HMC #0082
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Power cord, Video cable, and a USB cable are provided.
(#0157) TKE Table Top KMM

Feature code #0157 is a table top Monitor with an US English keyboard #103P. There is a touchpad for pointing. Included is a country specific power cord.

  • Minimum: Zero
  • Maximum: One per Tower TKE #0086
  • Prerequisites: Tower TKE #0086
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Power cord, Video cable, and a USB cable are provided.
(#0186) Client Must Provide Mouse

Feature code #0186 is a non-selectable feature code. If instructed by IBM to de-select feature code #0152, due to import restrictions, then #0186 is added to the order to inform the client that they must provide a USB optical mouse with a finger wheel.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082 and/or Tower TKE #0086.
  • Prerequisites: Tower HMC #0082 and/or Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: Mouse #0152.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0187) Client Must Provide HMC Tower KeyBd

Feature code #0187 is a non-selectable feature code. If instructed by IBM to de-select feature code #0153, due to import restrictions, then #0187 is added to the order to inform the client that they must provide a USB Keyboard in the proper language.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082.
  • Prerequisites: Tower HMC #0082.
  • Corequisites: None.
  • Compatibility Conflicts: HMC Tower Keyboard #0153.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0188) Client Must Provide HMC KMM

Feature code #0188 is a non-selectable feature code. If instructed by IBM to de-select feature code #0154, due to import restrictions, then #0188 is added to the order to inform the client that they must provide a 1u Rack Mounted Monitor and Keyboard with a built in pointing device. The Keyboard must be in the proper language. Both the keyboard and pointing device must be USB and have a proper cable to reach the HMC. The Monitor must be VGA. Its cable must have a male HD15 connector and also reach the HMC.

  • Minimum: None.
  • Maximum: One per Rack Mounted HMC #0083.
  • Prequisites: The Rack Mounted HMC #0083.
  • Corequisites: None.
  • Compatibility Conflicts: HMC Rack Keybd/Monitor/Mouse #0154.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0189) Client Must ProvideTKE Tower KeyBd

Feature code #0189 is a non-selectable feature code. If instructed by IBM to de-select feature code #0155, due to import restrictions, then #0189 is added to the order to inform the client that they must provide a USB Keyboard in US English.

  • Minimum: None.
  • Maximum: One per Tower TKE #0086.
  • Prerequisites: Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: TKE Tower Keyboard #0155.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0190) Client Must Provide TKE KMM

Feature code #0190 is a non-selectable feature code. If instructed by IBM to de-select feature code #0156, due to import restrictions, then #0190 is added to the order to inform the client that they must provide a 1u Rack Mounted Monitor and Keyboard with a built in pointing device. The Keyboard must be in US English. Both the keyboard and pointing device must be USB and have a proper cable to reach the TKE. The Monitor must be VGA. Its cable must have a male HD15 connector and also reach the TKE.

  • Minimum: None.
  • Maximum: One per Rack Mounted TKE #0085.
  • Prequisites: The Rack Mounted TKE #0085.
  • Corequisites: None.
  • Compatibility Conflicts: TKE Rack Keybd/Monitor/Mouse #0156.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0191) Client Must Provide Display

Feature code #0191 is a non-selectable feature code. If instructed by IBM to de-select feature code #6096, due to import restrictions, then #0191 is added to the order to inform the client that they must provide a Table Top Display. The Display must be VGA. Its cable must have a male HD15 connector and reach the HMC or TKE.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082 and/or Tower TKE #0086.
  • Prequisites: The Tower HMC #0082 and/or Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: Display #6096.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0014) Migration Offering Machine

Feature code #0014 is an information only feature code which is required to initiate an order to be fulfilled through a Migration Offering.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Initial system order only. Not offered in Japan.
  • Field Installable: N/A.
(#0099) WWPN Persistence

Feature code #0099 is an information only feature code which is required to initiate an ordering option to maintain IO serial numbers when a newly purchased system will replace an existing system within the customer's data center. This option eliminates the need to reconfigure zoning in SAN switches and LUN masking in storage controllers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
(#0016) HW for DPM

This feature code provides the cabling required for OSA-Express6S 1000 BASE-T Ethernet (#0426) features defined as CHPID type OSM connectivity which is used with Dynamic Partition Manager (DPM).

Note: The OSA-Express6S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition Manager when configured.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Two OSA-Express6S 1000BASE-T Ethernet (#4026) features are required, for primary and backup connectivity. A port is defined as CHPID type OSM .
  • Compatibility Conflicts: The OSA-Express6S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition Manager when configured.
  • Customer Setup: No.
  • Limitations: Dynamic Partition Manager can be ordered along with Ensemble Membership (FC #0025) but they cannot both be enabled at the same time on the system. Dynamic Partition Manager supports Linux, running in an LPAR, on KVM on IBM Z hypervisor, and on z/VM V6.4.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Two 3.2 meter (10.5 feet) Category 6 copper cables with RJ-45 connectors of each end are provided. Installation is performed by service personnel.
(#0017) Customized MRReport

This feature code is strictly for S/390 Manufacturing 1 Poughkeepsie Product Assistance Center to create and to charge customers for a Customized MRREPORT for zSystem machines. U.S CUSTOMERS - Contact Poughkeepsie Product Assistance Center for the customized MRReport. WORLD TRADE CUSTOMERS: Do not order this FC prior to contacting HELPS390 at IBMFR for assistance.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0018) Cost Analysis Sizing

This feature code is used to charge a fee for time spent on the request that requires extensive IBM Development and Engineering review, evaluation, consultation and cost analysis. When the feature code is eventually ordered, the cost for the evaluation and sizing may, in some cases, be deducted from the quoted price.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0019) Manage FW Suite

This feature is used to enable the base set of tiered function associated with the IBM Z Unified Resource Manager. The Manage suite includes core operational controls, installation and configuration management, energy monitoring, hypervisor management, and intraensemble data network (IEDN) management, as well as virtual server lifecycle management. The Manage suite is included in the base IBM Emperor II at no charge for CPs and IFLs. One of the two tiered suites of functionality for the IBM Z Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate Suite (#0020), is ordered, Manage Suite (#0019) is automatically included.

  • Minimum: None or one if using IBM Z Unified Resource Manager.
  • Maximum: One.
  • Prerequisites: None.
  • Corequisites: Either #0019 or #0020 must be ordered. If the Automate Suite (#0020) is ordered, the Manage suite (#0019) is automatically included.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0020) Automate Suite

This feature is used to enable the Automate suite of functionality associated with the IBM Z Unified Resource Manager. The Automate Suite includes representation of resources in a workload context, goal-oriented monitoring and management of resources, and energy management. The Automate Suite is included in the base IBM Emperor II at no charge for CPs and IFLs. One of the two tiered suites of functionality for the IBM Z Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate Suite (#0020), is ordered, Manage suite (#0019) is automatically included.

  • Minimum: None or one if using IBM Z Unified Resource Manager.
  • Maximum: One.
  • Prerequisites: None.
  • Corequisites: Either #0019 or #0020 must be ordered. If the Automate Suite (#0020) is ordered, the Manage suite (#0019) is automatically included.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0025) Ensemble membership

This feature ships the appropriate cabling for connectivity to the intranode management network (INMN).

Ensemble membership requires that the IBM Emperor II have two OSA-Express6S 1000BASE-T Ethernet features defined as CHPID type OSM for connectivity to the intranode management network (INMN). Communication across the INMN is exclusively for the purpose of enabling the IBM Z Unified Resource Manager of the Hardware Management Console (HMC) to perform its various management disciplines (such as performance management, network virtualization management, energy management, etc.).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Two OSA-Express6S 1000BASE-T Ethernet (#0426) features are required, for primary and backup connectivity. A port is defined as CHPID type OSM.
  • Compatibility Conflicts: The OSA-Express6S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition manager when configured.
  • Customer Setup: No.
  • Limitations: Ensemble membership can be ordered along with HW for DPM (#0016) but they cannot both be enabled at the same time on the system.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Two 3.2 meter (10.5 feet) Category 6 copper cables with RJ-45 connectors of each end are provided. Installation is performed by service personnel.
(#0032) NonRSF Connection for On/Off Capacity on Demand (On/Off
CoD)

The purpose of this feature code is to allow for alternative delivery of On/Off CoD records to customers, by allowing for the downloading of record from the Resource Link web site, verses the normal electronic call home delivery. Feature code 0032 will be added to the ResourceLink profile to indicate the On/Off CoD link will be delivered via media/CDRom. This signals Business Practices to establish a contract addendum that details the requirements for VPD transmission, billing practices, warranty terms.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0035) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0036 and #0037.
  • Customer Setup: No.
  • Limitations: Available on box orders in :
    ----------------- ----------------- ------------------- -----------------
    Argentina         Chile             Israel              Saint Lucia
    Aruba             China             Jamaica             Sri Lanka
    Bahamas           Colombia          Korea               Singapore
    Bangladesh        Costa Rica        Laos                Suriname
    Barbados          Dominican         Macao               Taiwan
                      Republic
    Belize            Ecuador           Malaysia            Thailand
    Bermuda           El Salvador       Mexico              Trinidad & Tobago
    Bolivia           Guatemala         Myanmar             United States
    Brazil            Guyana            NetherlandsAntilles Uruguay
    Brunei Darussalam Haiti             Nicaragua           Venezuela
    Cambodia          Honduras          Panama              Viet Nam
    Canada            Hong Kong         Peru
    
  • Field Installable: Yes.
(#0036) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0035 and #0037.
  • Customer Setup: No.
  • Limitations: Available on box orders in :
    --------------- ----------------- ----------------- --------------------
    Abu Dhabi       Egypt             Lesotho           Senegal
    Afghanistan     Equatorial Guinea Liberia           Serbia
    Albania         Eritrea           Libya             Seychelles
    Algeria         Estonia           Liechtenstein     Slovakia
    Angola          Ethiopia          Lithuania         Slovenia
    Armenia         France            Luxembourg        Sierra Leone
    Austria         Finland           Macedonia         Spain
    Azerbaijan      Gabon             Madagascar        Somolia
    Belarus         Gambia            Mali              South Africa
    Belgium         Georgia           Malta             Sudan
    Benin           Germany           Mauretania        Swaziland
    Bosnia          Ghana             Martinique        Sweden
    Botswana        Greece            Middle East DB    Switzerland
    Bulgaria        Guadeloupe        Moldova           Syrian Arab Republic
    Burkinao Faso   Guinea            Montenegro        Szekesfehervar
    Burundi         Guinea Bissau     Morocco           Tajikistan
    Cape Verde      Guinea Conocracy  Namibia           Tanzania
    Bulgaria        Guadeloupe        Moldova           Syrian Arab Republic
    Burkinao Faso   Guinea            Montenegro        Szekesfehervar
    Burundi         Guinea Bissau     Morocco           Tajikistan
    Cape Verde      Guinea Conocracy  Namibia           Tanzania
    Cameroon        Hungary           Netherlands       Togo
    Central African Iceland           New Zealand       Turkey
    Republic
    Chad            India             Niger             Turkmenistan
    Comoros         Iran              Norway            Uganda
    Congo           Iraq              Oman              Ukraine
    Croatia         Ireland           Pakistan          United Kingdom
    Cyprus          Italy             Poland            Uzbekistan
    Czech Republic  Ivory Coast       Portugal          Yemen
                    Jordan            Romania           Zambia
    DemocraticRepub
    Denmark         Kuwait            Russian           Zimbabwe
                                      Federation
    Djibouti        Kyrgyzstan        Rwanda
    Eastern Europe  Latvia            Sao Tome 1
    Direct Business                   Princip
    
  • Field Installable: Yes.
(#0037) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0035 and #0036.
  • Customer Setup: No.
  • Limitations: Available on box orders in Japan.
  • Field Installable: Yes.
(#0072) Air w/o TEIO & w/o HtrR

This feature provides a means to order and price return packaging materials for installed zEC12 machines which are being returned or relocated. Select #0072 when the system to be moved is MT 2827, radiator cooled, without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0073, #0074, #0075,# 0076, #0077, #0078, #0079,#0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0073) Air w/o TEIO & w/HtrR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0073 when the system to be moved is MT 2827, radiator cooled, without Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111 and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0074) Air w/TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0074 when the system to be moved is MT 2827, radiator cooled, with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0075, #0076, #0077, #0078, #0079, #0015, # 0106, #0107, #0108 ,#0109, #0110, #0111 and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0075) Air w/TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0075 when system to be moved is MT 2827, radiator cooled, with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0076) Wat w/o TEIO & w/o HtrR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0076 when the system to be moved is MT 2827, water cooled, without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0077) Wat w/o TEIO & w/HtrR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0077 when the system to be returned is MT 2827, water cooled, without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0078) Wat w/TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0078 when the system to be moved is MT 2827, water cooled, with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0079) Wat w/TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0079 when the system to be returned is MT 2827, water cooled, with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0082) HMC

The Hardware Management Console (HMC) has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured HMC ordered with IBM Emperor II, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the HMC, depending on setup configuration. In addition, if call home support is enabled on the HMC, additional analysis of events logged by the HMC will be available on IBM Resource Link. The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC. Although customers can carry forward their HMCs on IBM Emperor II, these tamper protection capabilities will only be delivered on newly manufactured HMCs. The IBM Emperor II environment can contain both HMCs that have been carried forward and newly manufactured HMCs.

  • Minimum: In an ensemble, Two; otherwise None.
  • Maximum: Ten (10), combination of #0082 and #0083.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports IBM Emperor II. It can also be used to support z13, LinuxONE Emperor, z13s, LinuxONE Rockhopper, zEC12, and zBC12 z196, z114, z10 EC, and z10 BC servers. They must be upgraded to a new AROM level.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0083) HMC Rack Mount

Feature code 0083 is a 1u Rack Mounted HMC. These rack mounted HMC components are 19 inch rack mountable components that can be placed in customer 19 inch racks. The Hardware Management Console (HMC) has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured HMC ordered with IBM Emperor II or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the HMC, depending on setup configuration. In addition, if call home support is enabled on the HMC, additional analysis of events logged by the HMC will be available on IBM Resource Link. The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC. Although customers can carry forward their HMCs on IBM Emperor II, these tamper protection capabilities will only be delivered on newly manufactured HMCs. The IBM Emperor II environment can contain both HMCs that have been carried forward and newly manufactured HMCs.

  • Minimum: In an ensemble, Two; otherwise None.
  • Maximum: Ten (10), combination of #0082 and #0083.
  • Prerequisites: The rack mount unit is plugged in a customer supplied frame, not the IBM Z frame, and requires customer supplied PDUs.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports IBM Emperor II. It can also be used to support z13, LinuxONE Emperor, z13s, LinuxONE Rockhopper, zEC12, zBC12, z196, z114, z10 EC, and z10 BC servers. They must be upgraded to a new AROM level.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0085) TKE Rack Mount w/4768

Feature code 0085 is a new purchase of a 1u Rack Mounted TKE. These rack mounted TKE components are 19 inch rack mountable components that can be placed in customer 19 inch racks. A client provided shelf is recommended for holding any USB Smart Card readers. You can order up to 10 TKE feature code per CPC. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network connected to one or more servers, and designed to provide a secure, hardware-based compliance-level method for master and operational key entry as well as local and remote management of the cryptographic coprocessor features. This feature provides basic key management -- key identification, exchange, separation, update, backup, as well as security administration. This feature is optional when used to manage a Crypto Express feature that is running in Common Cryptographic Architecture (CCA) coprocessor. The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 10, 100, or 1000 Mbps. The TKE has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured TKE ordered with IBM Emperor II, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the TKE, depending on setup configuration. Although customers can carry forward their TKEs on IBM Emperor II, these tamper protection capabilities will only be delivered on newly manufactured TKEs. The IBM Emperor II environment can contain both TKEs that have been carried forward and newly manufactured TKEs.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10, combination of #0085, and #0086.
  • Prerequisites: None.
  • Corequisite: None.
  • Compatibility Conflicts: If you have smart cards and smart card readers from previous generations of TKEs in your environment, be aware of the following smart card and smart card reader considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0086) TKE w/4768

Feature code 0086 is a new purchase of Tower TKE. You can order up to 10 TKE feature code per CPC. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network connected to one or more servers, and designed to provide a secure, hardware-based compliance-level method for master and operational key entry as well as local and remote management of the cryptographic coprocessor features.

This feature provides basic key management -- key identification, exchange, separation, update, backup, as well as security administration. This feature is optional when used to manage a Crypto Express feature that is running in Common Cryptographic Architecture (CCA) coprocessor.

The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 10, 100, or 1000 Mbps. The TKE has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured TKE ordered with IBM Emperor II, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the TKE, depending on setup configuration. Although customers can carry forward their TKEs on IBM Emperor II, these tamper protection capabilities will only be delivered on newly manufactured TKEs. The IBM Emperor II environment can contain both TKEs that have been carried forward and newly manufactured TKEs.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10, combination of #0085, and #0086.
  • Prerequisites: None.
  • Corequisite: None.
  • Compatibility Conflicts: If you have smart cards and smart card readers from previous generations of TKEs in your environment, be aware of the following smart card and smart card reader considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0105) Air w/o TEIO & w/o HtrR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0105 when the system to be returned is MT 2964, radiator cooled, without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0106) Air w/o TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0106 when the system to be returned is MT 2964, radiator cooled, without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0107) Air w/TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0107 when the system to be returned is MT 2964, radiator cooled, with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0108) Air w/TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0108 when the system to be returned is MT 2964, radiator cooled, with Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0109) Wat w/o TEIO & w/o HtrR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0109 when the system to be returned is MT 2964, water cooled, without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0110) Wat w/o TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0110 when the system to be returned is MT 2964, water cooled, without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0111) Wat w/TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0111 when the system to be returned is MT 2964, water cooled, with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0112) Wat w/TEIO & w/HtR

This feature provides a means to order and price return packaging materials for installed machines which are being returned or relocated. Select #0112 when the system to be returned is MT 2964, water cooled, with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, 30074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, and #0111.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0119) 1 CPE Capacity Unit-IFL

Pricing feature equal to the remainder of the three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833) .
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0120) 100 CPE Capacity Unit-IFL

Pricing feature equal to the quotient of three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-IFL (#0119).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0127) 1 CPE Capacity Unit-SAP

Pricing feature equal to the remainder of the three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0128) 100 CPE Capacity Unit-SAP

Pricing feature equal to the quotient of three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-SAP (#0127).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0152) Mouse

Feature code #0152 is a USB optical mouse with a finger wheel.

  • Minimum: One per Tower HMC #0082 or Tower TKE #0086.
  • Maximum: One per Tower HMC #0082 or Tower TKE #0086.
  • Prerequisites: Tower HMC or Tower TKE.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0153) HMC Tower Keyboard

Feature code #0153 is a USB keyboard, in the language specified.

  • Minimum: One per Tower HMC #0082.
  • Maximum: One per Tower HMC. #0082.
  • Prerequisites: Tower HMC #0082.
  • Corequisites: A language selection is required #0235 to #0249.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0154) HMC Rack Keybd/Monitor/Mouse

Feature code #0154 is a 1u Rack Mounted Display and Keyboard with a built in Pointing device. The Keyboard will come in the language specified.

  • Minimum: One per Rack Mounted HMC #0083.
  • Maximum: One per Rack Mounted HMC #0083.
  • Prequisites: The Rack Mounted HMC #0083.
  • Corequisites: A language selection is required #0235 to #0249.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB, VGA cable, and Power Jumper is included.
(#0155) TKE Tower Keyboard

Feature code #0155 is a USB keyboard, in the English language.

  • Minimum: One per Tower TKE #0086.
  • Maximum: One per Tower TKE #0086.
  • Prerequisites: Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0156) TKE Rack Keybd/Monitor/Mouse

Feature code #0156 is a 1u Rack Mounted Display and Keyboard with a built in Pointing device. The Keyboard will come in the English language.

  • Minimum: One per Rack Mounted TKE #0085.
  • Maximum: One per Rack Mounted TKE #0085.
  • Prequisites: The Rack Mounted TKE #0085.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB, VGA cable, and Power Jumper is included.
(#0412) 10GbE RoCE Express2

10GbE RoCE Express2 provides a natively attached PCIe I/O Drawer based Ethernet feature that supports 10 Gbps Converged Enhanced Ethernet (CEE) and RDMA over CEE (RoCE). The RoCE feature enables shared memory communications between two CPCs using a shared switch. The RoCE feature will also be exploited by Linux on z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP).

Single Root I/O Virtualization (SR-IOV) for 10 GbE RoCE Express2 allows a PCIe device to appear to be multiple separate physical PCIe devices. The SR-IOV specification is an industry standard specification to help promote interoperability. This provides the ability for that PCIe device to present multiple instances of itself up to the OS instance or hypervisor.

  • Minimum: 0.
  • Maximum: 8. Orderable by ports, in increments of 2, up to16 ports (8 features).
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Total limit of 8 RoCE Express + RoCE Express2 adapters for the machine.
  • Field Installable: Yes.
(#0420) zEDC Express

The zEDC Express feature is designed to help improve cross-platform data exchange, reduce CPU consumption, and save disk space. There is one PCIe adapter/compression coprocessor per feature. The zEDC Express feature can be shared by up to 15 LPARs.

  • Minimum: None. If used, a minimum of two is recommended.
  • Maximum: 16.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property IBM.
  • Cable Order: None.
(#0422) OSA-Express6S GbE LX

The OSA-Express6S Gigabit Ethernet (GbE) long wavelength (LX) feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID type OSD exclusively - TCP/IP, Layer 2, Layer 3 traffic). The ports support attachment to a one gigabit per second (Gbps) Ethernet Local Area Network (LAN). Each port can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S GbE LX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a long wavelength (LX) transciever. The sending and receiving transceivers must be the same (LX-to-LX).
  • Customer Setup: No.
  • Limitations: Total limit of 48 features for the machine.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector.
(#0423) OSA-Express6S GbE SX

The OSA-Express6S Gigabit Ethernet (GbE) short wavelength (SX) feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID type OSD exclusively - TCP/IP, Layer 2, Layer 3 traffic). The ports support attachment to a one gigabit per second (Gbps) Ethernet Local Area Network (LAN). Each port can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S GbE SX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX-to-SX).
  • Customer Setup: No.
  • Limitations: Total limit of 48 features for the machine.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector.
(#0424) OSA-Express6S 10 GbE LR

The OSA-Express6S 10 Gigabit Ethernet (GbE) long reach (LR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD (TCP/IP, Layer 2, Layer 3 traffic), and OSX (intraensemble data network - IEDN). The 10 GbE feature is designed to support attachment to a single mode fiber 10 Gigabit per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S 10 GbE LR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a long reach (LR) transceiver. The sending and receiving transceivers must be the same (LR-to-LR).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine.
    • When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from an Emperor II, z14, z13, Emperor, z13s, Rockhopper, zEC12, zBC12, z196, or z114 to an IBM Z BladeCenter Extension (zBX).
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0425) OSA-Express6S 10 GbE SR

The OSA-Express6S 10 Gigabit Ethernet (GbE) short reach (SR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD and OSX. The 10 GbE feature is designed to support attachment to a multimode fiber 10 gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.

  • Minimum: None.
  • Maximum: 48 features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S 10 GbE SR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a short reach (SR) transceiver. The sending and receiving transceivers must be the same (SR-to-SR).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine.
    • When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from an Emperor II, z14, z13, Emperor, z13s, Rockhopper, zEC12, or zBC12, z196, or z114 to an IBM Z BladeCenter Extension (zBX).
  • Field Installable: Yes.
  • Cable order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0426) OSA-Express6S 1000BASE-T

The OSA-Express6S 1000BASE-T Ethernet feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID). The following CHPIDs are supported:

  1. OSC (TN3270E and non-SNA DFT)

  2. OSD (TCP/IP, Layer 2, Layer 3 traffic)

  3. OSE (SNA/APPN/HPR traffic and TCP/IP passthru)

  4. OSM (Intranode management network - INMN)

Each port supports attachment to a 1000BASE-T (1000 Mbps or 1 Gbps) Ethernet Local Area Network (LAN). The feature supports autonegotiation and automatically adjusts to 100 or 1000 Mbps, depending upon the LAN. When the feature is set to autonegotiate, the target device must also be set to autonegotiate. The feature supports 100 Mbps or 1000 Mbps (1 Gbps) full duplex. It can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.

When configured at 1 Gbps, the 1000BASE-T Ethernet feature supports jumbo frames when in QDIO mode (CHPID type OSD).

  • Minimum: None.
  • Maximum: 48 features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: When the OSA-Express6S feature is set to autonegotiate, the target device must also be set to autonegotiate. Both ends must match (autonegotiate on or off).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine.
    • The 1000BASE-T feature supports full-duplex operation exclusively.
    • Using CHPID type OSM - OSA-Express for Unified Resource Manager, provides connectivity to the intranode management network (INMN) from z13 to Unified Resource Manager functions.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. The OSA-Express6S 1000BASE-T Ethernet feature supports use of an EIA/TIA Category 5 Unshielded Twisted Pair (UTP) cable terminated with an RJ-45 connector with a maximum length of 100 meters (328 feet).
(#0427) FICON Express16S+ LX

The FICON Express16S+ LX (long wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for z Systems (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture (supporting attachment to SCSI devices), providing connectivity between a combination of servers, directors, switches, and devices (control units, disk, tape, printers) in a storage area network (SAN). Each of the two independent ports/channels is capable of 4 gigabits per second (Gbps), 8 Gbps, or 16 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels.

FICON Express16S+ LX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems. The FICON Express16S+ LX feature also supports cascading (the connection of two FICON Directors in succession) to minimize the number of cross-site connections and help reduce implementation costs for disaster recovery applications, GDPS, and remote copy. Each FICON Express16S+ LX channel can be defined independently, for connectivity to servers, switches, directors, disks, tapes, and printers as:

  1. CHPID type FC - FICON, High Performance FICON for z Systems (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.

  2. CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.

The FICON Express16S+ LX feature utilizes a long wavelength (LX) laser as the optical transceiver and supports use of a 9 micron single mode fiber optic cable terminated with an LC Duplex connector. LX may also be referred to as LW by vendors.

  • Minimum: None. At least one I/O feature (FICON) must be present in a server.
  • Maximum: 160 features (320 channels) in PCIe I/O drawer (#4013).
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Ensure the attaching/downstream device has a long wavelength (LX) transceiver. The sending and receiving transceivers must be the same (LX-to-LX).
  • Customer Setup: No.
  • Limitations:
    • Can only be installed in PCIe I/O drawer (#4013).
    • The FICON Express16S+ LX feature does not support autonegotiation to 1 or 2 Gbps.
    • The FICON Express16S+ LX feature is designed to support distances up to 10 kilometers (6.2 miles) over 9 micron single mode fiber optic cabling without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
    • Both ports of the adapter need to be defined as either FC or FCP CHPIDs. A mix of FC and FCP CHPIDs on the same adapter is not supported.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0428) FICON Express16S+ SX

The FICON Express16S+ SX (short wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for z Systems (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture (supporting attachment to SCSI devices), providing connectivity between a combination of servers, directors, switches, and devices (control units, disk, tape, printers) in a storage area network (SAN).

Each of the two independent ports/channels is capable of 4 gigabits per second (Gbps), 8 Gbps, or 16 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels. FICON Express16S+ SX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

The FICON Express16S+ SX feature also supports cascading (the connection of two FICON Directors in succession) to minimize the number of cross-site connections and help reduce implementation costs for disaster recovery applications, GDPS, and remote copy.

Each FICON Express16S+ SX channel can be defined independently for connectivity to servers, switches, directors, disks, tapes, and printers as:

  1. CHPID type FC - FICON, High Performance FICON for z Systems (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.

  2. CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.

The FICON Express16S+ SX feature utilizes a short wavelength (SX) laser as the optical transceiver, and supports use of a 50 micron multimode fiber optic cable or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector.

Note: IBM does not support a mix of 50 and 62.5 micron fiber optic cabling in the same link. SX may also be referred to as SW by vendors.

  • Minimum: None. At least one I/O feature (FICON) must be present in a server.
  • Maximum: 160 features (320 channels) in PCIe I/O drawer (#4013).
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Ensure the attaching/downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX to SX).
  • Customer Setup: No.
  • Limitations:
    • Can only be installed in PCIe I/O drawer (#4013).
    • The FICON Express16S+ SX feature does not support autonegotiation to 1 or 2 Gbps. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
    • For unrepeated distances for FICON Express16S+ SX refer to Planning for Fiber Optic Links, GA23-1408 available in the Library section of Resource Link: http://www.ibm.com/servers/resourcelink
    • Both ports of the adapter need to be defined as either FC or FCP CHPIDs. A mix of FC and FCP CHPIDs on the same adapter is not supported.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0431) IBM zHyperLink Express

(No longer available as of April 10, 2018)

IBM zHyperLink Express is a short distance, IBM ZB. I/O adapter which works in conjunction with a FICON SAN infrastructure. This feature is a 2 port adapter which resides in the3906 PCIe I/O drawer and supports direct connectivity to FICON storage systems at distances up to 150m.

  • Minimum: 0.
  • Maximum: 16 (32 ports).
  • Prerequisites: PCIe I/O drawer (#4013).
  • Corequisites: FICON connectivity to each storage system connected via zHyperLinks.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: 150m max distance in a point to point configuration.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied 24x MTP-MTP cable is required for each port of the zHyperLink Express feature. It is single 24-fiber cable with Multi-fiber Termination Push-on (MTP) connectors. Internally, the single cable houses 12 fibers for transmit and 12 fibers for receive. Two fiber type options are available with specifications supporting different distances for the zHyperLink Express:-- 150m: OM4 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 4.7 GHz-km @ 850 nm.-- 100m: OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2.0 GHz-km @ 850 nm.
(#0604) IBM Virtual Flash Memory (VFM)

Provides up to 6.0 TB of virtual flash memory in 1.5 TB increments. Virtual Flash Memory is a replacement for zFlash Express memory.

  • Minimum: 0.
  • Maximum: 4. VFM memory ordered reduces the maximum orderable memory for the model.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#0848) 32GB USB Backup Media

An optional feature which will provide additional backup coverage for configurations which require additional coverage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None Known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
(#0879) TKE 9.0 LIC

The Trusted Key Entry (TKE) 9.0 level of Licensed Internal Code (LIC) is installed in a TKE workstation (#0085 or 0086). TKE 9.0 LIC is a no-charge enablement feature which is loaded prior to shipment when a TKE workstation is ordered. The TKE 9.0 LIC includes support for the Smart Card Reader (#0891).

  • Minimum: 0.
  • Maximum: 10.
  • Prerequisites: TKE workstation (#0085 or 0086).
  • Corequisites: CPACF (#3863) or Crypto Express6S (#0893).
  • Compatibility Conflicts: TKE workstations with TKE 9.0 LIC can also be used to control LinuxONE Emperor and LinuxONE Rockhopper servers.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
(#0891) TKE Smart Card Reader

The TKE Smart Card Reader feature supports the use of smart cards, which resemble a credit card in size and shape, but contain an embedded microprocessor, and associated memory for data storage. Access to and the use of confidential data on the smart cards is protected by a user-defined Personal Identification Number (PIN). This feature is optional when used with the TKE workstation to manage a Crypto Express6S feature that is defined as a Common Cryptographic Architecture (CCA) coprocessor. This feature is required when used with the TKE workstation to manage a Crypto Express6S feature that is defined as an IBM Enterprise PKCS #11 (EP11) coprocessor.

The TKE 9.0 level of LIC (#0879) allows the storing of the following on smart cards:

  • CCA master and operational key parts.
  • Crypto Adapter Logon keys - keys used to sign onto the TKE workstation when using smart card profiles.
  • Authority Signature Key - key associated with an authority index on a Crypto Express feature.
  • EP11 master key material and administrator certificates.
  • Migration zones - used in the process of migrating data from one feature to another.

One (1) feature includes two Smart Card Readers, two cables to connect to the TKE 9.0 workstation, and 20 smart cards.

  • Minimum: 0.
  • Maximum: 20.
  • Prerequisites: CP Assist for Cryptographic Function (#3863) or Crypto Express6S (#0893 or 0890).
  • Corequisites: TKE workstation (# 0085 or 0086) with 9.0 level of LIC (#0879) for secure key parts entry and Crypto hardware management or ISPF panels for clear key entry and Crypto hardware management. If EP11 is to be defined, smart cards used require FIPS certification.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: None. External cables to connect two Smart Card Readers to the TKE workstation are shipped with the feature.
(#0893) Crypto Express6S

The Crypto Express6S feature is designed to satisfy IBM Z and IBM LinuxONE server security requirements. It contains one PCIe adapter which can be configured as a coprocessor supporting secure key transactions or as an accelerator for Secure Sockets Layer (SSL) operations. This feature can be configured, via the Service Element (SE) panels, in one of three ways: as an IBM Common Cryptographic Architecture (CCA) coprocessor, as an IBM Enterprise PKCS #11 (EP11) coprocessor, or as an accelerator. The tamper-resistant hardware security module, which is contained on the Crypto Express6S feature, is designed to conform to the Federal Information Processing Standard (FIPS) 140-2 Level 4 Certification. It supports User Defined Extension (UDX) services to implement cryptographic functions and algorithms (when defined as an IBM CCA coprocessor).

  • Minimum: None or two. An initial order is two features, one thereafter.
  • Maximum: 16.
  • Prerequisites: CP Assist for Cryptographic Function (CPACF) (#3863).
  • Corequisites: TKE workstation (# 0085 or 0086) is optional when used to manage a Crypto Express6S feature that is defined as a CCA coprocessor in normal mode, but is mandatory when used to manage a Crypto Express6S feature that is defined as a CCA coprocessor in PCI-HSM mode or that is defined as an EP11 coprocessor (CCA in PCI-HSM mode and EP11 also require a smartcard reader plus smart cards with FIPS certification).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Can not ship as a loose piece MES to China.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: None.
(#1021) STP enablement

Time synchronization and time accuracy: If you require time synchronization across multiple servers or you require time accuracy for one or more IBM Z or IBM LinuxONE servers or you require the same time across heterogeneous platforms (IBM Z, Unix, AIX, etc) you can meet these requirements by implementing Server Time Protocol (STP). Server Time Protocol is a server-wide facility that is implemented in the Licensed Internal Code (LIC) and presents a single view of time to Processor Resource/Systems Manager (PR/SM).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Delivered in vital product data (VPD) enablement media. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#1750) Licensed Internal Code (LIC) ship using Net Indicator

This indicator flag is added to orders that are Licensed Internal Code (LIC) only and delivered by web tools. No hardware is shipped. The flag is generated by the system and is not orderable.

(#1929) Central Processor 4 (CP4)

Processor Unit characterization option. The CP4 is the Processor Unit purchased and activated supporting the z/VM, Linux on z Systems and KVM on IBM Z operating systems on Emperor II. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: None known. Field Installable: Yes.

(#1933) Integrated Facility for Linux (IFL)

Processor Unit characterization option. The IFL is a Processor Unit that is purchased and activated for exclusive use of Linux on z Systems.

  • Minimum: 0.
  • Maximum: 170.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1935) System Assist Processor (SAP), optional

Processor Unit characterization option. The purpose of the SAP feature is to designate Processor Units to be used specifically for assisting I/O operations. The optional SAP is a Processor Unit that is purchased and activated for use as a SAP. This optional SAP is a chargeable feature.

  • Minimum: 0.
  • Maximum: 16.
  • Prerequisites: One CP4 (#1929) or IFL (#1933).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1937) Unassigned Integrated Facility for Linux (IFL)

Processor Unit characterization option. An unassigned IFL is a Processor Unit purchased for future use as an IFL (#1933). It is offline and available for use.

  • Minimum: 0.
  • Maximum: 169.
  • Prerequisites: One CP4 (#1929) or IFL (#1933).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1990) 32GB PrePlanned Memory

Preplanned Memory provides the ability to plan for non-disruptive memory upgrades. The hardware required is pre-plugged based on a target capacity specified by the customer. This pre-plugged hardware will be enabled via a LICCC order placed by the customer when he has determined additional memory capacity is needed.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#1999) 64GB IBM Virtual Flash Memory PrePlanned Memory

VFM Preplanned Memory provides the ability to plan for a disruptive CPC drawer outage. The hardware required is pre-plugged based on a target capacity calculated by the configurator only when flexible memory has been selected (only if Flex memory is disabled).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Flexible memory option.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature removals become the property of IBM.
  • Cable Order: None.
(#2000) Line cord plan ahead

This option provides the ability to plan ahead for the second set of line cords. Must be same feature selection as initial set. The Plan Ahead function provides the means of ordering now, the hardware that will be required in the future to help avoid a disruptive hardware install in the future.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Line cords must be same feature selection as initial set.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: No.
(#3003) Balanced Power Plan Ahead

Phase currents are minimized when they are balanced among the three input phases. Balanced Power Plan Ahead is designed to allow you to order the full complement of bulk power regulators (BPRs) on any configuration, to help ensure that the configuration will be in a balanced power environment.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: May require additional internal battery features (#3216) and line cords. Configuration tool will determine. Second set of line cords is a corequisite.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. It is disruptive.
  • Cable Order: None.
(#3103) Universal lift tool upgr kit

This feature, with FC 3759, supplies new rails to permit CPC drawers to slide in/out of the IBM Emperor II frame.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: #3759.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3105) Universal lift tool/ladder

This feature supplies the full kit required for the service of IBM Emperor II systems. It includes new rails to permit CPC drawers to slide in/out of the IBM Emperor II frame.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. One #3105 is required per site. Two #3105 are recommended for larger sites. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3216) Internal Battery (IBF)

The IBF is the internal battery backup feature offered on IBM Emperor II. When selected, the actual number of IBFs is determined based on the power requirements and model. The batteries are installed in pairs.

  • Minimum: 0 or one pair.
  • Maximum: Three pairs.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
  • Cable Order: None.
(#3379) Fill and Drain adapter kit

This feature supplies new hose attachments which are required with FC 3378 for the service of IBM Emperor II systems.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: #3378.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3380) Fill and Drain kit

This feature supplies the full fill and drain kit required for the service of IBM Emperor II systems. It includes the hose adapters/fittings required for connection of a IBM Emperor II.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. One #3380 is required per site. Two #3380 are recommended for larger sites. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3863) CP Assist for Cryptographic Function (CPACF) enablement

CPACF, supporting clear and protected key encryption, is activated using the no-charge enablement feature (#3863). It offers the following:

  • For data privacy and confidentially: Data Encryption Standard (DES), Triple Data Encryption Standard (TDES), Advanced Encryption Standard (AES) for 128-bit, 192-bit and 256-bit keys.
  • For data integrity: Secure Hash Algorithm-1 (SHA-1) 160-bit, and SHA-2 for 224-, 256-, 384-and 512-bit support. SHA-3 for 224-, 256- 384-, 512 bit support, and SHAKE for 128-, and 256 bit support. SHA-1, SHA-2 and SHA3 are shipped enabled on all IBM Emperor II 's and do not require the no-charge enablement feature.
  • For Key Generation: Pseudo Random Number Generation (PRNG), Deterministic Random Number Generation (DRNG), and True Random number generation (TRNG).
  • New Emperor II CPACF instructions for SHA-3 hashing, TRNG (True Random NumberGeneration), and Improved performance of AES GCM encryption.

For new servers, shipped from the factory, CPACF enablement (#3863) is loaded prior to shipment. For other than new shipments, Licensed Internal Code is shipped on media. The function is enabled using the Support Element (SE).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisite: Crypto Express6S (#0893).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#4013) PCIe I/O drawer

The Peripheral Component Interconnect Express (PCIe) I/O drawer is a physical resource used to house I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), and compression (zEDC Express). The PCIe I/O drawer contains 32 I/O slots; 16 I/O slots in the front and 16 I/O slots in the rear. The number of PCIe I/O drawers is automatically determined by the number of Crypto Express6S, FICON Express16S+, OSA-Express6S, RoCE Express2, or zEDC Express features ordered.

  • Minimum: 0.
  • Maximum: 5.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables for I/O features are a customer responsibility.
(#4029) A Frame - Radiator

Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None known. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. Cable Order: None.

(#4030) A Frame - Water

Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None known. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. Cable Order: None.

(#6096) Flat-panel display

The display offers the benefits of a flat-panel monitor including improved use of space and reduced energy consumption compared to CRT monitors. Minimum: 0. Maximum: Ten (10). Prerequisites: HMC #0082 or TKE #0086. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes. Parts removed as a result of feature conversion become the property of IBM. Cable Order: None.

(#6805) Additional CBU Test

An additional test activation that can be purchased with each CBU temporary entitlement record. There can be no more than 15 tests per CBU TER.Minimum: 0. Maximum: 15 per each instance of #6818, Capacity back up, CBU. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes.

(#6817) Capacity back up (CBU) years

Used to set the expiration date of a Capacity back up (CBU) temporary entitlement record. Minimum: 0. Maximum: Five (5). Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: Not applicable. Limitations: None. Field Installable: Yes.

(#6818) Capacity back up (CBU) records ordered

This feature code corresponds to the number of different CBU Temporary Entitlement Records (TERs) ordered. Each CBU TER contains configuration data corresponding to the number of years, number of tests, and various engine types. Minimum: 0. Maximum: Eight (8) per ordering session. Prerequisites: None. Corequisites: CBU Authorization (#9910). Compatibility Conflicts: None known. Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated. Limitations: None. Field Installable: Yes.

(#6822) Single CBU IFL Year

Pricing feature equal to the number of CBU years multiplied by the number of temporary IFL features, if less than 25 or the remainder after dividing by 25.Minimum: 0. Maximum: 24. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes.

(#6823) 25 CBU IFL-Year

Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary IFL features divided by 25. Minimum: 0. Maximum: 250. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes.

(#6830) Single CBU SAP-Year

Pricing feature equal to the number of CBU years multiplied by the number of temporary SAP features, if less than 25 or the remainder after dividing by 25.Minimum: 0. Maximum: 24. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes. (#6831) 25 CBU SAP-Year: Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary System Assist Processor (SAP) features divided by 25. Minimum: 0. Maximum: 250. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes.

(#6832) CBU Replenishment

This feature is used to restore the ability to activate a CBU TER. Each CBU TER comes with a default of one activation. An activation enables the resources required for disaster recovery. After an activation, no subsequent activations nor any additional testing of this CBU TER can occur until this feature is ordered. Minimum: 0. Maximum: 1. Prerequisites: Capacity back up (#6818). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes.

(#6833) Capacity for Planned Event (CPE)

This feature code corresponds to the number of different CPE Temporary Entitlement Records (TERs) ordered.Minimum: 0. Maximum: Eight (8) per ordering session. Prerequisites: None. Corequisites: CPE authorization (#9912). Compatibility Conflicts: None known. Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated. Limitations: None. Field Installable: Yes. (#7801) 14ft Water hoses: This feature supplies the water hose required for water cooled systems. It is supplied when ordering water cooled features #1028, #1029, #1030, #1031, or #1032. Minimum: 0. Maximum: 1. Prerequisites: #1028, #1029, #1030, #1031, or #1032. Corequisites: None. Compatibility Conflicts: None. Customer Setup: No. Limitations: #7801 is mutually exclusive with non-raised floor option #7998. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. Cable Order: None.

(#7923, #7924, #7925, #7926) Fiber Quick Connect

The Fiber Quick Connect (FQC) features, bracket and mounting hardware (#7923) and LC Duplex 6.6 feet (2 meter) harnesses (#7924), are optional features for factory installation of the IBM Fiber Transport System (FTS) fiber harnesses for connection to FICON LX adapters (#0409, #0418 or #0427) in a PCIe I/O drawer. FQC is offered on a frame-roll so the cabling is pre-plugged for carry forward cards. Fiber Quick Connect is for factory installation only, and is available on new servers and on initial upgrades to IBM Emperor II. FQC is not available as an MES to an existing IBM Emperor II. Each direct-attach fiber harness connects to six FICON LX channels at one end and one coupler in a multi-terminated push-on connector (MTP) coupler bracket at the opposite end.

When FQC is ordered, the configuration tool selects the required number of MTP mounting brackets and mounting hardware based upon the FICON LX feature quantity.

Note: FQC supports all of the FICON LX adapters. FQC cannot be ordered for selected channels.

(#7942) Top exit I/O cabling

When top exit I/O cabling is selected on an order, the required infrastructure is provided. Frame extensions are added to each corner of the system with this option. Routing of cabling from I/O drawers or PCIe I/O drawers will exit out the top of the frame (either the "A" or the "Z" frame). Top exit I/O cabling applies to all of your fiber optic cables (FICON Express and OSA-Express) as well as your copper cables for the OSA-Express 1000BASE-T Ethernet features.

Top exit I/O cabling is designed to provide you with an additional option. Instead of all of your cabling exiting under the server and/or under the raised floor, you now have the flexibility to choose the option that best meets the requirements of your data center. Top exit I/O cabling can also help to increase air flow.

In a raised floor environment, if Top exit I/O cabling (#7942) is selected, the power cord selection can be top exit or bottom exit. In a non-raised floor environment, if Top exit I/O cabling is selected then a top exit I/O power cord must also be selected as these are co-requisites with the non-raised floor option (#7998).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Cannot coexist with side covers (#7949).
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cabling is a customer responsibility.
(#7949) Side covers

Supplies a set of 2 side covers required for IBM Emperor II. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: Mutually exclusive with #7942 and #7998. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. Cable Order: None.

(#7998) Non-Raised Floor Support

Minimum: 0. Maximum: 1. (for a two-frame system) Corequisites: Top exit I/O cabling (#7942) and a top exit power cord. Limitations: Water cooling is mutually exclusive with the non-raised floor support (#7998). Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.

(#8003) 4-in-1 Bolt Down Kit

This feature applies to a raised-floor environment. This feature supplies the kit of parts that is designed to help secure the frames and their contents from damage when exposed to vibrations and shocks such as those in a seismic event. The kit includes hardware to cover all four floor depth options, 6 to 9 inches (15 to 23 cm), 9 to 13 inches (23 to 33 cm) 12 to 22 inches (30 to 56 cm), and 12 to 36 inches (30 to 91 cm).

  • Minimum: 0.
  • Maximum: 1. (for a two-frame system)
  • Prerequisites: None.
  • Corequisites: A Frame Radiator (4029).
  • Compatibility Conflicts: Mutually exclusive with features 7998, 8004 and 8005.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8004) 3 in1 Bolt Down Kit-W

This feature applies to a raised-floor environment. This feature supplies the kit of parts that is designed to help secure the frames and their contents from damage when exposed to vibrations and shocks such as those in a seismic event. The kit includes hardware to cover all three floor depth options, 9 to 13 inches (23 to 33 cm) 12 to 22 inches (30 to 56 cm), and 12 to 36 inches (30 to 91 cm).

  • Minimum: 0.
  • Maximum: 1 (for a two-frame system).
  • Prerequisites: None.
  • Corequisites: A Frame Water (4030).
  • Compatibility Conflicts: Mutually exclusive with features 7998, 8003 and 8005.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8005) Bolt-Down Kit, non-raised floor (NRF)

This feature supplies the kit of parts that are designed to help secure the frames and its contents from damage when exposed to vibrations and shocks such as those in a seismic event.

  • Minimum: 0.
  • Maximum: 1 (for a two-frame system).
  • Corequisites: A Fr Radiator (#4029 and Non-raised floor support (#7998).
  • Compatibility Conflicts: Mutually exclusive with features 8003 and 8004.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#9896) On/Off CoD Authorization

This feature is ordered to enable the ordering of On/Off Capacity on Demand (On/Off CoD) through Resource Link. Minimum: 0. Maximum: 1. Prerequisites: On-Line Capacity on Demand (#9900). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: Not applicable. Limitations: None. Field Installable: Yes.

(#9898) Permanent Upgrade authorization

This feature is ordered to enable the ordering of Licensed Internal Code Configuration Control (LICCC) enabled, permanent capacity upgrades through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: On-Line Capacity on Demand (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9900) On-Line Capacity on Demand (CoD) Buying

This feature is ordered to enable purchasing either permanent capacity upgrades or temporary capacity upgrades through Resource Link. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: Not applicable. Limitations: None. Field Installable: Yes.

(#9910) CBU Authorization

This feature enables the purchase of Capacity back up (CBU). This feature is generated when Capacity back up (#6818) is ordered, or it can be ordered by itself. This feature along with On Line Capacity on Demand (#9900) is required to order CBU through Resource Link.Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: Capacity back up (#6818). Compatibility Conflicts: None known. Field Installable: Yes.

(#9912) CPE Authorization

This feature is ordered to enable the purchase of Capacity for Planned Event (CPE). This feature is generated when Capacity for Planned Event (#6833) is ordered. This feature along with On Line Capacity on Demand (#9900) is required to order CPE through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9917) 1 MSU-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Central Processor (CP) resource tokens purchased through Resource Link. Million Service Unit (MSU)

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9918) 100 MSU-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 MSU-day (#9917).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9919) 10,000 MSU-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 MSU-day (#9917), 100 MSU-days (#9918).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9920) 1 IFL-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Integrated Facility for Linux (IFL) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9921) 100 IFL-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary IFL resource tokens purchased through Resource Link.

  • Minimum: 0
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 IFL-day (#9920).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9928) 1 SAP-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary System Assist Processor (SAP) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9929) 100 SAP-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary SAP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 SAP-day (#9928).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9970) Weight distribution kit

The weight distribution plate is designed to distribute the weight of a frame over two floor panels in a raised-floor installation and to eliminate a highly concentrated load on a single floor panel.

Certain configuration racks can weigh up to 2450 pounds per frame. The concentrated load on a caster or a leveling foot can be half of the total frame weight. For a multiple-system installation, it is possible that one floor panel could have two casters from two adjacent systems on it, and potentially induce a highly concentrated load onto a single floor panel.

Customers are responsible for consulting with the floor tile manufacturer to determine the load rating of the floor tile and the pedestal structure supporting the floor tiles.

Depending on the type of raised floors and the floor panels, additional panel supports (pedestals) may be required to restore or improve the structural integrity of the panel.

Note: Cable cutouts on a floor panel will significantly reduce the floor tile load rating.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Mutually exclusive with # 7998.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#9975) Height reduction for shipping

This feature is required if it is necessary to reduce the shipping height of the IBM Emperor II. This feature should be selected only when it has been deemed necessary for delivery clearance purposes. It should be ordered only IF ABSOLUTELY essential. This feature elongates the install time and increases the risk of cabling errors during the install activity.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: To ship the return packaging and instructions, one or both feature codes Height reduction for shipping (#9975), Frame height reduction for return (#9976), must be selected.
  • Compatibility Conflicts: None known.
(#9976) Frame height reduction for return

This feature is for zEC12 (MT 2827) or z13 (MT 2964) servers which need to be returned or relocated. The frame height reduction provides the tools and instructions to reduce the height of a zEC12 or a z13 when returned to IBM or when the zEC12 or z13 is relocated.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: To ship the return packaging and instructions, one or both feature codes Height reduction for shipping (#9975), Frame height reduction for return (#9976), must be selected.
  • Compatibility Conflicts: None known.

Back to topBack to top
 
Accessories

Not applicable.

Customer replacement parts

Not applicable.
Back to topBack to top
 

Supplies

Not applicable.

Supplemental media

Not applicable.

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
 © IBM Corporation 2018.
Back to topBack to top

Contact IBM

Feedback