Hi there forum!
I'm having some interesting problems with my (ISP supplied) SFP module (not SFP+ mind you) in my DEC750. I knew from the get-go that it would probably not be as plug-and-play as it was in my old USG 4 Pro, the port being SFP+ and all, but what I've encountered is somewhat beyond me.
I've determined that the SFP module is supposed to run at 1000baseLX (see spec sheet below), and it is quite possible to get it up and running. But it requires some manual work. I've set the module, in `ax0` to run at the specified speed/duplex:
1.jpg
But after (re-)booting it looks like this in the console;
2.jpg
Specifically the `media: Ethernet autoselect` and `status: no carrier` are a bit troubling, for I hope obvious reasons.
The workaround I've been able to come up with is to set the s/d to 1000Base-KX;
3.jpg
which gives me a carrier, but no connectivity. (I'm guessing the final lines are just remnants from previous successful DHCP requests as I re-created the errors and fixes a few times.) Then switching back to 1000baseLX I get both a carrier and proper connectivity until reboot;
4.jpg
Things I've tried so far;
- Going from `autoselect` to `1000baseLX` ❌
- Going from `autoselect` to `1000base-SGMII` ❌
- Going from `autoselect` to `1000baseSX` ❌
- Going from `1000base-SGMII` to `1000baseLX/code] ❌
- Setting `1000Base-KX` rebooting and then selecting `1000baseLX` ❌
So, if I've not been clear about what my problem is; I can, after some workarounds, get the link up and working, but I'd like to not have to as it stops me from retiring the USG 4 Pro and switching over the DEC750. I'm fine with having to do some automated post-ax0-up-scripting if that would solve my issue, but I've not found a straightforward way to change the s/d setting via the CLI or where I'd put a script to do it 😅
Thoughts? Idea? Suggestions? Dare I say, solutions? 😁
Thank you for your time regardless!
SFP module spec sheet, if that matters (https://shop.hexatronic.no/files/parts?partNumber=HSB-70590-67&fileName=HSB-70590.pdf) 😉
"ifconfig ax0 media 1000baseLX" may work from CLI/shell. Why poking the media type twice helps is odd - it may make setting the options in (e.g.) rc.conf (ifconfig_ax0 "media ...") a bit problematic, unless the options/commands are just fired in sequence.
I wouldn't expect any functional difference between "1000baseSX"/"...LX"/"...CX" or even "...KX", but KX might have some differences due to its use as a backplane interface. I could see the speed being an issue, potentially.
The Hexatronic module might have specific quirks built into the driver phy section... you'd have to dig into the interface driver used on the Ubiquiti. Seems a bit unlikely, but you never can tell.