UPDATE: Everything below was short-lived. When I rebooted the L009 again, it only went to 100Mbps (better than prior 10Mbps, but still...?
Interesting bit is that the CRS310 is now seeing the following speeds offered:
link-partner-advertising: 10M-baseT-half
10M-baseT-full
100M-baseT-half
100M-baseT-full
Missing the 2.5GBase-X seen earlier.
Swapping in a FS.com 1G SFP, the same issue appears.
Any idea which transceivers are known-good for this?
So the solution appears to be, per Mikrotik support:
-
Reset the port configurations on both sides
L009:/interface/ethernet/reset sfp1
CRS310: /interface/ethernet/reset ether1
-
On the SFP port, Disable autonegotiation and set 2.5G-BaseX. No apparent need to do the same on the CRS310.
/interface ethernet set sfp1 auto-negotiation=no speed=2.5G-baseX
-
Reboot the L009. Support mentioned that reseating the SFP might be sufficient, but that didn't work for me here. YMMV with other transceivers models.
Afterwards, both sides are at 2.5G, and throughput tests are going perfectly.
Here's what I see on CRS310's monitor output:
[snohomish@snohomish_sw3] > /interface/ethernet/monitor ether1 once
;;; DOWNLINK:sfp1:downstairs:rec_room:mikrotik:L009UiGS:snohomish_sw5_rec_room_aux
name: ether1
status: link-ok
auto-negotiation: done
rate: 2.5Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
supported: 10M-baseT-half
10M-baseT-full
100M-baseT-half
100M-baseT-full
1G-baseT-full
2.5G-baseT
advertising: 10M-baseT-half
10M-baseT-full
100M-baseT-half
100M-baseT-full
1G-baseT-full
2.5G-baseT
link-partner-advertising: 10M-baseT-half
10M-baseT-full
100M-baseT-half
100M-baseT-full
2.5G-baseT
[snohomish@snohomish_sw3] >
This is interesting because the CRS is still seeing autonegotiation from the sfp1. Is the SFP itself handling this indepenently of the switch?
On the L009 side (leaving out the EEPROM dump) :
[snohomish@snohomish_sw5_rec_room_aux] > /interface/ethernet/monitor sfp1 once
;;; UPLINK:ether1:downstairs:rec_room:mikrotik:crs310-8G+2S+::snohomish_sw3
name: sfp1
status: link-ok
auto-negotiation: disabled
rate: 2.5Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
supported: 10M-baseT-half
10M-baseT-full
100M-baseT-half
100M-baseT-full
1G-baseT-half
1G-baseT-full
1G-baseX
2.5G-baseT
2.5G-baseX
sfp-supported: 1G-baseX
sfp-module-present: yes
sfp-rx-loss: no
sfp-tx-fault: no
sfp-type: SFP/SFP+/SFP28/SFP56
sfp-connector-type: LC
sfp-encoding: sonet
sfp-link-length-om1: 200m
sfp-link-length-om2: 300m
sfp-vendor-name: Wiitek
sfp-vendor-part-number: SFP-2.5G-T
sfp-vendor-revision: 1.0
sfp-vendor-serial: WAMZ012604C050
sfp-manufacturing-date: 26-04-14
sfp-wavelength: 850nm
sfp-temperature: 42C
sfp-supply-voltage: 3.261V
sfp-tx-bias-current: 6mA
sfp-tx-power: -3.01dBm
sfp-rx-power: -3.979dBm
eeprom-checksum: good
My guess is that the SFP itself is handling the negotiation, but the L009 needs to have it disabled in order to not get in the SFP's way. No idea why it needs a reboot to lock that in, but this isn't something I'm going to be changing anytime soon.
Thanks everyone for the advice and shared knowledge!