Branch router clocks running slow

  • 1
  • Question
  • Updated 5 years ago
  • Answered
While looking at logs from one of our branch routers I noticed, it's clock was about 5 minutes slow. I dug further into the issue and found that in a sample of 5 of our branch routers, all the clocks were 5-15 minutes slow. They do have NTP configured (to HiveManager every day) and it does appear to correct itself and then start to drift again.

Also, when I rebooted a branch router as a test to see if it make an ntpclient connection on boot up, the clock went back to 1970-01-01 00:00:00 before ntpclient corrected the time.

Looking for suggestions and feedback how the clock should work.
Photo of Fraser Hess

Fraser Hess

  • 60 Posts
  • 7 Reply Likes
  • unsure

Posted 5 years ago

  • 1
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Increase the frequency of your clock sync'ing. Personally, I do hourly.

The branch routers were designed to be Internet-attached equipment, and since we can get the internal clock sync'd with trustworthy external sources, we chose to reduce our costs by not putting a real-time-clock circuit into these devices.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
If the drift is relatively constant on a per device basis, you could calibrate for it in software through NTP syncs that look at the drift deltas. It is probably more work than it is worth though and you could find the drift varies with temperature, or some other variable.

Yeah, just sync more often...