PCIe4 2-Port 32Gb FC Adapter
******* PLEASE READ THIS ENTIRE NOTICE *********
DATE: December 13, 2024
Table of Contents
1.0 Microcode and Document
Revision History:
5.0 Cautions and
Important Notes
6.0 Determine the Current
Microcode Level
7.0 Downloading the RPM
Format File to the Target Server
7.1 Downloading AIX RPM
Package
7.2 Downloading Linux RPM
Package
8.0 Discovery Tool Microcode
CD-ROM creation and download instructions
9.0 Verifying microcode image
before download
10.0 Microcode Download
Procedure for AIX:
10.1 Setting up for Microcode
download
10.2 Downloading Microcode to
the Adapter
11.0 Microcode Download
Procedure for Linux using QConvergeConsole CLI utility
11.1 Download and Install
QConvergeConsole CLI
|
Microcode Level |
Changes |
|
7710812214105106.070120 |
Impact: Data Severity: HIPER *
Potential undetected data loss can occur on LPARs using NPIV with Fibre Channel. This issue
can occur when the LPAR boots or when one of the LPAR targets on the SAN is
removed. The port login process can cause login collisions, invalid MPIO
configurations, or potentially undetected data loss. |
|
The Firmware Levels Below Are No Longer Supported by IBM. 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 |
|
|
Microcode
Level |
Changes |
|
7710812214105106.07010C |
Impact:
Usability Severity: ATT *Boot from Tape enablement *PEP firmware fix for VPD not readable |
|
7710812214105106.07010B |
This is the level of microcode that is initially
supported when it became generally available. |
|
Document Revision History |
Description |
|
12/13/2024 |
Updated readme for 070120 Release |
This Readme file is intended to give directions on how to update the microcode found on the following adapters:
PCIe4 2-Port 32G FC Adapter (CCIN: 579C with FC: EN1J and EN1K)
· 7710812214105106
Approximately 20 minutes.
IBM Power
· Concurrent Download
The microcode installation supports concurrent download while the adapter and attached storage devices are available for use. HOWEVER, it is highly recommended that installation be scheduled during a maintenance window or during non-peak production periods.
· AIX Diag and Standalone Diag CD
Please also use the latest AIX Standalone Diagnostics CD found here https://www.ibm.com/support/pages/node/6474531
Important Notice:
· EEH error entries in AIX system errlog are expected when updating adapter FW.
· Quiesce loads on adapter doing updates or long timeouts may result.
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 in the system by typing:
# lscfg -l fcs*
Note: All of the Fiber
Channel ports that are installed will be displayed. They will be listed as fcsX, where X is 0, 1, etc. Locate the fcsX instances associated with the adapter planned for
update.
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 fcsX is 070120
If the ROM Level is less than 070120, you
should update the microcode.
To locate the correct QConvergeConsole CLI Search for the following:
· CATEGORY: Fibre Channel Adapters
· PLATFORM/OS: Linux
· KEYWORDS: PPC
To verify firmware version running on the adapter run: # qaucli
Select: “1: Adapter Information”
If the “Firmware Version” is not 070120, then the
microcode should be updated.
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 directories on your AIX system to receive the RPM format file.
"mkdir -p /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".
For PCIe4 2-Port 32G FC Adapter (CCIN: 579C with FC: EN1J and EN1K)
rpm -ihv –ignoreos 7710812214105106.070120.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.
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 to a temporary directory on the target server such as /tmp.
2) Change the current directory to the temporary directory.
3) Unpack the rpm file:
For PCIe4 2-Port 32G FC Adapter (CCIN: 579C with FC: EN1J and EN1K)
rpm -ihv –ignoreos 7710812214105106.070120.grp.rpm
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
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 rpm file/s by executing the
instructions as in the previous section.
Please verify the file size and checksum of the raw microcode files matches what is listed below:
Directory for AIX: /etc/microcode
Directory for LINUX: /lib/firmware
# ls -l 7710812214105106.070120
# sum 7710812214105106.070120
Expected file size: 1122424
Expected checksum: 33781 1097
Microcode download must be performed separately for each Adapter under each Logical Partitions (LPAR's).
1) Stop all applications that use this interface/adapter
2) You only need to pick one of the fcs#s per adapter for microcode update.
Diag will update microcode for all ports.
1) At the command line type “diag”
2) Select the "Task Selection (Diagnistics, Advanced Diagnostics, Service Aids, etc.)" from diagnostics menu.
3) Select "Microcode Tasks” then select “Download Latest Available Microcode" from the menu.
4) Select all the Fibre Channel Adapters that need to be updated from the list of devices
5) If a source selection menu is displayed, Select “/etc/microcode”.
The following message will appear on the screen when download is completed: "Installation `of the microcode has completed successfully on the following instances of the adapter: … The current microcode level …… Please run diagnostics on these resources to ensure that the adapter is functioning properly."
Check & verify the firmware version as described in Section 6.1
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.
Microcode download must be performed separately for each Adapter under each Logical Partitions (LPAR's).
Microcode updates on Fibre Channel adapters installed in a Linux system require the use of the “qaucli” utility. The “qaucli” utility is included in the QConvergeConsole CLI tool found on the Marvell Public Driver Downloads web page located at:
https://www.marvell.com/support/downloads.html
· CATEGORY: Fibre Channel Adapters
· PLATFORM/OS: Linux
· KEYWORDS: PPC
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.
Download the code to the adapter following the qaucli menus.
After reboot, check and verify firmware version as described in Section 6.2
If the 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.