If that were the stipulation, IPv6 would have been supported in RouterOS 5 lol.I doubt its a priority unless they have customer, (talking in the $100,000+ range) that requests that functionality.............
I'm on the 7.7 on all devices. CRS309 is firmware 7.6 (which I'm trying). I don't believe they worked in my CCR2004 either. Mine are EA as well. I don't get any links to any devices when they're in, with autonegotiation or manual setting.What version of RouterOS are you running? What version of firmware is on the switch/router? There were some SFP+ updates in 7.4.1 and later I believe.
I have a couple of the EA versions of those and they seem to work fine. The switch (or router, in my case a CCR2004) seems to negotiate 10G to the SFP+, which in turn negotiates 2.5G to the other device (in my most recent test, the latest revision of the Wave AP with a 2.5G copper port).
7.6 firmware. I'm not on 7.8b on any device. Didn't think 7.6 firmware mattered since you mentioned the fixes were 7.4.1And under System Routerboard the firmware also 7.7?
7.8b2 has a warning that it's not for CRS300 devices.
I tried 2.5Gbps without autonegotiation, but I haven't tried 10. I can try that and come back.Oh, I was reading on my phone on a rooftop, and I thought I saw 7.8 on the CRS309 instead of 7.6. (Guess it's time to get glasses.)
Have you tried setting it to 2.5Gbps or 10Gbps without auto-negotiation? When I'm done with my outside work today, I'll have to take one of those and try it on a 309 in the lab.
So I just went down and tried it again, it seems to actually work on my CCR2004. However, on both my CRS309 and CRS328 I'm unable to get a link on any of the SFP+ ports. I even brought out an unopened one and that didn't work either.Oh, I was reading on my phone on a rooftop, and I thought I saw 7.8 on the CRS309 instead of 7.6. (Guess it's time to get glasses.)
Have you tried setting it to 2.5Gbps or 10Gbps without auto-negotiation? When I'm done with my outside work today, I'll have to take one of those and try it on a 309 in the lab.
I have a ticket open with Mikrotik in which they said they wanted to fix this and I provided them some logs and audit info for them to look into it. I haven't heard anything from them though, but I imagine it's on the table for the next update(s).I'm interested as well. Did anyone manage to get these working? They worked out-of-the-box in a Intel X520-DA2, I thought they'll just work on Mikrotiks, but CRS309/310 seem to see them (I can see the model, vendor, etc.) but no link, in either autoneg or forced 10G. Running 7.8.
Thanks, I raised a ticket too, will see.I have a ticket open with Mikrotik in which they said they wanted to fix this and I provided them some logs and audit info for them to look into it. I haven't heard anything from them though, but I imagine it's on the table for the next update(s).
OT: You said yours worked in an X520-DA2, what OS were you using them on, and did you have to do any mods for it to work?
Go, and test yourself.Did anyone retest with newer routeros, 7.10?
IMHO, having on the market, a 30$/€ SFP or SFP+ module supporting 1Gb/s or 2.5Gb/s would be very interesting if it can avoid such heat issues.I was looking for alternative to S+RJ10 because that runs as hot as fusion reactor.
Did a quick test - one CRS310 with S+RJ10, another one with the Ubiquity, both in autoneg - doesn't work. "RX loss" is shown all the time.Did anyone retest with newer routeros, 7.10?
If you can pull cat6e (or cat7) UTP cables, then you could pull FO cables as well. And optical SFP modules generally don't suffer from the excessive heat generation problem. Plus the range is much longer.
I thought FO is harder to deploy than copper as:If you can pull cat6e (or cat7) UTP cables, then you could pull FO cables as well.
Thank you very much for this very informative reply.I always use the small LC connectors,
...
/interface ethernet monitor sfp-sfpplus2
# 2023-08-22 12:20:10 by RouterOS 7.11
# software id = 3VVI-W6C1
#
name: sfp-sfpplus2
status: no-link
auto-negotiation: failed
advertising:
link-partner-advertising:
sfp-module-present: yes
sfp-rx-loss: yes
sfp-tx-fault: no
sfp-type: SFP/SFP+/SFP28
sfp-connector-type: RJ45
sfp-link-length-copper-active-om4: 100m
sfp-vendor-name: Ubiquiti Inc.
sfp-vendor-part-number: UACC-CM-RJ45-MG
sfp-vendor-revision: U07
sfp-vendor-serial: AK23017502216
sfp-manufacturing-date: 23-01-28
eeprom-checksum: good
eeprom: 0000: 03 04 22 10 00 00 00 20 40 04 80 06 67 00 00 00 ..".... @...g...
0010: 00 00 64 00 55 62 69 71 75 69 74 69 20 49 6e 63 ..d.Ubiq uiti Inc
0020: 2e 20 20 20 00 24 5a 4c 55 41 43 43 2d 43 4d 2d . .$ZL UACC-CM-
0030: 52 4a 34 35 2d 4d 47 20 55 30 37 20 03 52 00 e9 RJ45-MG U07 .R..
0040: 00 00 00 00 41 4b 32 33 30 31 37 35 30 32 32 31 ....AK23 01750221
0050: 36 20 20 20 32 33 30 31 32 38 20 20 00 00 08 91 6 2301 28 ....
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
*
I was trying RB5009 + this UACC-CM-RJ45-MG on 7.11.2 and nope. It can see it, but nothing can be negotiated (1000Mbit/s on the other side), even if I put manual speed, also doesn't work.I've been in contact with support on this and can now happily report as of latest version v7.11, for me this is now working!!!
No more RX Loss.
fs.com from my expirience is by far better than UBNT ...For what is worth: after waiting and waiting, I gave up and searched for a different, low-power RJ45 transceiver. I bought one from fs.com (SFP-10G-T100, part number #154925, chipset Broadcom, and marked as Power: ≤1.8W) and that just worked when plugged into a CRS309. On the other end is a S+RJ10 for now (I immediately ordered a few more from fs.com).
This is clearly more efficient than the S+RJ10:
- it doesn't burn my finger when I touch it
The transceiver itself doesn't have a temperature sensor, but as the S+RJ10 was reporting ~85 celsius before I took it off, and this not burning me, I'm sure there's a large difference.
- the "cpu temperature" has decreased by 1-2 celsius since then
Now I'm stuck with a few Ubiquity ones that don't seem to get any traction, sigh.
This looks great, but I have to ask, did you really pay $139 per adapter? That's what it's listed for at fs.com right now (the 100m version, which seems to be the only one with the low 1.8W rating)I bought one from fs.com (SFP-10G-T100, part number #154925, chipset Broadcom, and marked as Power: ≤1.8W)
I did Yes, it's expensive, but also it was the easiest (and possibly the cheapest) way to solve the one link I need at 10G over copper.This looks great, but I have to ask, did you really pay $139 per adapter? That's what it's listed for at fs.com right now (the 100m version, which seems to be the only one with the low 1.8W rating)I bought one from fs.com (SFP-10G-T100, part number #154925, chipset Broadcom, and marked as Power: ≤1.8W)
OK, thanks for confirming, and thanks for the hint about the product in the first place!I did Yes, it's expensive, but also it was the easiest (and possibly the cheapest) way to solve the one link I need at 10G over copper.
Another question, if I may. I ordered this adapter as well but when I plugged it into the SFP+ slot on the CRS309, it does not link up. I also have an S+RJ10 on the other side. I can see the vendor/serial info etc. in the SFP tab, but it won't connect.For what is worth: after waiting and waiting, I gave up and searched for a different, low-power RJ45 transceiver. I bought one from fs.com (SFP-10G-T100, part number #154925, chipset Broadcom, and marked as Power: ≤1.8W) and that just worked when plugged into a CRS309.
Initially no, but after the most recent version (7.13), I need to force link speed to fixed. I haven’t tried mixed, only same transceiver on both ends, both with fixedAnother question, if I may. I ordered this adapter as well but when I plugged it into the SFP+ slot on the CRS309, it does not link up. I also have an S+RJ10 on the other side. I can see the vendor/serial info etc. in the SFP tab, but it won't connect.For what is worth: after waiting and waiting, I gave up and searched for a different, low-power RJ45 transceiver. I bought one from fs.com (SFP-10G-T100, part number #154925, chipset Broadcom, and marked as Power: ≤1.8W) and that just worked when plugged into a CRS309.
Did you do anything else when you started using it in the CRS309?
I am on 7.13 and I can confirm that it does indeed start to work for me when I turn off auto-negotiation and configure the speed manually. It did not work with different adapters on both ends, I had to use two of the FS ones. Now I'll see how much cooler they run.Initially no, but after the most recent version (7.13), I need to force link speed to fixed. I haven’t tried mixed, only same transceiver on both ends, both with fixed
I filed a support ticket with MikroTik requesting that they fix that issue and fully support this FS.com module. The support case number is SUP-142140.I am on 7.13 and I can confirm that it does indeed start to work for me when I turn off auto-negotiation and configure the speed manually. It did not work with different adapters on both ends, I had to use two of the FS ones. Now I'll see how much cooler they run.Initially no, but after the most recent version (7.13), I need to force link speed to fixed. I haven’t tried mixed, only same transceiver on both ends, both with fixed
I wonder if disabling auto-negotiation would also make it work for the Ubiquiti ones.
Thanks again for the tips!
It's SFP. It is an industry standard.
Thanks for the guidance and my apologies for the heated attitude I brought in as my first post. I’ve absolutely enjoyed using Mikrotik products. I first familiarized myself with it almost a decade ago whilst living in Rīga, Latvia when it was still relatively unknown in the wider world, where it was used in the apartment complex I lived. Just recently though I purchased my first own home for the family here in Finland and based on a Canadian friend’s recommendation chose a mix of Mikrotik routers and Ubiquiti APs for building a home network. They have worked together surprisingly well. Just somehow I got hit in the face when I hoped to gain an extra Ethernet port by buying an RJ45 SFP module. I had indeed reviewed the official manual listing SFP compatibility for each RouterOS device, and had assumed the lowest tier of 1Gbps copper modules would all work. The only immediately available SFP RJ45 module I had nearby was one by Ubiquiti. I have little experience with enterprise level network equipment so I naturally assumed SFP was a standard and much like CAT6 as long as it has the designation it would work. I have now ordered a Mikrotik RJ45 module as a replacement and will report back.It's SFP. It is an industry standard.
You'd think.
And you'd think wrong.
Why else would FS.com ship a given module matching the rough specs of this thread's topic in 20 different versions plus "Generic," each with a different product ordering attribute? Why would their staff follow up after the order to make sure you selected the right one for your specific application? Why would they offer a firmware reprogrammer for moving existing modules from one vendor to another?
There do exist generic modules, but in my experience, they lack features, suggesting a lowest-common-denominator approach.
In my experience coding the SFP(+) for different vendors is only done to get around vendor lock-in.
interface ethernet monitor sfp-sfpplus2
name: sfp-sfpplus2
status: no-link
auto-negotiation: done
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,5G-baseT,10G-baseT,
10G-baseSR-LR,10G-baseCR
sfp-supported: 10M-baseT-half,10M-baseT-full,
100M-baseT-half,100M-baseT-full,
1G-baseT-half,1G-baseT-full
name: sfp-sfpplus2
status: no-link
auto-negotiation: done
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,5G-baseT,10G-baseT,
10G-baseSR-LR,10G-baseCR
sfp-supported: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,
1G-baseT-full
advertising: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,
1G-baseT-full
link-partner-advertising:
sfp-module-present: yes
sfp-rx-loss: no
sfp-tx-fault: no
sfp-type: SFP/SFP+/SFP28/SFP56
sfp-connector-type: RJ45
sfp-link-length-copper-active-om4: 100m
sfp-vendor-name: Ubiquiti Inc.
sfp-vendor-part-number: CM-RJ45-1G
sfp-vendor-revision: A1
sfp-vendor-serial: AX23082802353
sfp-manufacturing-date: 23-08-07
eeprom-checksum: good
eeprom: 0000: 03 04 22 00 00 00 08 00 00 00 00 01 0d 00 00 00 .."..... ........
0010: 00 00 64 00 55 62 69 71 75 69 74 69 20 49 6e 63 ..d.Ubiq uiti Inc
0020: 2e 20 20 20 00 24 5a 4c 43 4d 2d 52 4a 34 35 2d . .$ZL CM-RJ45-
0030: 31 47 20 20 20 20 20 20 41 31 20 20 00 00 00 5a 1G A1 ...Z
0040: 00 00 00 00 41 58 32 33 30 38 32 38 30 32 33 35 ....AX23 08280235
0050: 33 20 20 20 32 33 30 38 30 37 20 20 00 00 00 a1 3 2308 07 ....
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
*
Upgrading to 7.17beta2 yielded similar results, SFP is detected but no link is established. Manually configuring negotiation to any of the standard 1G/100M/10M both full and half duplex also doesn't help as it did some users. I'm going to on a limb and assume there's no compatibility. I'll try notifying Mikrotik support for further assistance.I can additionally confirm that another SFP product by Ubiquiti is incompatible with the latest stable RouterOS. Product is the UACC-CM-RF45-1G, running RoS on 7.16.1
Connecting it and a standard CAT6 RJ45 plug yields no lights and no established link. Curiously, RoS is able to detect the module and decipher it partially:
Do we have any information on a possible patch of some sort to fix compatibility?Code: Select allinterface ethernet monitor sfp-sfpplus2 name: sfp-sfpplus2 status: no-link auto-negotiation: done 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,5G-baseT,10G-baseT, 10G-baseSR-LR,10G-baseCR sfp-supported: 10M-baseT-half,10M-baseT-full, 100M-baseT-half,100M-baseT-full, 1G-baseT-half,1G-baseT-full name: sfp-sfpplus2 status: no-link auto-negotiation: done 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,5G-baseT,10G-baseT, 10G-baseSR-LR,10G-baseCR sfp-supported: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half, 1G-baseT-full advertising: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half, 1G-baseT-full link-partner-advertising: sfp-module-present: yes sfp-rx-loss: no sfp-tx-fault: no sfp-type: SFP/SFP+/SFP28/SFP56 sfp-connector-type: RJ45 sfp-link-length-copper-active-om4: 100m sfp-vendor-name: Ubiquiti Inc. sfp-vendor-part-number: CM-RJ45-1G sfp-vendor-revision: A1 sfp-vendor-serial: AX23082802353 sfp-manufacturing-date: 23-08-07 eeprom-checksum: good eeprom: 0000: 03 04 22 00 00 00 08 00 00 00 00 01 0d 00 00 00 .."..... ........ 0010: 00 00 64 00 55 62 69 71 75 69 74 69 20 49 6e 63 ..d.Ubiq uiti Inc 0020: 2e 20 20 20 00 24 5a 4c 43 4d 2d 52 4a 34 35 2d . .$ZL CM-RJ45- 0030: 31 47 20 20 20 20 20 20 41 31 20 20 00 00 00 5a 1G A1 ...Z 0040: 00 00 00 00 41 58 32 33 30 38 32 38 30 32 33 35 ....AX23 08280235 0050: 33 20 20 20 32 33 30 38 30 37 20 20 00 00 00 a1 3 2308 07 .... 0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ *