PCIe2
10Gb Cu 4-Port FCoE Adapter
*******
PLEASE READ THIS ENTIRE NOTICE *********
DATE: June 7, 2017
Table of Contents
Contents
1.0
Microcode and Document Revision History:
7.0
Determine the Current Microcode Level:
8.0
Downloading the RPM Format File to the Target Server
8.1
AIX Use this method to download to an AIX
system:
9.0 Discovery Tool Microcode CD-ROM creation and
download instructions
10.0
Verifying microcode before download and notes
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:
12.1
Setting up for Microcode download
12.2
Downloading Microcode to the Adapter
|
Microcode Level |
Changes |
|
00010000020025201927 |
Impact: Usability Severity: ATT Fix for the following: * TX
stall causing back-pressure in the ASIC resulting in mailbox
response not being sent to host. * System Crash when LPAR was booted into SLES * Hardware Ethernet Error caused by a dead
lock in adapter FW. A mutex was taken and not
released by mistake. *
Adapter
enters firmware loop when single bit ECC error is detected. System * Fix direct-attach issue with DS8000 storage |
|
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. Once new FW has been released to the field, we will provide a
6 month grace period for customers to update these products to the currently
supported FW level . Please Update To The Latest
Level At Your Earliest Convenience |
|
|
00010000020025201913 |
Fixed an
intermittent issue Link not coming up after reboot with Cisco switch. |
|
00010000020025201905 |
*Fix for SRIOV mode, adapter went to error
state when config Vnic. *Fix for SRIOV VF TX timeouts when other VFs
are FLR – reseted. *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 * 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 |
Original release |
|
Document
Revision History |
Description |
|
04/22/2014 |
Creating Readme file
with latest microcode for this adapter - df1060e214103e04 level 00001000010005800004 |
|
11/14/2014 |
Update to level 00010000020025200009 |
|
6/5/2015 |
Update to level 00010000020025200016 |
|
9/24/2015 |
Update to level 00010000020025201905 |
|
5/16/2016 |
Update to level 00010000020025201913 |
|
6/7/2017 |
Update to level 00010000020025201927 |
This
Readme file is intended to give directions on how to update the microcode found
on the PCIe2 10Gb Cu 4-Port FCoE Adapter (FC: EN0K and EN0L ).
Also
Feature Codes: EL57 and EL3C.
Approximately 20 minutes.
NOTE: It is recommended that the installation be scheduled during a
maintenance window or during non-peak production periods.
Feature Codes EN0K,EL57 ( Full Height ), EN0L, EL3C ( Low
Profile )
CCIN 2CC1
·
Red Hat Enterprise Linux 6.4 for POWER® , or later
·
SUSE Linux Enterprise Server 11 Service Pack 2, or later, with current maintenance updates available
from SUSE to enable all planned functionality
Download drivers link:
http://www.emulex.com/downloads/emulex/drivers/linux/
Basic card
function is supported on :
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.
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\*
or:
lscfg -l ent\*
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
or:
lsmcode -cd entx
Where “x” is the instance
of the adapter. The command will produce output similar to:
The current microcode level for fcs0 is 00010000020025201927
If the ROM Level is
less than 00010000020025201927 you should update the microcode.
NOTE: The
instructions that follow are specific Linux commands. Linux commands are CASE (lower
and upper) SENSITIVE, and must be entered exactly as shown, including
filenames.
1) List the Ethernet interfaces for PCIe2 10Gb
Cu 4-Port FCoE Adapter adapters installed in the system by typing:
ifconfig
-a | grep eth
Note: All of the Ethernet
adapters that are installed will be displayed. They will be listed as eth{n},
where {n} is 0, 1, etc.
2) For each adapter listed,
use ethtool -i eth{n} to determine which Ethernet interfaces are associated
with the PCIe2 10Gb Cu 4-Port FCoE Adapter. If driver name is “be2net”, that
interface is for PCIe2 10Gb Cu 4-Port FCoE Adapter. For example:
ethtool
-i eth{n}
Where {n} is the instance
of the adapter. The command will produce output similar to:
ethtool -i eth1
driver: be2net
version: 2.102.426r
firmware version:
10.2.252.1927
bus-info: 0001:01:00.0
If driver name is “be2net”,
eth1 is one of PCIe2 10Gb 4-Port FCoE Adapter interfaces. firmware-version is
“10.2.252.1927”.
If firmware-version is not 10.2.252.1927
or higher, on any of the adapters listed with a be2net driver; you should
update the microcode
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 df1060e214103e04.00010000020025201927.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.
Use this method to download the new
microcode to a Linux system:
NOTE: The instructions that follow are
specific Linux commands. Linux commands are CASE (lower and upper) SENSITIVE,
and must be entered exactly as shown, including filenames.
1)
Transfer the RPM format file to the /tmp
directory(using “Save as....”). You will see the filename for the RPM file.
2)
Install rpm on your Linux system by typing:
rpm -ivh /tmp/df1060e214103e04.00010000020025201927.Linux.rpm
3) The microcode package will install the
firmware images in the /lib/firmware directory. If a message is displayed
saying the "package <package_name> is
already installed", you will need to uninstall the listed 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 install the file again.
4) The microcode file will be installed to the
/lib/firmware directory. File name：df1060e214103e04.00010000020025201927
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 df1060e214103e04.00010000020025201927.aix.rpm
4) One microcode file will
be copied to "/etc/microcode".
File Name: df1060e214103e04.00010000020025201927
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.
Please verify the file size
and checksum of the raw microcode files matches what is listed below.
For AIX :
Please verify the file size
and checksumsum
# ls -l df1060e214103e04.00010000020025201927
-rw-r--r-- 1
root system 10598028 July 24 00:14 df1060e214103e04.00010000020025201927
# sum df1060e214103e04.00010000020025201927
53087 10350 df1060e214103e04.00010000020025201927
ls -l
/lib/firmware/df1060e214103e04.00010000020025201927 to verify file size is
10598028
sum /lib/firmware/df1060e214103e04.00010000020025201927 to verify Checksum is
53087
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) Detach
the Adapter’s interface (not always needed, but it is a good practice to do
this step).
Before detaching the interface, record the ip address and any
other pertinent information that was configured on the Adapter. This information may be needed if the microcode
update overwrites this section on the Adapter.
Note: If NIC ports are used in SEA Shared Ethernet
Adapter, or EtherChannel. Detach and rmdev are needed:
ifconfig en#
detach
rmdev -Rl ent#
3) You only need to
pick one fcs# per adapter for microcode update. Diag will update microcode for
all ports.
Note: in step 3) you might need to perform “rmdev -Rl
fscsi# “ to remove child devices to the
fcs#. Fcs# needs to be Available for fw download.
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 10Gb Cu 4-Port FCoE 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 00010000020025201927 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."
Note: If NIC
ports are used as SEA Shared Ethernet Adapter, Don’t run diag after FW update
as stated in this step 8.
9) If you
selected more than one adapter to update, then steps 6-9 will repeat until all
adapters are updated.
10) Exit diagnostics.
1) Verify the code level is
00010000020025201927 by typing "lsmcode
-cd fcs#" or “lsmcode -cd ent#” 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 fcs4
fcs4 U78C9.001.WZS00AB-P1-C9-T1 PCIe2 10Gb Cu 4-Port FCoE Adapter
(df1060e214103e04)
Part Number.................00E8140
Serial Number...............1A30500B05
EC Level....................L38135
Customer Card ID Number.....2CC1
Manufacturer................001A
FRU Number..................00E8140
Network
Address.............10000090FA0235DE
Device Specific.(Z0)........0000000B
Device Specific.(Z1)........00000010
Device Specific.(Z2)........00000000
Device Specific.(Z3)........08090000
Device Specific.(Z4)........00003001
Device Specific.(Z5)........39393939
Device Specific.(Z6)........39393939
Device Specific.(Z7)........C0022B40
Device
Specific.(Z8)........20000090FA0235DE
Device
Specific.(Z9)........ 10.2.252.1927
Device Specific.(ZA)....... 10.2.252.1927
Device Specific.(ZB)........30313233
Device Specific.(ZC)........00040000
Device Specific.(ZD)........000000FF
Hardware Location
Code......U78C9.001.WZS00AB-P1-C9-T1
# lscfg -vl ent6
ent6 U78C9.001.WZS00AB-P1-C9-T1 PCIe2 10GbE SFP+ CU 4-port Converged Network
Adapter (df1020e214103d04)
PCIe2 4-port (10Gb FCoE &
1GbE) Copper&RJ45, NIC PF:
Part
Number.................00E8140
Serial
Number...............1A30500B05
EC
Level....................L38135
Customer Card ID
Number.....2CC1
Network Address.............0090FA0235DA
ROM
Level.(alterable).......10.2.252.1927
Hardware Location Code......U78C9.001.WZS00AB-P1-C9-T1
1)
Use this
series of Linux commands to determine which of any installed Network adapters
are PCIe2 10Gb Cu 4-Port FCoE Adapter:
for i in `ls /sys/class/net | grep
eth` ; do echo -n "${i}: "; ethtool -i ${i} | grep bus-info; done
Output
will display the association between eth{n} devices and PCI bus device numbers,
nnnn:nn:nn.n
Output
will list PCI bus device numbers for the PCIe2
10Gb Cu 4-Port FCoE Adapter functions, nn:nn.n
This
example shows the four ports of one PCIe2 10Gb Cu 4-Port FCoE
Adapter. Firmware need only be updated on
the first port of each adapter,
2)
Stop all
applications that use the interface/adapter to be updated
3)
Configure
the adapter’s interface, eth1 in this example.
1)
Using
the eth{n} configured in previous step use ethtool --flash to
update the firmware.
ethtool --flash eth{n} df1060e214103e04.00010000020025201927
For
example, dmesg command will show the following messages:
be2net
0000:01:00.0: Flashing firmware file df1060e214103e04.00010000020025201927
be2net 0000:01:00.0: System reboot required for new FW to be active
be2net 0000:01:00.0: Firmware flashed successfully
These
messages show flashing is completed successfully.
3)
Reboot
the OS instance to activate the updated firmware.
4)
Verify
firmware has been activated
Using
same eth{n} interface used for ethtool --flash
command, type: