Re: REMINDER: LEAP SECOND

[Mike Hammett <nanog () ics-il net>]

It looks to have only affected the CCR line and only those running the NTP and not the SNTP package. 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 


----- Original Message -----

From: "Guilherme Ganascim" <guilherme.ganascim () persistelecom com br> 
To: nanog () nanog org 
Sent: Tuesday, June 30, 2015 8:08:28 PM 
Subject: Re: REMINDER: LEAP SECOND 

I had problems with Leap Second with mikrotik in versions 6.29.1, 6.28, 6.5 and other versions. 

Configured NTP Client in all of them. 

Anyone else had this problem? 


> On Jun 19, 2015, at 19:30, Baldur Norddahl <baldur.norddahl () gmail com> wrote: 
>
> On 19 June 2015 at 23:58, Harlan Stenn <stenn () ntp org> wrote: 
>
> > Bad idea. 
> >
> > When restarting ntpd your clocks will likely be off by a second, which 
> > will cause a backward step, which will force the problem you claim to be 
> > avoiding. 
>
> If you are afraid that your routers will crash due to the leapsecond, then 
> it would help to disable the thing that you think will crash them. Even if 
> the router crashes when you enable it later on. Because then you can have 
> one router crash at a time and have it happen in a service window where you 
> are ready for it. Instead of having all routers in your whole network crash 
> at exactly the same time. 
>
> Regards, 
>
> Baldur