FS.com BiDi SFP
-
I've got a few BiDi 1000Base SFPs from FS.com. Whenever I insert them into my XG-7100 1U, the console shows "Unsupported SFP+ module type was detected". Running an "ifconfig -vv ix1" shows "plugged: SFP/SFP+/SFP28 BASE-BX10 (SC)" and "vendor: FS PN: SFP-GE-BX SN: C2104040247 DATE: 2021-04-07" However, it the link is still down. I tried to manually set it to 1G, but the only option on the ix1 interface setting page is "Default" and "autoselect."
Also, every time I try booting with these SFPs installed, pfSense seems to freeze up entirely.
Any ideas on how to get this working?
-
See my reply on the other thread.
What you're seeing it what I expected to see locally but for some reason the modules I have (which were the cheapest I could find!) seem to work. I suspect it's because they report as a 1000BASE-LX device.
The reason it appears to 'lock up' is because the driver refuses to attach to a NIC with a bad module in it offsetting the interface numbering by one. That is fixed in 21.05 snapshots but it still won't link with that module.
Steve
-
@stephenw10 Seems plausible. I can confirm my working 3COM BiDi module represents itself as a 1000base-LX when plugged into pfSense or any other device.
-
@stephenw10 said in FS.com BiDi SFP:
What you're seeing it what I expected to see locally but for some reason the modules I have (which were the cheapest I could find!) seem to work. I suspect it's because they report as a 1000BASE-LX device.
I've got some Intel programmed modules coming from FS, so I'm hoping that will do the trick as well. Although I'm still a little skeptical, as I'm curious whether or not it will have to report as a 1000BASE-LX to properly work. I suppose we will find out soon enough!
-
@wblanton Not that it helps, but I mistakenly write LX - I meant SX. My BiDi module reports itself as a 1000Base-SX module.
-
N NTOC-ADMIN referenced this topic on
-
This post is deleted!
