Hi all,
I have 2 routerboards in one pop which have their times reset to 00:00:00 Jan 01 1970 everytime they are rebooted. I have nearly 10 routerboards running MT for over 1 year, but haven’t seen such problem before.
Does it have anything to do with CMOS battery? Anyone got suggestions pls?
Thanks.
use NTP and synchronise the time with a reliable time server
That would be what the battery was there for. Try replacing them.
Clock doesn’t work with any of our 12 RB532 units deployed - and NTP doesn’t work either. This is a serious bug.
if you have correct NTP client configuration, clock works fine in RB500.
Yes, the NTP server works. It is the national NTP server for New Zealand. All our Debian boxes use it. No, it doesn’t respond to ping.
[admin@ara-imperial] > /system resource print
uptime: 1w7h32m33s
free-memory: 18936kB
total-memory: 30384kB
cpu: “MIPS 4Kc V0.10”
cpu-frequency: 266MHz
cpu-load: 7
free-hdd-space: 98976kB
total-hdd-space: 126976kB
write-sect-since-reboot: 0
write-sect-total: 0
[admin@ara-imperial] > /system ntp client print
enabled: yes
mode: unicast
primary-ntp: 131.203.16.6
secondary-ntp: 0.0.0.0
status: started
[admin@ara-imperial] > /system clock print
time: 07:32:03
date: jan/08/2000
time-zone: +12:00
[admin@ara-imperial] >
Johnbrewer,
Are you in the Chathams or somewhere in Year 2000. Your NTP server has started, but time has not been set. It should be saying
status: synchronized and correct time and year.. Maybe it hadnt had time.
KenK
Nope, just in NZ. GMT +12.
Clocks on our 12 RB532 boxes still don’t work. Can anyone help?
There are no batteries on RB500 series routers. You have to use NTP servers or else the clock is reset after every reboot.
Ken
Maybe.
If you use Winbox, using “Tools” ping your NTP server.
If you get “no route to host” or “timeout”, using “IP” “Routes” add a static route to 0.0.0.0 using your default gateway.
I just came across your post, hope this helps.