I have noticed that the SFP port indicator LEDs on my CCR with version 6.9 are no longer indicating an active connection. When I enter WINBOX, I do see that the port is running (R). Anyone else notice this? I’ve checked the forum and found no mention of this - apologies if I have missed this elsewhere.
possible led broked? I have seen this to rb2011, but with some SFP’s not a sfp that have been working, and afterwards stop working.
Look at this.
http://forum.mikrotik.com/t/cloud-core-router/61111/1209
The funny part is that if you plug something into ether1 all LEDs are blinking.
It´s a bug with 6.9
Make sure you have latest bootloader installed and that system led configuration is correct
with v3.11.1 and following config works fine
[admin@MikroTik] /system leds> print
Flags: X - disabled, * - default
TYPE INTERFACE LEDS
0 * interface-activity sfp1 eth0-led
1 * interface-activity sfp2 eth1-led
2 * interface-activity sfp3 eth2-led
3 * interface-activity sfp4 eth3-led
I’m running v3.10 Firmware (this appears to be the latest version we can get) and RouterOS 6.10 and the LEDs are not working on the SFP Ports at all. When I look at the LED config in Winbox it is blank and it won’t let me add the settings.
When I look on Terminal, the settings do not load when you type print and if I try and add the settings, the Terminal crashes halfway through typing them.
Could really do with getting these LEDs working!
I’m currently running Firmware 3.10 (this is the newest version the CCR is showing as available) and RouterOS 6.10.
The SFP LEDs are still not working. I’ve tried /system leds print and it shows nothing.
It also won’t let me configure from Winbox, showing unknown when trying to select an LED. When trying the command from Terminal, it locks up halfway through trying to type the command.
I have same problem with SFP+ port on CRS1036-8G-2S+ with Direct Attach Cables. Actually running ROS 6.7 with bootloader 3.10.
more here:
http://forum.mikrotik.com/t/ccr1036-8g-2s-problem-with-direct-attach-cable-in-sfp-port/72436/1
I’m currently running Firmware 3.10 (this is the newest version the CCR is showing as available) and RouterOS 6.10.
The SFP LEDs are still not working. I’ve tried /system leds print and it shows nothing.
It also won’t let me configure from Winbox, showing unknown when trying to select an LED. When trying the command from Terminal, it locks up halfway through trying to type the command.
Send supout file from your CCR to support and we will take a look what it going on with SFP leds on this device.
I have same problem also customer wants to replace CCR beacuse of this failure.
I recommend to first check if this problem can be fixed by re-adding led configuration to make sure that it ain’t simply corrupted led configuration.
for CCR1036-8G-2S+:
/system leds
set 0 disabled=no interface=sfp-plus1 leds=eth0-led1 type=interface-speed
set 1 disabled=no interface=sfp-plus1 leds=eth0-led2 type=interface-activity
set 2 disabled=no interface=sfp-plus2 leds=eth1-led1 type=interface-speed
set 3 disabled=no interface=sfp-plus2 leds=eth1-led2 type=interface-activity
for CCR1036-12G-4S:
/system leds
set 0 disabled=no interface=sfp1 leds=eth0-led type=interface-activity
set 1 disabled=no interface=sfp2 leds=eth1-led type=interface-activity
set 2 disabled=no interface=sfp3 leds=eth2-led type=interface-activity
set 3 disabled=no interface=sfp4 leds=eth3-led type=interface-activity