Post new question
Question
Reply
 
Student
Posts: 1
Member Since: ‎07-28-2016
Message 1 of 1 (1,322 Views)

ConnectX-3 firmware update

Product Name: PSID: HP_0280210019
Operating System: Linux

Hello,

 

I'm installing MLNX_OFED_LINUX-3.1-1.0.3-rhel7.2-x86_64 on CentOS 7.2 machine.

Initially I used MLNX_OFED_LINUX-3.3-1.0.4.0-rhel7.2-x86_64 but it's conflicted with current kernel (3.10.0-327.22.2.el7.x86_64), so I'm using 3.1-1.0.3 version.

 

(1)

As you can see the following log ((e)&(f)), current firmware version is v2.33.5000 and v2.35.5100 is required.

 

"...The firmware for this device is not distributed inside Mellanox driver: 21:00.0 (PSID: HP_0280210019)
To obtain firmware for this device, please contact your HW vendor..."


How can I upgrade firmware of this ConnectX-3 card?

Using "PSID: HP_0280210019", I can't find the proper firmware from the Mellanox website.

Is there any way to get the right firmware for HP_0280210019 ConnectX-3 card?

 

(2)

I'm installing same OFED on two machines with same environments (same ConnectX-3 card, cables, and OS).

In the (e) log, at least, each VPI is recognized as "UP 1X QDR (Ethernet)".

But, in the (f) log, all VPI are shown as "DOWN (Ethernet)".

Is there anything I should check?

 

Thank you in advance for any help!

 

 

-----

 

(a)

# cat /etc/redhat-release

CentOS Linux release 7.2.1511 (Core)

# uname -a

Linux xxx 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

 

(b)

// I'm using only the first port among 2 ports.

# cat /etc/modprobe.d/mlx4_core.conf

options mlx4_core port_type_array=2,2 num_vfs=8,0,0 probe_vf=8,0,0  log_num_mgm_entry_size=-1

 

(c)

# ./mlnxofedinstall --enable-sriov

...
The 3.10.0-327.22.2.el7.x86_64 kernel is installed, MLNX_OFED does not have drivers available for this kernel.
You can run mlnx_add_kernel_support.sh in order to to generate an MLNX_OFED package with drivers for this kernel.

Installation finished successfully.

Preparing... ################################# [100%]
Updating / installing...
   1:mlnx-fw-updater-3.1-1.0.3 ################################# [100%]

Added 'RUN_FW_UPDATER_ONBOOT=no to /etc/infiniband/openib.conf

Attempting to perform Firmware update...
Note: Will burn SR-IOV enabled firmware only for ConnctX3 devices.
To configure SR-IOV for other devices, please use the 'mlxconfig' or 'mstconfig' utility.

The firmware for this device is not distributed inside Mellanox driver: 21:00.0 (PSID: HP_0280210019)
To obtain firmware for this device, please contact your HW vendor.

Failed to update Firmware.
See /tmp/MLNX_OFED_LINUX-3.1-1.0.3.23105.logs/fw_update.log

WARNING: Original /etc/infiniband/openib.conf saved as /etc/infiniband/openib.conf.rpmsave
To load the new driver, run:
/etc/init.d/openibd restart

 

(d)

# lspci -nn | grep Mella

21:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003]

21:00.1 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.2 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.3 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.4 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.5 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.6 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:00.7 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

21:01.0 Network controller [0280]: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] [15b3:1004]

 

 

(e)

# hca_self_test.ofed

 

---- Performing Adapter Device Self Test ----

Number of CAs Detected ................. 9

PCI Device Check ....................... PASS

Kernel Arch ............................ x86_64

Host Driver Version .................... MLNX_OFED_LINUX-3.1-1.0.3 (OFED-3.1-1.0.3): modules

Host Driver RPM Check .................. PASS

Firmware on CA #0 VPI .................. v2.33.5000

Firmware Check on CA #0 (VPI) .......... FAIL

    REASON: mismatch CA #0 firmware detected (found v2.33.5000, required v2.35.5100)

Firmware on CA #1 VPI .................. v2.33.5000

Firmware Check on CA #1 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #2 VPI .................. v2.33.5000

Firmware Check on CA #2 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #3 VPI .................. v2.33.5000

Firmware Check on CA #3 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #4 VPI .................. v2.33.5000

Firmware Check on CA #4 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #5 VPI .................. v2.33.5000

Firmware Check on CA #5 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #6 VPI .................. v2.33.5000

Firmware Check on CA #6 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #7 VPI .................. v2.33.5000

Firmware Check on CA #7 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #8 VPI .................. v2.33.5000

Firmware Check on CA #8 (VPI) .......... NA

    REASON: NO required fw version

Host Driver Initialization ............. PASS

Number of CA Ports Active .............. 9

Port State of Port #1 on CA #0 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #2 on CA #0 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #1 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #2 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #3 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #4 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #5 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #6 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #7 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #1 on CA #8 (VPI)..... UP 1X QDR (Ethernet)

