SFP-10G-T for Mellanox?
- Thread starter Jamy
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Is the card using generic Mellanox or an OEM firmware? I seem to remember seeing someone else on here having issues with vendor locking on transceivers on his OEM NIC before flashing the generic Mellanox firnware.
You can probably figure that out from the PSID.
NOTE: I'm just guessing here. Could definitely be something else.
You can probably figure that out from the PSID.
NOTE: I'm just guessing here. Could definitely be something else.
It's Dell re-flashed to generic Mellanox.Is the card using generic Mellanox or an OEM firmware? I seem to remember seeing someone else on here having issues with vendor locking on transceivers on his OEM NIC before flashing the generic Mellanox firnware.
You can probably figure that out from the PSID.
NOTE: I'm just guessing here. Could definitely be something else.
I'm not sure if they are compatible or not, that's why I'm posing the issue here
Hoping those more experienced with Mellanox than I have an answer. Mellanox lists the card as able to use SFP+ and SFP28. MLX5CMD indicates the below, so it seems to recognize it, but windows still shows the cable unplugged.
Adapter: Mellanox ConnectX-4 Lx Ethernet Adapter #4
Location (PCI bus, device, function): (4,0,1)
Operational Info
State : Polling
Active protocol : Ethernet
Physical state : 0
Active link speed : Unknown
Enabled PHY manager link speed : {25.00 Gbps, 10.00 Gbps, 1.00 Gbps}
Enabled core to PHY link speed : {10.00 Gbps, 1.00 Gbps}
Active negotiation mode : 4
Loopback mode : 0
FEC : 0
Cable supported speeds : {10.00 Gbps}
Troubleshoot Info
Status Opcode : 0
Group Opcode : 0
Message : No issue was observed
Good. That shouldn't be an issue then.
I'm fairly sure they are supposed to work in NICs too.
Could you try live booting a Linux distro like Ubuntu or Debian and see if it behaves differently? At the same time, you could collect and paste the output of "sudo ethtool -m [interface_name]" here.I'm not sure if they are compatible or not, that's why I'm posing the issue here
MLX5CMD indicates the below, so it seems to recognize it, but windows still shows the cable unplugged.
See https://forums.servethehome.com/index.php?threads/brocade-icx-6610-48p-112-obo.39628/post-372430
CX4s and newer NICs have more restrictions on the types of transceivers they will accept. While I don't have your brand of transceiver, I've been able to confirm @NablaSquaredG's experience using Mellanox firmware.
CX4s and newer NICs have more restrictions on the types of transceivers they will accept. While I don't have your brand of transceiver, I've been able to confirm @NablaSquaredG's experience using Mellanox firmware.
Interesting. I'm curious to see if it is a brand lock thing or something else. I have a 10gbaseT model that claims to be coded for Mellanox on the way for testing.
DACs are vendor coded. Some NIC vendors don't enforce their vendor locks on DACs though from what I've been told, only on fiber (and possibly 10GBase-T) transceivers.
My understanding is that it's because vendor locking a cable with permanently attached ends becomes very hard for their customers to use, especially for vendors like Intel who don't make switches etc. You'd require DACs with different vendor codes on each end, which is something only available from third party DACs, defeating the entire point.
If you are using one of the fs.com 10GbE SFP+ units that also links at 5/2.5/1GbE, be wary. I've had nothing but trouble with the ethernet performance at 1Gbps (lots of errors) and there also seem to be buffering issues.