Gen2 x4 or gen3 x2 lanes would be a good explanation, it really depends on the motherboard. I had only 6 Gbps with my MCX311A-XCAT and it turned out that my mobo supports only gen2 x2 on the second PCIE x16 slot even though the first slot is gen3. I had to change motherboard to be able to fully use SFP+. I am thinking on QSFP+ now. If we can buy these cheap cards and convert them to real Mellanox, then SFP+ and QSFP+ have almost the same price.
Flashing stock Mellanox firmware to OEM (EMC) ConnectX-3 IB/Ethernet dual-port QSFP adapter
- Thread starter ullbeking
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Yes i was able to flash the device and it works great. BUT i could not get WOL to work.
It is hard to find them second hand, they are still expensive compared to CX3. I just bought 2 dual-port HP CX3 for $60. Or maybe a half brick, I'll figure out next week.
Not with EMC branded ones, but with HPEs:
The single port models are cheap for "current gen" ethernet nics (e.g. hpe branded,. single port cx-4: 825110-b21 | eBay)
I have a couple of ConnectX-3 with 2 Proa. 314-BCCT IIRC. These are not HP branded. Are these just locked to ETH? I have 40GbE working nicely, but wondering about IB support.
Are those HP nics visually branded with a sticker on it?
Are those HP nics visually branded with a sticker on it?
Hello I was able to flash a MCX354A-QCBT card to FCBT latest firmware.
The flash finished successfully and i was able to get the 40gbps link working to my Dell s4810 switch.
But when i restart the server it stops working.
In the windows server 2019 device manager i get a yellow exclamation mark.
The ethernet ports stop working.
What could be wrong and what should i do differently?
The flash finished successfully and i was able to get the 40gbps link working to my Dell s4810 switch.
But when i restart the server it stops working.
In the windows server 2019 device manager i get a yellow exclamation mark.
The ethernet ports stop working.
What could be wrong and what should i do differently?
Are you running infiniband / ethernet or VPI mode.
Frequently if your running ethernet and the cards are set to VPI mode (autodetect and run either or) you will have problems when the windows machines start. Look up how to set the PORT_TYPE use mellanox firmware tools. If you set it with the firmware tools it gets written to card and stays in the mode until manually changed.
The VPI mode frequently times out the windows driver before the card has decided what type of switch its talking to.
Frequently if your running ethernet and the cards are set to VPI mode (autodetect and run either or) you will have problems when the windows machines start. Look up how to set the PORT_TYPE use mellanox firmware tools. If you set it with the firmware tools it gets written to card and stays in the mode until manually changed.
The VPI mode frequently times out the windows driver before the card has decided what type of switch its talking to.
@Terry Wallace I have set the PORT_TYPE using the firmware tools to ethernet mode.
The card starts with Ethernet mode by default but the drivers are showing an error (Yellow Exclamation mark in Device Manager)
The card starts with Ethernet mode by default but the drivers are showing an error (Yellow Exclamation mark in Device Manager)
What driver version is that? On newer drivers the Port Protocol tab is gone, at least on my CX354a cards. I also don't see the Information tab. When I changed them to Ethernet mode, the device name changed from "Mellanox ConnectX-3 Pro VPI" to "Mellanox ConnectX-3 Pro Ethernet" after the reboot. I'm using the WinOF 5.50.54000 package from Mellanox OFED for Windows - WinOF / WinOF-2.
@LodeRunner
I am using the same drivers as you have linked.
I see the Port Protocol tab in the System Devices section.
I am using the same drivers as you have linked.
I see the Port Protocol tab in the System Devices section.
Maybe it's different for the CX3 Pros. Here's the driver information on my server:
Given that the Information tab is missing in your images, I think your system is not loading the correct driver, unless the MT04099's don't get that driver panel. My workstation has a MCX311A-XCAT and it uses the same version, but adds tabs for Teaming and VLAN settings (but that may also be a Win 10 vs Server 2019 thing).
Given that the Information tab is missing in your images, I think your system is not loading the correct driver, unless the MT04099's don't get that driver panel. My workstation has a MCX311A-XCAT and it uses the same version, but adds tabs for Teaming and VLAN settings (but that may also be a Win 10 vs Server 2019 thing).
Last edited: