CCR1036-8G-2S+ problem with Direct Attach Cable in SFP+ port

Hardware MikroTik hardware general
1

I have finally got my hands on the CCR1036-8G-2S+ and started testing it in our network. But suddenly I have fallen in troubles with Direct Attach Cables which are connecting CCR to Extreme Networks X670.

First of all I X670 was unable to establish a link with CCR, but on the side of CCR port was running, but no link or activity signalized by LEDs. This was fixed by disabling auto-negotiation on X670 and forcing 10GbE full-duplex.

At this point data goes trough at 10Gbps but link and activity LEDs still don’t have a light. I gave chance to a few other DA cables but behavior is same. Actually I don’t have SM/MM SFP+ modules available for testing.

Any ideas?

Martin

CCR 6.9 SFP Indicator LEDs not functioning
2

We are using SR modules to connect to Summit X670 switches successfully. You problem sounds like it is related to DA cable compatibility.

3
4

Yes, it seems to be some problem with DA cables at the side of CCR. I tested more different cables with no difference in behavior. Some SR/LR will arrive on Monday, so I plan to do more testing.

5

I finally did some more test fit SR/LR SFP+ modules instead of DAC and noticed no problem with LEDs. So it look like support for DAC in CCR is somehow unfinished.

Does any body else runs CCR with DAC? I have a DAC only from one vendor, so I’m just curious if it is problem of brand or DAC in general.

6

Which ROS version is installed on this CCR? Led behavior for DACs should be correct in latest releases.

7

Our box is actually running ROS 6.7 with bootloader 3.10. Both SFP+ port are used, communication is running but no lights.

8

What do you see in “/system led print”? Possibly default config for leds might have been corrupted.

9

output is empty

/system led print
Flags: X - disabled, * - default 
 #    TYPE                     INTERFACE                                                                        LEDS
10

Try re-adding led configuration.

/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

11

nope…

[admin@felk-fw] /system leds> set 0 disabled=no interface=te1 leds=eth0-led1 type=interface-speed 
no such item

[admin@felk-fw] /system leds> set 2 disabled=no interface=te1 leds=eth0-led2 type=interface-activity       
no such item

[admin@felk-fw] /system leds> set 3 disabled=no interface=te2 leds=eth1-led1 type=interface-speed          
no such item

my 10GbE interfaces are named te1, te2 :slight_smile:

12

In that case it would be good to upgrade this unit to v6.11. And check leds there, if they are not working there and leds are not avaialble for configuration then we would like to get supout file from this device.

13

this is productional, mission critical box, it is save to upgrade to 6.11 ? :slight_smile:

14

So, I upgraded to the ROS 6.11, but attempts to restore default LED config in console still fails with: no such item, but i was able to add configuration in the Winbox dialog LEDs.

[admin@felk-fw] /system leds> set 1 disabled=no interface=te2 leds=eth1-led2 type=interface-speed 
no such item

There is also some inconsistence between Winbox dialog and the console. Console offers type=interface-speed, but there is no such option in the Winbox LEDs dialog. When configuration is created in Winbox it after a while becomes “default” (changes color) and I’m unable to change it anymore.
winbox-leds.png

15

try this

[admin@felk-fw] /system leds print
[admin@felk-fw] /system leds set 1 disabled=no interface=te2 leds=eth1-led2 type=interface-speed

16

nope … i tried this many times

[admin@felk-fw] > /system leds set 1 disabled=no interface=te2 leds=eth1-led2 type=interface-speed   
failure: This preset is read-only!