Error Counter Check on CA #0 (VPI)...... NA (Eth ports)

Error Counter Check on CA #1 (VPI)...... PASS

Error Counter Check on CA #2 (VPI)...... PASS

Error Counter Check on CA #3 (VPI)...... PASS

Error Counter Check on CA #4 (VPI)...... PASS

Error Counter Check on CA #5 (VPI)...... PASS

Error Counter Check on CA #6 (VPI)...... PASS

Error Counter Check on CA #7 (VPI)...... PASS

Error Counter Check on CA #8 (VPI)...... PASS

Kernel Syslog Check .................... PASS

Node GUID on CA #0 (VPI) ............... 00:02:c9:03:00:f6:ef:f0

Node GUID on CA #1 (VPI) ............... 00:14:05:00:d3:a2:8c:35

Node GUID on CA #2 (VPI) ............... 00:14:05:00:e5:c0:e2:a1

Node GUID on CA #3 (VPI) ............... 00:14:05:00:d5:e0:c2:1a

Node GUID on CA #4 (VPI) ............... 00:14:05:00:ca:34:61:56

Node GUID on CA #5 (VPI) ............... 00:14:05:00:08:0d:34:72

Node GUID on CA #6 (VPI) ............... 00:14:05:00:ba:43:bd:b4

Node GUID on CA #7 (VPI) ............... 00:14:05:00:d6:4f:7f:80

Node GUID on CA #8 (VPI) ............... 00:14:05:00:2a:aa:5f:08

------------------ DONE ---------------------

 

(f)

 

# hca_self_test.ofed

 

---- Performing Adapter Device Self Test ----

Number of CAs Detected ................. 9

PCI Device Check ....................... PASS

Kernel Arch ............................ x86_64

Host Driver Version .................... MLNX_OFED_LINUX-3.1-1.0.3 (OFED-3.1-1.0.3): modules

Host Driver RPM Check .................. PASS

Firmware on CA #0 VPI .................. v2.33.5000

Firmware Check on CA #0 (VPI) .......... FAIL

    REASON: mismatch CA #0 firmware detected (found v2.33.5000, required v2.35.5100)

Firmware on CA #1 VPI .................. v2.33.5000

Firmware Check on CA #1 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #2 VPI .................. v2.33.5000

Firmware Check on CA #2 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #3 VPI .................. v2.33.5000

Firmware Check on CA #3 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #4 VPI .................. v2.33.5000

Firmware Check on CA #4 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #5 VPI .................. v2.33.5000

Firmware Check on CA #5 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #6 VPI .................. v2.33.5000

Firmware Check on CA #6 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #7 VPI .................. v2.33.5000

Firmware Check on CA #7 (VPI) .......... NA

    REASON: NO required fw version

Firmware on CA #8 VPI .................. v2.33.5000

Firmware Check on CA #8 (VPI) .......... NA

    REASON: NO required fw version

Host Driver Initialization ............. PASS

Number of CA Ports Active .............. 1

Port State of Port #1 on CA #0 (VPI)..... UP 1X QDR (Ethernet)

Port State of Port #2 on CA #0 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #1 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #2 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #3 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #4 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #5 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #6 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #7 (VPI)..... DOWN (Ethernet)

Port State of Port #1 on CA #8 (VPI)..... DOWN (Ethernet)

Error Counter Check on CA #0 (VPI)...... NA (Eth ports)

Error Counter Check on CA #1 (VPI)...... PASS

Error Counter Check on CA #2 (VPI)...... PASS

Error Counter Check on CA #3 (VPI)...... PASS

Error Counter Check on CA #4 (VPI)...... PASS

Error Counter Check on CA #5 (VPI)...... PASS

Error Counter Check on CA #6 (VPI)...... PASS

Error Counter Check on CA #7 (VPI)...... PASS

Error Counter Check on CA #8 (VPI)...... PASS

Kernel Syslog Check .................... PASS

Node GUID on CA #0 (VPI) ............... 24:be:05:ff:ff:82:04:70

Node GUID on CA #1 (VPI) ............... 00:14:05:00:74:9d:d3:e8

Node GUID on CA #2 (VPI) ............... 00:14:05:00:5b:d6:c8:5c

Node GUID on CA #3 (VPI) ............... 00:14:05:00:91:15:4c:6f

Node GUID on CA #4 (VPI) ............... 00:14:05:00:f4:f1:03:95

Node GUID on CA #5 (VPI) ............... 00:14:05:00:01:b5:af:22

Node GUID on CA #6 (VPI) ............... 00:14:05:00:d4:12:58:1e

Node GUID on CA #7 (VPI) ............... 00:14:05:00:d4:4c:ca:e8

Node GUID on CA #8 (VPI) ............... 00:14:05:00:72:14:6c:52

------------------ DONE ---------------------

Reply
0
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation