SFP+ copper module (FS 10G-T) incompatible with Mikrotik CRS 3xx?
Posted: Wed Nov 28, 2018 10:54 am
Because I need jumbo frames on 10Gb-T, (and after disqualifying Mikrotik S+RJ10, since it does not support jumbo frames), I bought some fs.com FS 10G-T modules.
I need this module in a CRS305. I tested this on the latest RouterOS: v6.44beta39.
The module shows up, but refuses to create a link, be it against 1G or 10G, against standard NICs, other SFP+ modules or regular switches.
I tried plugging in without cable and connecting cable afterwards, and connecting cable first and then inserting in the switch (this has been a known defect for Mikrotik). No change.
Here is a module dump:
Note that the module shows up as "sfp-connector-type: LC", and not as RJ45.
Support from FS.com states:
Is there anything I can do to get these modules working?
Is it a know (or not yet known) incompatibility without a potential solution in sight?
I need this module in a CRS305. I tested this on the latest RouterOS: v6.44beta39.
The module shows up, but refuses to create a link, be it against 1G or 10G, against standard NICs, other SFP+ modules or regular switches.
I tried plugging in without cable and connecting cable afterwards, and connecting cable first and then inserting in the switch (this has been a known defect for Mikrotik). No change.
Here is a module dump:
Code: Select all
name: sfp-sfpplus4
status: no-link
auto-negotiation: done
advertising:
link-partner-advertising:
sfp-module-present: yes
sfp-rx-loss: yes
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: LC
sfp-link-length-50um: 30m
sfp-link-length-62um: 10m
sfp-vendor-name: FiberStore
sfp-vendor-part-number: SFP-10G-T
sfp-vendor-serial: D8830921422
sfp-manufacturing-date: 18-03-23
sfp-wavelength: 850nm
sfp-temperature: 13C
sfp-supply-voltage: 3.327V
sfp-tx-bias-current: 6mA
sfp-tx-power: -3.01dBm
eeprom-checksum: good
eeprom: 0000: 03 04 07 10 00 00 00 40 00 0c 00 06 67 00 00 00 .......@ ....g...
0010: 03 01 00 00 46 69 62 65 72 53 74 6f 72 65 20 20 ....Fibe rStore
0020: 20 20 20 20 00 00 00 00 53 46 50 2d 31 30 47 2d .... SFP-10G-
0030: 54 20 20 20 20 20 20 20 20 20 20 20 03 52 00 84 T .R..
0040: 00 1a 0a 58 44 38 38 33 30 39 32 31 34 32 32 20 ...XD883 0921422
0050: 20 20 20 20 31 38 30 33 32 33 20 20 68 f0 03 33 1803 23 h..3
0060: 00 00 08 cc 60 6b 6a d2 48 23 da 01 88 e4 3d 7a ....`kj. H#....=z
0070: 66 39 44 00 00 00 00 00 00 00 00 00 22 0a 03 b5 f9D..... ...."...
0080: 55 00 ec 00 4b 00 f6 00 90 88 71 48 88 b8 79 18 U...K... ..qH..y.
0090: 1d 4c 03 e8 1b 58 05 dc 3d e8 09 cf 31 2d 0c 5a .L...X.. =...1-.Z
00a0: 31 2d 00 fb 27 10 01 3c 00 00 00 00 00 00 00 00 1-..'..< ........
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00c0: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00 ....?... ........
00d0: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 1d ........ ........
00e0: 0d c0 81 fb 0b b8 13 88 00 00 00 00 00 00 02 00 ........ ........
00f0: 00 40 00 00 00 40 00 00 00 00 00 ff ff ff ff 00 .@...@.. ........Support from FS.com states:
For the reason that the optics are recognized as LC modules, it's because that all FS 10G-T modules are coded with 10G SR codes.
However we've run through enough tests that the 10G SR coded modules will be able to function well even though it is not correctly recognized.
Is there anything I can do to get these modules working?
Is it a know (or not yet known) incompatibility without a potential solution in sight?