PCIe2 2-Port 16Gb FC Adapter 

******* PLEASE READ THIS ENTIRE NOTICE *********

DATE: February 8, 2021

Table of Contents

 

 

1.0 Microcode and Document Revision History:

2.0 General information

3.0 Installation time

4.0 Machine's Affected:

5.0 Linux Requirements:

6.0 AIX Requirements:

7.0 Determine the Current Microcode Level

7.1 AIX Systems:

7.2 Linux Systems:

8.0 Downloading the RPM Format File to the Target Server

8.1 Downloading AIX RPM Package

8.2 Downloading Linux RPM Package

9.0 Discovery Tool Microcode CD-ROM creation and download instructions

10.0 Verifying microcode before download and notes

10.1 Verifying microcode before download for AIX

10.2 Verifying microcode before download for Linux

11.0 Microcode Download Procedure for AIX:

11.1 Setting up for Microcode download

11.2 Downloading Microcode to the Adapter

11.3 Verify and Re-configure adapters

12.0 Microcode Download Procedure for Linux using Emulex hbacmd utility

12.1 Download One Command Manager

12.2 Download Code to Adapter

12.3 Download Code to Adapter for Ubuntu

 

1.0 Microcode and Document Revision History:
 

Microcode Level

Changes

00012000040025700030

 

Impact: Usability   Severity: ATT

* Fix open-dev leaving extra item on stack resulting in failed boot

 

* Fix fcp-targets did not return target ports for IBMi direct attach resulting in failed boot

The Firmware Levels Below Are No Longer Supported By IBM Once They Have Been Removed From The Microcode Down Load Website.

It is best practices to update to the latest FW level not only for IBM support of these products, but for optimal performance and to ensure that all of the required HW/FW fixes are installed. Please Update To The Latest Level At Your Earliest Convenience

 

00012000040025700027

 

* Fix fcode stack imbalance

00012000040025700015

 

*Fixed Memory Address Not Aligned issue caused by FLOGI retry loop. Initial partition boot may fail with one of the following reference codes: BA210001, BA218001, BA210003, or BA218003.

 

*livedump fix for when data frame is jammed with PARA = FFFFFFF

*Fix Intermittent boot failures with direct attach

*Long link down after setting board_mode online fix

*PRLI failure for direct attach fix

*Fix for ‘Setportspeed’ settings (8G/16G adapter) negotiates to ‘auto’ speed when forced to 2Gb

*Provide interlock between FLOGI and ACQE error fix

*Fix for [linux] VF driver receiving incorrect PVID immediately after correct PVID.

 

*This level of firmware supports the Firmware Secure Boot feature of Power systems

 

00011000040041500010

 

 

Impact: Usability   Severity: ATT

Fix for the following:

*Scanning adapter in SMS when direct attached to V7000 takes over 2 minutes

*Fatal error state after some Admin WQE failures

*This level of firmware supports the Firmware Secure Boot feature of Power systems

*Adapter EEH error because status frame sent incorrectly.

*Feature to disable an unsupported function (FEC) on 16G Optical link as it was in all releases prior FW 11.2.211.21. This prevents the link from sometimes coming up as 8G.

00011000020021100031

This fw level was not released to Fix Central but may have been included in adapter shipments to customer as part of an ifix. Newer released fw will include this fix.
*ifix fw for the following:
Fixed speed negotiation issue where link came up at 8G instead of 16G.
This ifix fw disabled an unsupported function (FEC) on 16G Optical, to prevent the link from sometimes coming up as 8G.

00011000020021100021

 

* adapter has an intermittent issue where reading NIC fcode returns 00

* FCode memory leak in fibre channel driver

* adapter with FW 11.1.35.67 failing NIM install

* Direct Attach LinkUp Issue with DS8K array. FEC set to off on both sides to work.

* Add data scrubbing to adapter FW dump process to remove/obscure user data

* Customer reporting spontaneous dump on FCoE adapter running 10.2.252.1921 fw

* FC adapter intermittently aborts active I/Os after Accepted REC

* VIOS crashed when lpar was booted into Sles

