PCIe3 16Gb 4-Port FC Adapter

 

PCIe3 Low Profile 16Gb 4-Port FC Adapter

 

 

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

 

DATE: April 19, 2021

 

 

Contents

 

 

1.0 Overview.. 1

2.0 Adapters Affected. 1

3.0 Microcode Description and Revision History. 1

4.0 Cautions and Important Notes. 1

5.0 To Determine Adapter Microcode Levels. 1

5.1 AIX Systems. 1

5.2 Linux Systems. 1

6.0 Install RPM Package. 1

6.1 AIX RPM Package. 1

6.2 Linux RPM Package. 1

7.0 Installing the Adapter's Microcode. 1

7.1 Using the AIX Command-Line Method. 1

7.2 Using the Diagnostic Service Aid Method. 1

7.3 Using the Marvell QConvergeConsole CLI Method. 1

8.0 Verifying the Update. 1

8.1 Verifying the Update on AIX. 1

8.2 Verifying the Update on Linux. 1

Document Change History. 1

 

 

 

----------------------------------------------------------------------------------

1.0 Overview

 

This update contains the AIX RPM file for the current level of microcode for the 16Gb PCIe3 4-Port FC Adapter, Feature Code(s) EN1E and EN1F.

 

This is a multi-port adapter with two identical ASICs. Each ASIC controls two ports so only a single resource (port) needs to be updated per ASIC.

 

 

 

----------------------------------------------------------------------------------

2.0 Adapters Affected

 

This microcode is for feature codes EN1E ( High Profile ) and EN1F ( Low Profile ).

 

CCIN: 579A

 

To determine the part number of the adapter on an AIX system, on the command line key the following command:

 

#lscfg -l fcsX  (where fcsX represents the adapter)

 

Affected adapters will be listed as:

PCIe3 4-Port 16Gb FC Adapter (7710712014109e06)

 

To determine the presence of this adapter on a Linux system, on the command line key in:

 

# ls /sys/class/fc_host

 

Example output: host1 host2 host3 host4

 

Next determine the model description and name for each host. For each host{n} displayed in previous command, on the command line key in the following command,where host{n} is replaced by one of hosts listed in previous step:

 

# cat /sys/class/scsi_host/host{n}/model*

 

 

The typical time to install the microcode is 0.4 hr.

 

 

----------------------------------------------------------------------------------

3.0 Microcode Description and Revision History

 

Microcode Level

Changes

7710712014109e06.070006

This is the level of microcode that is initially supported when it became generally available.

 

 

 

----------------------------------------------------------------------------------

4.0 Cautions and Important Notes

 

·       Concurrent Download - The microcode installation does NOT support concurrent download while the fcs resources are available for use. If the fcs resources are in use, they must manually be released prior to starting the download. Failure to do so will result in a message instructing that the fcs resource be freed.

 

NOTE: It is recommended that the installation be scheduled during a maintenance window or during non-peak production periods.

 

 

 

----------------------------------------------------------------------------------

5.0 To Determine Adapter Microcode Levels

 

Before installing the microcode, it is important to determine the current microcode level of the adapter.

 

5.1 AIX Systems

 

1.    List the Fibre Channel (FC) adapters installed in the system by typing on the command line:

 

# lsdev -C | grep fcsX

 

Note the device names of all the fibre channel adapters installed. The adapter device names will be fcsX, where X is 0,1,2,3 or some other number. There will be an fcsX listing for each port of the FC EN1E or EN1F adapter

 

2.    Determine the current microcode level on the adapter by typing on the command line:

 

# lsmcode -d fcsX   (where X is the number of the adapter's port returned from the "lsdev" command above.)

 

A screen similar to the following will be displayed:

 

DISPLAY MICROCODE LEVEL

fcs0              PCIe3 4-Port 16Gb FC Adapter (7710712014109e06)

 

The current microcode level for fcs0

is 070006.

 

Use Enter to continue.

 

F3=Cancel            F10=Exit             Enter

 

 

 

If the current microcode level is not 070006 (as shown in the ‘lsmcode’ output’) then the microcode image on the adapter is not at the latest level.

 

5.2 Linux Systems

 

1.    Download and Install the latest QConvergeConsole CLI package from the Marvell Driver Download site: http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/IBM_Search.aspx

 

*** NOTE: For Ubuntu, you must convert rpm to deb for ubuntu with the "alien" utility. ***

If you do not already have alien installed you will need to first, get alien:

 

#apt-get install alien

           

Then use alien to convert rpm to deb format.

#alien -d QConvergeConsoleCLI-2.2.00-15.ppc64le.rpm --scripts -k  <change the package name to match the package name you downloaded>

                        NOTE: the scripts flag is important. It is needed to pull in the correct libraries for the tool.

 

 

2.    Verify firmware version running on the host.

 

# qaucli

 

In the first ‘menu’ pick “1: Adapter Information

If the “Firmware Version” version reported is not 7.00.06, then the microcode image on the adapter is not at the latest level.

 

 

 

----------------------------------------------------------------------------------

6.0 Install RPM Package

 

6.1 AIX RPM Package

 

Use this method to install the AIX RPM package on an AIX system.

 

Note that the commands are case sensitive and must be entered exactly as shown, including file names. Installing the RPM places the binary file 7710712014109e06.070006 in the /etc/microcode directory.

 

1.     If the /etc/microcode directory does not exist, make a directory to receive the RPM format file. On the command line type:

 

