[181714] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Guilherme Ganascim)
Wed Jul 1 08:58:18 2015
X-Original-To: nanog@nanog.org
From: Guilherme Ganascim <guilherme.ganascim@persistelecom.com.br>
Date: Tue, 30 Jun 2015 22:08:28 -0300
To: "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <CAPkb-7AG8vpHhVB_Vsq2xurO7tBj71X7HjOsDKY-fOuesKHFNA@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
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:
>=20
> On 19 June 2015 at 23:58, Harlan Stenn <stenn@ntp.org> wrote:
>=20
>> Bad idea.
>>=20
>> 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.
>>=20
>=20
> 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.
>=20
> Regards,
>=20
> Baldur