00010000020025201919

* Fixed an intermittent issue of Link not coming up after reboot with Cisco switch.

* Fixed FC Tape class 3 error recovery

* Fixed performance scaling when using IBM Flash system 900

00010000020025201905

 

*Fix for SRIOV mode, adapter went to error state when config VNIC.

*Fix for SRIOV VF TX timeouts when other VFs are FLR

*Fix for SRIOV VNIC ping failure when injecting EEH errors.

*Fix for spontaneous livedump with adapter entered error state (9F000013,00001007)

*Fix a rogue frame with EoFa and a bad length, seen during switch reboots.

*Fix an inbound class 2 FLOGI rejected with non-retryable invalid class of service

00010000020025200016

 

*Fix for SRIOV race conditions in PCI Function Reset

*Fix for Outbound Jammer test (Dropped outbound data frame of single frame sequence)

*Fix IO fail to resume after f/w update on FCoE

*Fix DMA to 0 in an IBMi system

*Fix for SRIOV hard LPAR shutdowns

00010000020025200009

 

* FC Adapter Port Error on ISL pull

* P_RJT response for Fibre Channel Class 2 ELS's

* Reboot FCoE adapter path recovery failure - mailbox error and fcs unknown error

* FC adapter does not indicate closed exchange when WQE with LNK bit set fails (fw ignores early closure of exchange for linked scsi commands)

* Experiencing NIM install issues with adapters                            

* DCBX Get Config Mailbox Cmd timing out. Fix Link bounces  

* Unable to set pause Flow control when connected to DCBX switch with PFC off

* GRP5 Link COS ACQE needs to be delivered on DCBX/PFC change

* AIX issues BA_RJT with reason code "Protocol Error" to target-Initiated ABTS

00001000010005800004

 

*Exchanges aborted after REC is successfully ACC'd by target device.

*COMMON_GET_FLOW_CONTROL issues in dedicated mode

*No link after cable plugged in

*VIOS disk path does not recover from Initiator port cable pull

*Adapter pport stat counter TX_BROADCAST_BYTES incorrect

*Logging in and out of fabric

 

00001000010003400005

*Adapter livedump following CRC forced errors.

*Fcode fix of SAN boot LPAR stuck at LED AA00E158

*No link after cable plugged in.

*Failed paths to SAN after a switch reboot.

0001000010003400003

This is the level of microcode that initially shipped with the adapter when it became generally available.

 

Document Revision History

Description

02/08/2021

Updated readme file for 12.4.257.30 firmware release.

11/17/2020

Updated readme file for 12.4.257.27 firmware release.

2/10/2020

Updated readme file for 12.4.257.15 firmware release.

1/24/2019

Added ifix fw 00011000020021100031 to history list of unsupported fw.

9/13/2018

Update to level 00011000040041500010

1/19/2018

Update to level 00011000020021100021

6/15/2016

Update to level 00010000020025201919

5/5/2016

Added 2 Feature codes EL43 and EL5B

1/7/2016

Update to level 00010000020025201905

6/18/2015

Update to level 00010000020025200016

11/14/2014

Update to level 00010000020025200009

05/22/2014

Update readme file with level 00001000010005800004

05/27/2013

Update readme file with level 00001000010003400005

02/28/2013

Creating Readme file with latest microcode for this adapter - df1000e21410f103


2.0 General information

This Readme file is intended to give directions on how to update the microcode found on the PCIe2 2-Port 16Gb FC Adapter (FC: EN0A and EN0B, EL43 and EL5B ).

 

 

3.0 Installation time

Approximately 20 minutes.

 

 

4.0 Machine's Affected: 

Feature Code EN0A ( Full Height ), EN0B ( Low Profile )

Linux Feature Codes EL5B ( Full Height ), EL43 ( Low Profile ) 

CCIN 577F

 

 

           Cautions and Important Notes

 

·    Concurrent Download

The microcode installation supports concurrent download while the adapter and attached storage devices are available for use. HOWEVER, it is recommended that installation be scheduled during a maintenance window or during non-peak production periods.

 