# mkdir /etc/microcode

 

2.     Transfer the RPM format file, 7710712014109e06.070006.aix.rpm to any temporary directory on the target system.

 

3.     Unpack the file. On the command line type:

 

# rpm -ihv --ignoreos 7710712014109e06.070006.aix.rpm

 

4.     If the microcode package unpacks successfully, the microcode file will be added to the /etc/microcode directory.

 

If a message is received 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 3 and attempt to unpack the file again.

 

5.     Verify the file size and sum of the 7710712014109e06.070006 file in /etc/microcode. On the command line type:

 

For the file size:

 

# ls -al 7710712014109e06.070006

 

For the sum:

 

# sum 7710712014109e06.070006

 

The output of these commands should be:

file size: 882920

sum: 35198 863

 

 

 

6.2 Linux RPM Package

 

Use this method 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 path names.

 

1.    Transfer the Linux rpm file, 7710712014109e06.070006.Linux.rpm, to a directory on the target system, /tmp is used in this example.

 

2.    Unpack the rpm file. On the command line type :

 

# rpm -ihv --ignoreos /tmp/7710712014109e06.070006.Linux.rpm

 

If the microcode package unpacks successfully, the microcode file will be added to the/lib/firmware directory.

 

3.    If a message is displayed indicating 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 file size and sum of the 7710712014109e06.070006 file in /lib/firmware directory. On the command line type:

 

For the file size:2

 

# ls -al /lib/firmware/7710712014109e06.070006

 

For the sum:

 

# sum /lib/firmware/7710712014109e06.070006

 

The output of these commands should be:

file size: 882920

sum: 35198 863

 

 

 

----------------------------------------------------------------------------------

7.0 Installing the Adapter's Microcod

 

7.1 Using the AIX Command-Line Method

 

Login as root user. From the command line key in:

 

# diag -d fcsX -T download

 

where fcsX is the port you on which you want to install the microcode.

Self-explanatory menus will step you through the microcode installation.

 

*** Repeat the above steps for at least one of the ports in the second pair. ***

 

7.2 Using the Diagnostic Service Aid Method

 

Login as root user.

From the command line key in: diag

Select: Task Selection (Diagnostics, Advanced Diagnostics, Service Aids, etc.)

Select: Microcode Tasks

Select: Download Latest Available Microcode

Select: file system /etc/microcode

Select the device: fcs*

 

Press enter when prompted to download the microcode.

 

Upon completion, a message will state that the microcode has been successfully downloaded and that the new level is 070006.

7.3 Using the Marvell QConvergeConsole CLI Method

 

The following steps assume you are logged on with root permissions,  you have the QConvergeConsole CLI already installed and you have at least one PCIe3 16Gb 4-Port FC Adapter , Feature Code EN1E or EN1F installed in the system.

 

If you do not have the QConvergeConsole CLI installed see section 5.2 for instructions.

 

From the command line launch the QConvergeConsole by typing the following:

 

# qaucli

 

From the first menu select “3: Adapter Updates

Next select “1: Flash Update

Select the adapter you wish to update and hit ‘enter’

 

You will be asked for the filename.

Type in /lib/firmware/7710712014109e06.070006 <or the level you are planning to update to> and hit ‘enter’

 

Next you will see the Update begin and complete.  The output will be similar to the following:

 

Updating Flash on HBA port(s) - QLE2964L. Please wait...

Flash update complete. Changes have been saved to the HBA port(s).

 

Press <Enter> to continue:

 

If you have more than 1 EN1E or EN1F adapter that needs to be updated, repeat the above steps for the remaining adapters.

 

----------------------------------------------------------------------------------

8.0 Verifying the Update

 

8.1 Verifying the Update on AIX

 

1.    List the Fibre Channel (FC) adapters installed in the system by typing on the command line:

 

# lsdev -C | grep fcsX

 

Note the device names of all the fibre channel adapters installed.

The adapter device names will be fcsX, where X is 0,1,2,3 or some other number.

There will be an fcsX listing for each port of the FC EN1E or EN1F adapter

 

2.    Determine the current microcode level on the adapter by typing on the command line:

 

# lsmcode -d fcsX  (where X is the number of the adapter's port returned from the "lsdev" command above.)

 

A screen similar to the following will be displayed:

 

DISPLAY MICROCODE LEVEL                                         

fcs0              PCIe3 4-Port 16Gb FC Adapter (7710712014109e06)

 

The current microcode level for fcs0 is 070006.

 

Use Enter to continue.

 

F3=Cancel            F10=Exit             Enter

 

 

If the current microcode level is 070006, then the microcode image was updated successfully.

 

Repeat above steps for remaining ports.

 

 

 

8.2 Verifying the Update on Linux

 

1.    Verify firmware version running on the host.

 

# qaucli

 

In the first ‘menu’ pick “1: Adapter Information” and then select one of the adapter ports.

 

Repeat above steps for remaining ports.

 

If the “Firmware Version” version reported is  7.00.06, then the microcode image on the adapter is at the latest level.

 

If version reported is not as expected, carefully retrace steps to confirm each step is completed without error.

 

 

 

----------------------------------------------------------------------------------

 Document Change History

Date

Change

4/20/2021

Initial Document

 

 

 

----------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------

Privacy(http://www.ibm.com/privacy) | Legal(http://www.ibm.com/legal) | Contact

IBM(http://www.ibm.com/contact)