Network Time Protocol is based on a 32 x 32 bit number.  32 bits of digits and 
32 bits of decimals.  It rolls over once ever 136 years.  It will roll over in 
2036.

We had a bunch of calix shelves reporting Feb 7, 2036.  Calix kept saying 
things like we were getting bogus NTP etc.  Turns out that their clocks are 
getting set to 0x00000000h by something.  I doubt NTP is reporting that date.  

From: That One Guy /sarcasm 
Sent: Tuesday, October 18, 2016 2:28 PM
To: af@afmug.com 
Subject: Re: [AFMUG] OT DHCP update

my helmet is at the shop right now, so forgive my ignorance. but what?

On Tue, Oct 18, 2016 at 3:26 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  Yep, this could be like Y2K.  Once the clock rolls, I don’t think NTP yet has 
a field showing epoch number so how do you differentiate between 1900 and 2036?

  From: Paul Stewart 
  Sent: Tuesday, October 18, 2016 2:23 PM
  To: af@afmug.com 
  Subject: Re: [AFMUG] OT DHCP update

  Clock rolls over …  


    On Oct 18, 2016, at 4:13 PM, Chuck McCown <ch...@wbmfg.com> wrote:

    A few weeks ago I was requesting help in thinking through some DHCP lease 
issues.  Turns out, we think, that there were some Calix system clock 
fruitiness.

    Anyone care to guess what is magic about February 7, 2036?





-- 

If you only see yourself as part of the team but you don't see your team as 
part of yourself you have already failed as part of the team.

Reply via email to