·    AIX Diag and Standalone Diag CD

For FW 11.4.415.10 or higher, AIX APAR IJ08893 is required before running AIX Diag.

Please also use the latest September 2018 AIX Standalone Diagnostics CD found here http://www14.software.ibm.com/webapp/set2/sas/f/diags2/download/home.html

 

 

5.0 Linux Requirements:

Basic card function is supported on:

•  Red Hat Enterprise Linux 6.4 for POWER®, or later

•  SUSE Linux Enterprise Server 11 Service Pack 2, or later.

 

Download drivers link:

https://www.broadcom.com/support/download

 

 

6.0 AIX Requirements:

Basic card function is supported on:

·       AIX Version 7.1 with the 7100-02 Technology Level, or later

·       AIX Version 7.1 with the 7100-01 Technology Level and Service Pack 6, or later

·       AIX Version 7.1 with the 7100-00 Technology Level and Service Pack 8, or later

·       AIX Version 6.1 with the 6100-08 Technology Level, or later

·       AIX Version 6.1 with the 6100-07 Technology Level and Service Pack 6, or later

·       AIX Version 6.1 with the 6100-06 Technology Level and Service Pack 10, or later

If you are using another release of AIX, ensure that the adapter is supported on that release before you install the adapter. Contact service and support for assistance.

 

Important Notice:  EEH error entries in AIX system errlog are expected when updating adapter FW.

 

 

7.0 Determine the Current Microcode Level

7.1 AIX Systems:

Before you install the microcode, it is important to determine the microcode level of the Adapter installed in the target system. Use the following instructions to read the ROM level stored in the Adapter's VPD.

1)  List the Fiber Channel adapters or Ethernet adapters installed in the system by typing:

     # lscfg -l fcs\*

Note: All of the Fiber Channel and Ethernet adapter ports that are installed will be displayed. They will be listed as fcsX and entX, where X is 0, 1, etc.

2) To check the current microcode level for the adapter or controller enter the following command

    # lsmcode -cd fcsx <Where “x” is the instance of the adapter>

 

The command will produce output similar to:

The current microcode level for fcs0 is 00011000040041500027

 

If the ROM Level is less than 00012000040025700030 you should update the microcode.

 

7.2 Linux Systems:

The following steps are for Linux Red Hat or SuSE systems running 2.6 kernels which support the /sys filesystem. These steps assume you are logged in with root permissions and one or more PCIe2 16Gb 2-Port Fibre Channel Adapters, Feature Code EN0A or EN0B are installed.

1) Display the model description for each installed Fibre Channel adapter. Expect two instances of PCIe2 16Gb 2-Port Fibre Channel Adapters to be displayed; one for each port on the dual port adapter. Type the following commands to display a list showing the host{n}: description for each installed adapter.

# cd /sys/class/scsi_host; find -L host* -maxdepth 1 -name "modeldesc" -printf %h: -exec cat {} \;

The output will be similar to that shown here. The host{n} values will be used in the next step. If the list is empty, either there are no adapters installed or there was an error in typing the command. If the list contains other adapters but no 16Gb 2-Port FC adapters are listed, none are installed, and this firmware update should not be applied.

host2: IBM xxxP/Nxxx PCIe2 16Gb 2-Port Fibre Channel Adapter
host3: IBM xxxP/Nxxx PCIe2 16Gb 2-Port Fibre Channel Adapter

2) Display the firmware version for each adapter. Type the following command, replacing host{n} with the value reported for each adapter listed in Step 1.

# cat host{n}/fwrev

The microcode version listed may vary but output will be similar to that shown here, four numbers separated with “.”, sli-4:2:b:

11.4.415.10, sli-4:2:b

Repeat this command for each  host{n}. If one or more adapter lists a microcode version that is not 12.4.257.30, then the microcode update should be applied.

3) Display Linux Operating System version. Type the following command to display the Operating System version. Make a note of Operating System version, it will be needed later.

For Red Hat systems, type the following command.

 

# cat /etc/redhat-release

 

Output will be similar to:
Red Hat Enterprise Linux Server release 7.4

 

