"Burning FS2 image failed: Device/Image mismatch: FW image file cannot be programmed to device ConnectX-3Pro, it is intended for: ConnectX-3 A1 only"
What needs to be done ?
Mellanox SX6012, HP 544+ QSFP+ and 40GBASE-LR4 modules
- Thread starter Matta
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
What needs to be done ?
I think your card might have a non standard logic lane to SERDES mapping as compared to the stock mellanox card.
Dump the original HP firmware config and post the logic lane to Serdes mapping
It looks something like this:
Dump the original HP firmware config and post the logic lane to Serdes mapping
Bash:
flint -d mt4099_pciconf0 dc orig_firmware.ini
Code:
;;Logic lane to Serdes mapping
tx_logic_0_serdes = 0
tx_logic_1_serdes = 1
tx_logic_2_serdes = 2
tx_logic_3_serdes = 3
rx_logic_0_serdes = 3
rx_logic_1_serdes = 2
rx_logic_2_serdes = 1
rx_logic_3_serdes = 0
tx_logic_4_serdes = 4
tx_logic_5_serdes = 5
tx_logic_6_serdes = 6
tx_logic_7_serdes = 7
rx_logic_4_serdes = 7
rx_logic_5_serdes = 6
rx_logic_6_serdes = 5
rx_logic_7_serdes = 4
eth_tx_lane_polarity_port1 = 0xf
eth_tx_lane_polarity_port2 = 0xf
eth_rx_lane_polarity_port1 = 0x0
eth_rx_lane_polarity_port2 = 0xf
tx_lane_polarity_port1 = 0xf
tx_lane_polarity_port2 = 0xf
Code:
;;Logic lane to Serdes mapping
rx_logic_0_serdes = 3
rx_logic_1_serdes = 2
rx_logic_2_serdes = 1
rx_logic_3_serdes = 0
tx_logic_0_serdes = 0
tx_logic_1_serdes = 1
tx_logic_2_serdes = 2
tx_logic_3_serdes = 3
rx_logic_4_serdes = 7
rx_logic_5_serdes = 6
rx_logic_6_serdes = 5
rx_logic_7_serdes = 4
tx_logic_4_serdes = 4
tx_logic_5_serdes = 5
tx_logic_6_serdes = 6
tx_logic_7_serdes = 7
eth_rx_lane_polarity_port1 = 0x0
eth_tx_lane_polarity_port1 = 0xF
rx_lane_polarity_port1 = 0x0
tx_lane_polarity_port1 = 0xF
eth_rx_lane_polarity_port2 = 0xF
eth_tx_lane_polarity_port2 = 0xF
rx_lane_polarity_port2 = 0xF
tx_lane_polarity_port2 = 0xFThe SERDES mapping in my previous post was from a ConnectX-3 MCX354A, so I can't say for certain it will be that same mapping for the CX-3 Pro. I'd flash the stock mellanox firmware, dump the config for the mellanox firmware and compare both firmware config files for differences.
If the logic lane to SERDES mapping is different, you'd need to figure out how to edit the firmware config and upload it back onto the card.
This thread is on a different problem, but contains some information on editing + merging the firmware config into the firmware .bin file.
github.com
If the logic lane to SERDES mapping is different, you'd need to figure out how to edit the firmware config and upload it back onto the card.
This thread is on a different problem, but contains some information on editing + merging the firmware config into the firmware .bin file.
GitHub - BeTeP-STH/mft-scripts: Mellanox firmware files and MFT related scripts
Mellanox firmware files and MFT related scripts. Contribute to BeTeP-STH/mft-scripts development by creating an account on GitHub.
github.com
Could you post the info for your card and the sha1sum digest value for the firmware you downloaded? @mach3.2, my C3-Pro's Serdes mapping is the same as what you posted for the CX3 before I flashed. I just noticed the CX3-Pro I purchased had "Promiscuous VLAN" for its PRS name. Hmm...
My card's values:
My card's values:
Code:
# sha1sum fw-ConnectX3Pro-rel-2_42_5000-MCX314A-BCC_Ax-FlexBoot-3.4.752.bin
04d15c09b53b0cc4c3b1599dc13e68dbae37fb04 fw-ConnectX3Pro-rel-2_42_5000-MCX314A-BCC_Ax-FlexBoot-3.4.752.bin
Code:
# flint -d /dev/mst/mt4103_pci_cr0 query full
Image type: FS2
FW Version: 2.43.7028
FW Release Date: 12.1.2020
MIC Version: 2.0.0
Config Sectors: 1
PRS Name: cx3pro_MCX314A_40g_promiscus_vlan.prs
Product Version: 02.43.70.28
Rom Info: type=PXE version=3.4.662
type=UEFI version=14.9.90 cpu=AMD64
Device ID: 4103
Description: Node Port1 Port2 Sys image
GUIDs: ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
MACs: xxxxxxxxxxxx xxxxxxxxxxxx
VSD:
PSID: MT_1090111023
# flint -d /dev/mst/mt4103_pci_cr0 hw query
HW Info:
HwDevId 503
HwRevId 0x0
Flash Info:
Type M25PXxx
TotalSize 0x200000
Banks 0x1
SectorSize 0x1000
WriteBlockSize 0x10
CmdSet 0x80
JEDEC_ID 0x157120
# flint -i ./fw-ConnectX3Pro-rel-2_42_5000-MCX314A-BCC_Ax-FlexBoot-3.4.752.bin query full
Image type: FS2
FW Version: 2.42.5000
FW Release Date: 5.9.2017
MIC Version: 2.0.0
Config Sectors: 1
PRS Name: cx3pro_MCX314A_40g.prs
Product Version: 02.42.50.00
Rom Info: type=PXE version=3.4.752
Device ID: 4103
Description: Node Port1 Port2 Sys image
GUIDs: 0002c9000100d050 0002c9000100d051 0002c9000100d052 0002c9000100d050
MACs: 0002c9000001 0002c9000002
VSD: n/a
PSID: MT_1090111023Cards work in two of my servers with DACs inbetween, I'm fine with that.
I'll give up on trying to make it work with my 40GBASE-LR4 modules and I'll try to find another card for PC.
Which card do you recommend (that's easy to obtain) that has most compatibility with various modules ?
Thanks.
I'll give up on trying to make it work with my 40GBASE-LR4 modules and I'll try to find another card for PC.
Which card do you recommend (that's easy to obtain) that has most compatibility with various modules ?
Thanks.
Did you manage to flash to stock Mellanox Firmware? It‘s possible that the HP firmware has some special locks
In any case, I recommend using transceivers with Mellanox OUI programmed. Although people say that Mellanox is not picky when it comes to transceivers / cables, I don‘t agree.
yes, for basic cases Mellanox is not picky. But once you do stuff like LR, 56G, running 100G transceivers at 40G, Mellanox IS picky
In any case, I recommend using transceivers with Mellanox OUI programmed. Although people say that Mellanox is not picky when it comes to transceivers / cables, I don‘t agree.
yes, for basic cases Mellanox is not picky. But once you do stuff like LR, 56G, running 100G transceivers at 40G, Mellanox IS picky
I've found stock Mellanox 40Gbe card (MCX314A-BCCT ConnectX-3 Pro), waiting for it to be delivered.
If that doesn't work, then I'll try to move to 40GBASE-SR transcievers and sell these LRs that I have. Cabling is not an issue, I'll redeploy OM3/4 cable on those 50 meters that I need.
If that doesn't work, then I'll try to move to 40GBASE-SR transcievers and sell these LRs that I have. Cabling is not an issue, I'll redeploy OM3/4 cable on those 50 meters that I need.
Also, I've successfully connected Mellanox SX6012 and Brocade ICX6610-48p with mentioned 40GBASE-LR transcievers and 15m SMF cable. Additionally, I've tried connecting this HP card that's in TrueNAS server and it still won't work.
That definitely ruled out malfunctioned/incompatible transcievers and cabling. I just need a card with good compatibility.
That definitely ruled out malfunctioned/incompatible transcievers and cabling. I just need a card with good compatibility.
This is the card I bought recently for my devices. It worked right away in my Linux machines (Proxmox on a Dell R610 and Ubuntu on an old i7 based gaming PC) and worked after 5 minutes of downloading and installing drivers on my Win 11 and Win 10 machines. I haven't set up my network yet, but I did quickly test each card and transceiver (different than yours, SPTSBP2CLCKV INTEL 100G-CWDM4 for $5 each) and they work connecting to each other with no network switch. I got an Arista 7050SX2-72Q and my next task is setting up the network.