Community discussions

MikroTik App

Search found 5 matches

by lele
Tue Aug 25, 2015 4:07 pm
Forum: General
Topic: 6.31 on RB750, ethernet flapping
Replies: 0
Views: 515

6.31 on RB750, ethernet flapping

I have upgraded an RB750 to 6.31. Since the upgrade, one of the ethernet ports is flapping "no link"/"link ok" every 10 seconds and is obviously showing very poor performance. The log also registers link down, link up events. The LED stays lit. The ethernet in question is connect...
by lele
Thu Jul 02, 2015 12:38 am
Forum: General
Topic: Leap second bug present on TILE devices?
Replies: 49
Views: 12909

Re: Leap second bug present on TILE devices?

So, using NTP on CCR is sure to be the largest contributing factor, but it's not 100% limited to that scope. While unrelated bugs can't be ruled out, this specific issue is tied to the processing of a leap second event from the NTP subsystem to the linux kernel. So it can not happen if you are not ...
by lele
Wed Jul 01, 2015 9:29 am
Forum: RouterBOARD hardware
Topic: all CCR crashed
Replies: 40
Views: 10159

Re: all CCR crashed

Given what happened. I would try and simulate the addition of a leap second on the CCRs well before june 30.
Now, tell me I did not warn you.
by lele
Thu Apr 02, 2015 12:13 pm
Forum: RouterBOARD hardware
Topic: all CCR crashed
Replies: 40
Views: 10159

Re: all CCR crashed

There is at least a report of spurious leap seconds observed in Italy on march 31, 23.59.60, with a possible explaination: http://lists.ntp.org/pipermail/pool/2015-April/007338.html Given what happened. I would try and simulate the addition of a leap second on the CCRs well before june 30. cheers, L.
by lele
Thu Apr 02, 2015 1:33 am
Forum: RouterBOARD hardware
Topic: all CCR crashed
Replies: 40
Views: 10159

Re: all CCR crashed

Since it has been mentioned, there *is* something weird concerning leap seconds that *could* be related. We had a number of Linux hosts incorrectly adding a leap second last night: 2015-04-01T01:59:59.003687+02:00 fe-a-01 kernel: [9475817.256006] Clock: inserting leap second 23:59:60 UTC we are stil...