For SuSE systems, type the following command. Output will be similar to:

 

# cat /etc/SuSE-release

 

SUSE Linux Enterprise Server 12 (ppc64)

VERSION = 12

PATCHLEVEL = 3

 

 

8.0 Downloading the RPM Format File to the Target Server

8.1 Downloading AIX RPM Package

Use this method to download to an AIX system:

 

NOTE: The instructions that follow are specific AIX commands. AIX commands are CASE (lower and upper) SENSITIVE, and must be entered exactly as shown, including filenames.

 

1) Make two directories on your AIX system to receive the RPM format file.
    Enter:      "mkdir /tmp/microcode"

    and then create this directory

    Enter:      "mkdir /tmp/microcode/RPM"

 

2) Transfer the RPM format file to the /tmp/microcode/RPM directory (using "Save as ...").  Change to that directory, "cd /tmp/microcode/RPM".

You'll see the filename for the RPM file.
       "rpm -ihv --ignoreos df1000e21410f103.00012000040025700030.aix.rpm"

3) For AIX:  The microcode files will be added to /etc/microcode/.

 

NOTE:
 - "/etc/microcode" is a symbolic link to "/usr/lib/microcode".
 - If permission does not allow the copy to the above stated directory or file then the user will be prompted for a new location.

 

8.2 Downloading Linux RPM Package

Follow these steps to install the Linux RPM package on a Linux system. Note that the Linux commands are case sensitive and must be entered exactly as shown, including file names.

1) Transfer the Linux rpm file, df1000e21410f103.00012000040025700030.grp.Linux.rpm, to a temporary directory on the target server such as /tmp.

2) Unpack the rpm file by typing:

# rpm -ihv /tmp/df1000e21410f103.00012000040025700030.grp.Linux.rpm

 

3) The microcode package extracts the firmware file to the /lib/firmware directory. If a message is displayed saying the "package <package_name> is already installed", you will need to uninstall the rpm package.

 

On the command line type: rpm -e <package_name>

 

where <package_name> is the name of the package that was returned in the message. Return to Step 2 and attempt to unpack the file again.

 

4) Verify the microcode image in Section 10.2

 

 

9.0 Discovery Tool Microcode CD-ROM creation and download instructions

To obtain information how to burn a CD-ROM and run the Discovery Tool for an AIX or Linux System please go to: http://www14.software.ibm.com/support/customercare/mds/

1) After running the Discovery Tool successfully, the "/tmp/microcode/RPM" directory was created, and your rpm files are copied from the CD-ROM.

 

2) Change to that directory, "cd /tmp/microcode/RPM".

3) Unpack the file by executing the instructions below:
    Enter the commands:
    # rpm -ihv --ignoreos df1000e21410f103.00012000040025700030.aix.rpm

4) One microcode file will be copied to "/etc/microcode".              
               File Name: df1000e21410f103.00012000040025700030

NOTE:
 - "/etc/microcode" is a symbolic link to "/usr/lib/microcode".
 - If permission does not allow the copy to the above stated directory or file then the user will be prompted for a new location.

 

10.0 Verifying microcode before download and notes

10.1 Verifying microcode before download for AIX

Please verify the file size and checksum of the raw microcode files matches what is listed below.

Please verify the file size and checksum

# ls -l df1000e21410f103.00012000040025700030

Expected file size: 11274612

 

# sum df1000e21410f103.00012000040025700030

Expected checksum: 27266 11011

 

10.2 Verifying microcode before download for Linux

Please verify the file location, size and checksum of the raw microcode files matches what is listed below.

 

Please verify the file size and checksum

# ls -l df1000e21410f103.00012000040025700030.grp

Expected file size: 11274612

 

# sum df1000e21410f103.00012000040025700030.grp

Expected checksum: 27266 11011

 

 

11.0 Microcode Download Procedure for AIX: 

Microcode download must be performed separately for each Adapter under each Logical Partitions (LPAR's).

11.1 Setting up for Microcode download

1) Stop all applications that use this interface/adapter

2) You only need to pick one of the fcs# per adapter for microcode update. Diag will update microcode for all ports

 

