Jump to content

Mellanox MCX312B-XCCT not present in the list of avaible NICs


Cael817
Go to solution Solved by JorgeB,

Recommended Posts

Hi all,

Recently bought a couple of Mellanox MCX312B-XCCT CX312B, these are dual ports and one is used for connecting a pfsense box between WAN and LAN (1G SFP on the WAN side and a 10G SFP+ DAC cable on the LAN side).
The other i put in my Unraid box (One port unused and one connected to LAN with a 10G SFP+ DAC) but it won't show up in the list of NICs in the "/Settings/NetworkSettings -> Interface Rules and the drop down lists.

Checking the logs gives me these warnings and "0000:04:00.0" being my Mellanox card indicates that everything is not all right.

Jan 22 19:39:48 Tower kernel: ACPI: Early table checksum verification disabled
Jan 22 19:39:48 Tower kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x04000000 64bit pref]
Jan 22 19:39:48 Tower kernel: floppy0: no floppy controllers found
Jan 22 19:39:48 Tower kernel: ACPI Error: No handler for Region [SYSI] (000000001bc0de87) [IPMI] (20220331/evregion-130)
Jan 22 19:39:48 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20220331/exfldio-261)
Jan 22 19:39:48 Tower kernel: ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
Jan 22 19:39:48 Tower kernel: ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
Jan 22 19:39:48 Tower kernel: ACPI: \_SB_.PMI0: _PMC evaluation failed: AE_NOT_EXIST
Jan 22 19:39:48 Tower kernel: mlx4_core 0000:04:00.0: Failed to initialize queue pair table, aborting
Jan 22 19:39:48 Tower kernel: mlx4_core: probe of 0000:04:00.0 failed with error -5
Jan 22 19:52:02 Tower root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg
Jan 22 19:52:08 Tower root: Fix Common Problems: Other Warning: dynamix.file.manager Support Updated

I have updated the FW to the latest i could find "2.42.5000" but i have the error/issue. I have also deleted network-rules.cfg and network.cfg and rebooted but no dice.
The two cards i have have been swapped around between the pfsense box and the unraid one where both worked as intended in pfsense.

Last idea i have right now is to swap in the card in another PCIe port but wanted to ask here first.

Bit of googeling on "mlx4_core 0000:04:00.0: Failed to initialize queue pair table, aborting" but that doesn't seem like something 'i' can configure?
https://support.mellanox.com/s/article/MLNX2-117-2389kn

Someone have any good ideas?

tower-diagnostics-20230122-2125.zip

Link to comment

Good news, changing the PCIe port worked.

 

This is a Dell R720xd and i had the Mellanox card in riser 2, slot 5 which indicates that its connected to CPU 1. Moved it around to riser 1, slot 3 and that slot says CPU 2. Show right up after starting the server, set it to 'eth0' and did a restart and viola, everything works.

 

Thanks @JorgeB.

  • Like 1
Link to comment
  • 1 year later...

Hey, I am trying to use this same card as above. One SFP+ port on the Mellanox card via Linkbasic Direct Attached Copper 1m 10G SFP+ Uplink Cable to SFP+ port 11 on UDM Pro. The card shows in the unraid network settings setup. However when i try configure the device shows online for a few seconds then drops. eth0 is existing 1000mbps port. I am not sure if this is a configuration thing of hardware is cable or pcie slot. i also had a short lived issue with getting stuck in the flexboot initialisation as the USB was not reading. Port one was connected to the UDM at the start. @Cael817 how did you configure? I have set rules for the port to go to the same vlan as the existing GBE. I have set the SFP to a new ip address manually with ETH1 mac address so when it joins the network it will be at an ip i know. then i can replace it with the existing static one services call to.

Screenshot 2024-02-26 190446.png

Screenshot 2024-02-26 190415.png

Screenshot 2024-02-26 190354.png

IMG_20240226_200728.jpg

Link to comment

I hope this is of some help, it was about a year ago i fiddled with this, these are my settings (starting to think that having a 1GBe as backup may hurt my performance but im not sure, system is up so my settings don't seem to show the same screen as yours but i can stop my VMs tomorrow if you need better screens).

image.thumb.png.d05ebd2ec93a7e571b1638533bbb9eed.png

image.png.54516a86fdaa72d0653bf1fbdee121a7.png

This is the cables i bought from fs.com

image.png.8610b7bef94dd7401fcabfb302c2e7ca.png

Im not sure i explained my connections thoroughly and im not sure this will help but..

Wan is connected to a pfSense box with 1GBe fiber, pfSense box has one one the Mellanox cards and a 1GBe SFP in the Wan port, The second (LAN) port has one of the DAC cables connecting to my switch (Cisco, that's why i bought a Cisco coded cable, i think you can disable the check but price was low and id didn't want to screw around with that, fortunately the Mellanox card didn't complain (and shouldn't to my understanding)), Then from the switch i have the other DAC cable connected to my Unraid and eth0 using the other Mellanox card (second SFP port on this Mellanox card is unused).

 

Edited by Cael817
Link to comment

Thanks for the support @Cael817, taking the time to look out the information to help me is very kind of you. Through some experimentation I think you made the 10g port the eth0 using the "Interface Rules" and the 1GBE your eth1. I have replicated making NIC p1 = eth0, NIC p2 = eth1, GBE = eth2. I have bonded eth0 and eth2. eth0 picks up a ip from DHCP on UDM and Unraid is accessible by this DHCP provided address in addition to the static address assigned by the UDM router to the GBE /eth2 port. If i pull eth2 Unraid is inaccessible. In addition i have the warning "interface ethernet port 0 is down. check cable!" I'm still uncertain if it is a config or cable issue. perhaps you could share your config of your eth1. Perhaps there is something i am overlooking with my inexperience with sfp and NIC.

Screenshot 2024-02-27 115953.png

Screenshot 2024-02-27 114642.png

 

EDIT: to include the interface dashboard view. It will alternate on/off eth0.

733113006_Screenshot2024-02-27123317.png.41a4b685983251f2340208de8b2dbbd5.png

213738171_Screenshot2024-02-27123552.png.112d8c6508163796489e1c71d03f95ad.png

Edited by Be-Art
Addition of screenshots
Link to comment

Hey @Cael817, do you mind sharing your config info with me, i am stumped. I have got SFP+ fiber transceivers now because of the check cable statement and still no communication. Greatly appreciated if i could know if there is anything special configured on your eth1 before bonding to eth0. 

Screenshot 2024-02-28 201900.png

Screenshot 2024-02-28 194247.png

Link to comment

Crap, genuinely sorry. I completely forgot about this when i got some cool suff for my 3D printer build.

 

Anyway, i don't remember doing anything special, heres a screen with eth1 removed from the bond

Capture.thumb.PNG.52bd7b29d73cb2fb784967e82c4762af.PNG

 

And here's when re adding it

Capture2.thumb.PNG.c74d020c6086b50ef881470b5b266073.PNG

 

Now, i have to admit that i have not tested if the backup is working but im going to pull the 10GB in a few minutes and see what happens 😃

 

Few minutes later, failover worked

image.png.4ad9faf98677055bedbb6eacf9efaf3e.png

Edited by Cael817
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...