CRS317 not functioning with Avago SFP

I just got a CRS317-1G-16S+. I’m trying to use Avago ABCU-5700RZ SFP 1000Base-T modules in it. When I plug a module in, I can see it discovered in Webfig. However, when I plug a cable in there is no link or activity. The cable is known good. I don’t have any other SFP modules to test with.

Are these modules known to have problems?

Thanks.

Many devices from most vendors are more or less picky about SFP modules. Mikoritk prepared SFP compatibility list and you’ll notice overwhelming lack of information about modules from other vendors. Which may be understandable, testing for interoperability is a huge task and there’s no money for device vendors in it. However, generic SFP module vendors may test compatibility with certain devices and advertise this fact.

In case of total lack of information about compatibility it’s safe to assume there will be problems when using such combination.

Better use SPF modules listed in the Compatibility List…
It can be a Mikrotik SFP Module on one side and another Vendor’s on the other, in case you want to choose a compatible one for the Mikrotik and a compatible onoe e.g. for your server… (with same characteristics…)

I had the same issue as well in my CRS309 with the Avago ABCU-5700RZ 1000Base-T modules initially and finally got it to work:

  1. Open your Mikrotik in WinBox
  2. Select “Interfaces” then select the port with the Avago SFP
  3. Disable (uncheck) Auto Negotiation, Select 1Gbps and Check Full Duplex.
  4. Click apply and profit! You can see at the bottom that the SFP is enabled, running and the link is ok.

Thanks for the reply. I found out about the force speed trick after I sent the Avago SFPs back. Same trick does work with the Finisar modules I got later.

Thanks a lot this works perfectly.

One thing I’m wondering though. If at a later time I pull this transceiver out and then plug a 10g DAC or fiber transceiver in will I need to modify the settings again or will it automatically reset and use 10g?

What makes things worse, it sends out these igmp reports using 0.0.0.0, since it has no IP Address other than on the management vlan.
Because of the low ip address, it wins every querier election and ultimately breaks multicast, where a L3 device needs to be the querier for PIM / igmp-proxy to work correctly.