11.2 Downloading Microcode to the Adapter

1) At the command line type “diag

2) Select the "Task Selection" from diagnostics menu.

3) Select "Microcode Tasks” then select “Download Microcode" from the menu.

4) Select all of the PCIe2 2-port 16Gb FC Adapters that need to be updated from the list of devices by using the arrow keys to highlight the entry and pressing "Enter" to mark it.  The devices will be displayed as fcs#, where # is the number of the device.  Press "F7" when you are done marking all the adapters you want to flash.

5) If a source selection menu is displayed, Select “/etc/microcode”.

6) A dialogue box may be displayed on screen.  It will state that the current microcode level on the adapter is not in the /etc/microcode directory.  This is acceptable because the adapter will reject any incorrect code.  Press "Enter" to continue.

7) Select 00012000040025700030 level and press "Enter" to flash the adapter.

8) The following message will appear on the screen when download is completed: "Microcode download complete successfully.  The current microcode level ……   Please run diagnostics on the adapter to ensure that it is functioning properly."

9) If you selected more than one adapter to update, then steps 6-9 will repeat until all adapters are updated.

10) Exit diagnostics.

11.3 Verify and Re-configure adapters

1) Verify the code level is 00012000040025700030 by typing "lsmcode -cd fcs#" for each Fiber Channel or Ethernet adapter updated. <Where # is the instance of the adapter>

 

2) Re-configure/Verify the adapter’s information through the “smit” menus if necessary.

 

# lscfg -vl fcs1

fcs1   U2C4B.001.DBJ2970-P2-C6-T2  PCIe2 2-Port 16Gb FC Adapter (df1000e21410f103)

 

        Part Number.................00E3495

        Serial Number...............1A22700026

        EC Level....................D77535

        Customer Card ID Number.....577F

        Manufacturer................001A

        FRU Number..................00E3496

        Device Specific.(ZM).........3

        ROM Level.(alterable)....100300

        Network Address.............10000090FA0203E2

        Device Specific.(Z0)........0000000D

        Device Specific.(Z1)........00000030

        Device Specific.(Z2)........00000000

        Device Specific.(Z3)........08090000

        Device Specific.(Z4)........01000001

        Device Specific.(Z5)........ZE323537

        Device Specific.(Z6)........ZE323537

        Device Specific.(Z7)........C0022B40

        Device Specific.(Z8)........20000090FA0203E2

        Device Specific.(Z9)........12.4.257.30

        Device Specific.(ZA)........12.4.257.30

        Device Specific.(ZB)........00000000

        Device Specific.(ZC)........00040000

        Device Specific.(ZD)........000000FF

        Hardware Location Code......U2C4B.001.DBJ2970-P2-C6-T2

 

 

12.0 Microcode Download Procedure for Linux using Emulex hbacmd utility

