Hello
CCR2004 16S+ with 7.16.1 installed into a data center with 20° C
suddenly appeared the blu lines in the logs.
the router doesnt even open console terminal box. cpu at 0%
no snmp daemon on it. just a idle router at the moment…
no services exposed to the internet. just a plain l2tp to the router itself and a pppoe connection to the internet.
about 0 traffic on it
the very same even with the latest version beta
no activity on the router, really idle
Any SFP with DDC plugged in (and being queried about their state)?
IIRC it’s been mentioned that there’s a I2C bus which connects all internal monitored parts (power supplies and fans) as well as DDC buses of SFP cages. And if any of those devices block I2C bus for too long, ROS can not poll statuses of PSUs and fans and panicks. And similar behaviour was reported and every time it involved a SFP module not officially supported by MT (which means almost all SFP models).
Modules without DDC support (there aren’t many but they do exist) don’t cause such problems.
It was also mentioned with a few (recent) v7 releases that handling of these issues was improved … so if it’s not already you may want to upgrade ROS on your CCR to a recent version.
we have 2x 3mt DAC from mikrotik
1x GPON SFP+ from zyxel 2.5G
nothing else
I dont know if it uses that bus.
maybe the situation described here?
http://forum.mikrotik.com/t/ccr2004-with-sfp-onu-module-fail-both-psu/158227/1
Should I change kind of RB? Maybe a 1036 or 1009?
Still facing
PSU entered state FAIL
fans entered state FAIL
problems from time to time with our GPON module.
It did not change during update to recent ROS.
The issue is the GPON module,
change it and it will be OK.
otherwise I had success into a HEX-S
in that router 0 issues.
What do you suggest we change it to?
7.19beta2 has the same problem on CCR2116 
or change the GPON SFP or change the router.
Changing from a CCR to a HEX-S solved my issue
That is a sad statement if I have ever seen one.
Fix an CCR problem by buying a hex. I mean you gotta do what you gotta do but c’mon MT fix this issue.
GPON MA5671A (FS Modded Firmware)
CRS309 has all the information
CCR2116 does not have it and PSU1&PSU2 and FAN errors occur.
attached screenshots
The issue is HOW the CCR and the HEX manages and access the SFP.
It is a matter of BUS path.
So, change the router and you will fix that specific issue.
We have an issue with a specific kind of SFP GPON… dont blame MT.
If CCR doesnt work, put another platform (4011, HEX or similar)
So which router does not meet specifications in handling gpon traffic…
So if the problem is the gpon then my obvious question is
So which router does not meet specifications in handling gpon traffic…
You cannot have it both ways. If a faulty gpon works, then the router that it works on, is garbage as it should be more discriminating.
The whole thread is about compatibility between devices on different side of SFP cage. So CCR seems a bit more troublesome than some other RouterBoards. And GPON modules seem a bit more troublesome than plain MM/SM modules. MT doesn’t claim compatibility with 3rd party modules (neither in general nor for particular models), module vendors might (but since MT is relatively small player, SFP module vendors might not bother testing their devices with MT gear). So it boils down to trial and error process …
Change one of side of SFP cage and problem may go away. Obviously one can not change ONT module with pain SM module (for reasons not related to MT equipment), but one can change router.
I don't know how you can say that I should change my router after spending €1,000 in my case, when I'm coming from a Ubiquiti ER4 (€200) without any problems. In my case, I have a CCR2116 with problems, probably with a GPON, from what I've read in several forum threads. It's an MT problem and you have to accept that, since your product, which is supposed to be high-end, should have better compatibility than a mid-range/low-end Ubiquiti router.
Hello, well you bought the router, not the GPON interface . I undestand that is something not nice, but that is the situation.
I solved with another architecture, an HEX-S and everything worked. On CCR I had issues.