CSS318-16G-2S+ SFP+ Ports - no link [solved]

Hello,

today I got my CSS318-16G-2S+ and I trying to get one of the SFP+ Ports working at least. It is my first MikroTik Switch with SwOS. I have experience with RouterOS and other MikroTik products.

I've tried two MikroTik S+85DLC03D , one MikroTik S-R1 and two third Party 10G Fiber SFP+ Modules.

All these SFP(+) Modules are working in other MikroTik routers and switches.

All these SFP(+) Modules are shown/recognized in both SFP+ Ports under the SFP-Tab in SwOS.

But no Module is able to establish a link, not with Auto Negotiation, not with manual speed settings, not with Flow Control disabled. The LEDs of both SFP+ ports are staying dark and unter the Link Tab, "no link" is always shown.

I have no more guesses or ideas what could be wrong, especially after I tried every possible port/setting combination, which is done quite fast with SwOS.

Could it be simply a defective unit?

PS.: SwOS is 2.18 and I've resetted the switch two times already.

PPS.: The other switch, a CRS226-24G-2S+, is reporting that the 10G link is established and is sending data to the CSS318-16G-2S+ switch, but is recieving zero data back. I can confirm, that I can enable and disable the SFP+ Ports of the CSS318-16G-2S+ Switch under the Link Tab, which is recognized correspondly on the CRS226-24G-2S+ side.

Solved:

The fault was on the CRS226-24G-2S+ side. It seems that the first SFP+ port is partially defective after a module died in this port. Simply switching the module to the second SFP+ port solved the issue.

Hard to say . . . . I have that switch, also on 2.18, and have yet to find one that doesn't work . . . Avago, Finisar, 10G-Tek and one other connecting to either other MikroTik switches, or Intel or Mellanox host controllers, so the combo should be good.

Your fiber matches the SFP's in terms of mode and wavelength, and is not crossed?

Thank you for your answer. The issue was the first SFP+ Port of the CRS226-24G-2S+ Router. When I have some spare time, I will investigate what exactly is defective with this port. Its really weird, because everything else seemed to work normally.