Microcode download must be performed separately for each Adapter under each Logical Partitions (LPAR's).

 

12.1 Download One Command Manager

Microcode updates on Fibre Channel adapters installed in a Linux system require the use of the Emulex hbacmd utility. The hbacmd utility is included in the Emulex One Command CLI Applications Kit downloads web page located at:

 

https://www.broadcom.com/support/download-search

 

Group: Storage Adapters, Controllers, and ICs

Family: Fibre Channel Host Bus Adapters

OEM: IBM

Product: All

Asset type: All

Keyword: PowerPC

Select “Management Software and Tools”

 

For purpose of updating the microcode, One Command Manager (CLI) will be used. Select the Application Kit {version} (CLI) link. 

When prompted, save the Application Kit a directory of your choice on the target server.

Complete the requested user registration information, then select Download Driver button.

When prompted, save the elxcmcore-xxxx-xxxx-x.x.x.x-x.tgz file to a temporary directory, /tmp or you may save to directory of your choice.

Change directory to the directory where you have saved the elxcmcore-xxxx-xxxx-x.x.x.x-x.tgz archive.

Unpack the tgz archive, by typing:

# tar xzf elxcmcore-xxxx-xxxx-x.x.x.x-x.tgz

Change directory to elxocmcore-xxxx-xxxx-x.x.x.x-x and install the utility, by typing:
# ./install.sh

Answer questions as prompted using descriptive information provided as a guide.

Display the utility version to verify the hbacmd command is functional by typing: /usr/sbin/ocmanager/hbacmd version
Utility component version information should be displayed

Ensure that all I/O activity to storage devices controlled by the adapter is stopped prior to proceeding with firmware update as the adapter will be reset after firmware update.

12.2 Download Code to Adapter

List installed Emulex adapters by typing: /usr/sbin/hbacmd listhbas

Output from this command will be similar to the following, repeated one section for each discovered adapter. Adapters can be identified by looking for e200 in Flags value. For each adapter, make a note of the Port WWN: value. The Port WWN values will be required as an argument for commands in next steps.
 

Port WWN             : 10:00:00:10:9b:40:7c:8f

Node WWN           : 20:00:00:10:9b:40:7c:8f

Fabric Name          : 00:00:00:00:00:00:00:00

Flags                      : 8000e200

Host Name             : host.ibm.com

Mfg                        : Emulex Corporation

Serial No.              : 1A82000674

Port Number          : 0

Mode                     : Initiator

PCI Bus Number   : 80

PCI Function         : 0

Port Type               : FC

Model                    : 00E3495

 

List hba attributes for each adapter listed in the above step, Type /usr/sbin/hbacmd hbaattributes {wwpn}, where {wwpn} is one of the port WWPN values.

 

The output will look similar to the following and will list current versions of FW Version, SLI2 FW, SLI3 FW as well as Boot Code, all of which will be updated by microcode update. Save current operational firmware values for comparison post update.

HBA Attributes for               10:00:00:10:9b:40:7c:8f

 

Host Name                            : host.ibm.com

Manufacturer                        : Emulex Corporation

Serial Number                      : 1A82000674

Model                                   : 00E3495

Model Desc                          : IBM 00E3495 PCIe2 16Gb 2-Port Fibre Channel Adapter

Node WWN                          : 20 00 00 10 9b 40 7c 8f

Node Symname                    :

HW Version                         : 0000000d

FW Version                          : 12.4.257.12

Vendor Spec ID                    : 10DF

Number of Ports                   : 1

Driver Name                         : lpfc

Driver Version                      : 12.0.0.10; HBAAPI(I) v2.3.d, 07-12-10

Device ID                             : E200

HBA Type                            : 00E3495

Operational FW                    : 12.4.257.12

IEEE Address                       : 00 10 9b 40 7c 8f

Boot Code                            : Enabled

Boot Version                        : 12.4.257.12

Board Temperature              : Normal

Function Type                      : FC

Sub Device ID                      : 03F1

PCI Bus Number                  : 80

PCI Func Number                : 0

Sub Vendor ID                     : 1014

IPL Filename                        : HL2LP3

Service Proc FW Name        : 12.4.257.12

ULP FW Name                     : 12.4.257.12

FC Universal BIOS Version : 12.4.257.12

FC x86 BIOS Version          : 12.4.257.6

FC EFI BIOS Version          : 12.4.215.0

FC FCODE Version             : 12.4.257.12

Flash Firmware Version       : 12.4.257.12

 

Update microcode on one port per adapter. This step assumes that microcode image .rpm package has been installed on system as described in section 8.2.

Warning: Do not interrupt or power off the system while microcode update(s) are in progress.

Start microcode update on one adapter port, type: /usr/sbin/hbacmd download {wwpn} /lib/firmware/df1000e21410f103.00012000040025700030.grp

 

               <Where {wwpn} is one of the port WWN values of adapter.>

 

Completion of download will be indicated by “Download Complete.” message.

System must be rebooted for firmware to be loaded.  Reboot system

 

After system reboot, check firmware version as described in Section 7.2 or using: /usr/sbin/hbacmd hbaattributes {wwpn} as above for each port.

If, firmware version is not the version you are expecting, carefully retrace steps for omissions and examine console output for errors.  Contact IBM support if you need further assistance.