It could be everything. If this happened only to me and nobody else, then it's either an attack directed to my network or something triggered by my setup.Yours CCRs could be hacked earlier and poisoned today.
2015-04-01T01:59:59.003687+02:00 fe-a-01 kernel: [9475817.256006] Clock: inserting leap second 23:59:60 UTC
No news. I wrote a script that connects and removes NTP servers from the configuration of every CCR router on the last hour / last day of the month and adds it back an hour after the first day of the month.Any news on this ?
Well at about 00:00 UTC we had pretty much all of our CCRs crash and lock solid .. at the same timeTonight a leap second will be introduced by NTP servers from all the world. I disabled NTP on all CCRs, excluding a few ones that I have at hand. Let's see how it is going this time.
My routers have 6.26, 6.27, 6.28, 6.29, 6.29.1 and they all crashed. All kinds of CCR (1009, 1016, 1032 on various flavors).Same here
3x CCR1009's all hard locked no winbox/serial. Had to go on-site and power cycle.
2x Running 6.29.1 + NTP package (whether that makes any diff). And 1x running latest rc22.
OK, first of all sorry about previous joke poster, cause looks like i had similar problem, but only on few CCRs.
Am i right to say that only CCRs with NTP package installed and configured was affected?
And all were synchronized (configured) to public server?yes, it seems so, i got v6.27 which NTP package installed and the CCR was crashed.
but the others which have v6.27 without NTP package installed, they are normal.
but some of my CCR using v6.19 with NTP package installed are not crashed.
Most of my CCRs don't have the NTP package installed, and they all crashed badly.Am i right to say that only CCRs with NTP package installed and configured was affected?
you can also use "IP Cloud" automatic time. It will not be as precise, within 1-2 seconds usually.I have one ccr (ccr1036-8g-2s+) running BGP, OSPF, OSPF3 on v6.19 (uptime 200+ days)
Yesterday, I saw this thread while searching for possible issues with the upcoming leap second,
disabled the ntp client on time.
It did not crash.
Maybe the time on the router is not that important,
maybe, we could let it disabled?
Could a time drift cause any problems for example BGP?
of course. but better than no NTP at allHaving the time synchronized is a *must*, because otherwise it's difficult (if not impossible) compare logs of multiple devices, and in a complex network it helps debug troubles quickly.
Normis ip cloud time synchronization is not an option for many reasons, and it's not always applicable.