IBM PCIe3 CAPI Flash Accelerator Adapter (FC EJ16; CCIN 2CE5)
Adapter Microcode and Software Libraries
version 4.1-2369-a7aaed6 (4.1.160512D1)
DATE: April 25, 2017
Table of Contents
1.0 General Information
1.1 Microcode Change History
2.0 Linux Operating System
2.1 RedHat
2.2 Ubuntu
2.3 SLES
3.0 Software Update
This provides software support and adapter updates for the EJ16 PCIe3 CAPI Flash Accelerator Adapter.
|
Release date |
Code level |
Adapter Microcode (AFU Version) |
Change Description |
|
April 2017 |
4.1-2369-a7aaed6 |
4.1.160512D1 |
Impact: Function Severity: ATT - User space software updates on Ubuntu and RHEL - Arkdb performance enhancements |
|
December 2016 |
4.0-2228-04c7743 |
160512D1 |
- User space software updates on Ubuntu and RHEL |
|
June 2016 |
2.1-1951-d654a81 |
160512D1 |
- Stability and bug fixes for adapter microcode - Improved user space application error handling - Ubuntu 16.04 support |
|
October 2015 |
2.0-1777-1a1ce61 |
150930D1 |
- Enable persistent storage modes (physical LUN addressing) - Enable multipathing - Support for multiple LUNs - Improve error handling - Enable cxlflash kernel module support - Requires 4096 byte formatted LUNs |
|
June 2015 |
1.0-1048-d0feb68 |
141208D7 |
- Debian installations are non-interactive to facilitate headless deployment - Enable systemd support - Improve loopback diagnostic functionality - Improve error handling when simultaneous link failures occur on both fibre channel ports |
|
January 2015 |
1.0-1032-a6fe159 |
141208D1 |
- Bug fix for arkdb error handling on memory allocation failures - No adapter microcode change from previous |
|
December 2014 |
1.0-1028-f5e3b0b |
141208D1 |
Initial Release |
This package consists of a tarball of rpm packages and a configuration and installation script.
· cflash_configure - Installation and configuration validation tool for both adapter microcode and user space software
· cxlflash.rpm - Support applications for the IBM Data Engine for NoSQL User Libraries
· cxlflashimage.rpm - Adapter microcode
· Linux kernel 3.10.0-514.el7.ppc64le or newer is required, as this kernel includes the cxlflash driver for feature code EJ16. This package is incompatible with earlier kernel versions.
This package consists of a tarball of debian packages and a configuration and installation script:
· cflash_configure - Installation and configuration validation tool for both adapter microcode and user space software
· cxlflash.deb - Support applications for the IBM Data Engine for NoSQL User Libraries
· cxlflashimage.deb - Adapter microcode
· Linux kernel 4.4.0-36.55 or newer is required, as this kernel includes the cxlflash driver for feature code EJ16. This package is incompatible with earlier kernel versions.
This package is incompatible with SLES.
Prerequisites:
· The IBM Advanced Toolchain for PowerLinux 10.0 is required. For additional information, refer to the Advanced Toolchain documentation.
· Platform Firmware FW860.10 or OP820.10
Determine if this package is applicable:
1. Check the adapter microcode level using “cflash_version.” If /opt/ibm/capikv/bin/cflash_version is not installed, install this package. If cflash_version states that a newer version is required, install this package.
user@system:~$ sudo /opt/ibm/capikv/bin/cflash_version
INFO: cxlflash: 4.1-2369-a7aaed6
INFO: 0004:01:00.0 101404cf 160512D1
2. If the contents of /opt/ibm/capikv/bin/version.txt is different from “2369-a7aaed6” or if this file is missing, install this update.
Packages must be installed as a set. New accelerator images will not take effect until a reload of the adapter occurs (see below) or the operating system is rebooted.
1. Untar the package
mkdir /tmp/pkg
cp EJ16-4.1-2369-a7aaed6.tgz /tmp/pkg
cd /tmp/pkg
tar -xzvf EJ16-4.1-2369-a7aaed6.tgz
2. Run “cflash_configure” to begin the install, reload, and validation process. Accept the license agreement, if applicable.
user@system:/tmp/pkg$ ./cflash_configure
...
INSTALL success
INFO: cxlflash: 4.1-2369-a7aaed6
INFO: 0040:01:00.0 101404cf 160512D1
INFO: Installed Versions....OK
3. Check for error messages or a non-zero return code. If a failure has occurred during installation, retry the installation or contact IBM Support with a copy of the output from installation.