RB3011: System clock looses seconds and NTP not working

Hardware MikroTik hardware general
1

Hi,

I’m using a brand-new RB3011 with ROS 6.33.3 with the additional ntp package. I have enabled both ntp client and server, hence devices on the LAN get their time via the RB as ‘proxy’.

Unfortunate, the RB clock is slow by about 80s per hour. Initially, it gets the right time via ntp client (not sntp), but even if I can log further ntp packets via the firewall, they don’t seem to adjust the internal clock.

I know that the RB is not a ‘reference’ clock, but I have not seen such a large clock drift with other embedded devices apart that the ntp adjustment is not working.

Any hints on how to debug this?

2

I have the same problem…

3

same here with 6.33.5 on RB3011
but not with other devices, only with “arm” (tested against tile, ppc, mips-be and smips)

workaround script:
/system ntp client set enabled=no
/system ntp client set enabled=yes

4

Get the same issue with
RB3011UiAS-RM, RouterOS 6.33.5
NTP Client enabled but time is dramatically slow. More than 20 minutes per several hours.

There are several MIKROTIK in the same network:

  1. RB2011UiAS-2HnD-IN
  2. mAP-2n
  3. caP-2n
  4. RB3011UiAS-RM
    All have RouterOS 6.33.5, all have NTP Client with 2 identical ntp servers.
    All devices except RB3011UiAS-RM have correct time. RB3011UiAS-RM is slow, very slow.

Disabling/Enabling NTP Client at RB3011 not always gets correct time. Sometimes I must do it twice or more.

THIS IS CRITICAL ISSUE INDEED.

5

we know the issue and we are working on it.

6

I hoped you would fix this issue in ROS 6.34 but the bug is still the same. So it seems the problem is very serious?

7

Please Mikrotik, ask to this question and update the status of this bug because it’s extremely serious and seems that you’re selling defective hardware. I hope you can fix it via firmware update or ROS update. I really hope that. Thanks for your hard work.

8

I confirm the issue.

With 6.35rc26 the problem still persists.

Every 15minutes the clock is off by ~21seconds.
rb3011-clock-drift.png

9

try 6.35rc29

10

It looks good so far.

Thanks! That was fast :slight_smile:

11

If you define “fast” as “less than three months”, yes. Actually I’m a bit worried about software QA at Mikrotik…

12

I meant fast in response to my report of the issue. Usually my reports or requests are piped to /dev/null :stuck_out_tongue: