01-23-2018 03:04 AM - edited 01-29-2018 07:20 AM
We have nine IAP-305 (version 184.108.40.206) which worked perfectly for a couple of weeks.
They are set up with one acting as Virtual Controller and the rest are slaves.
Last week they started rebooting intermittently. Not all at the same time, more like in sequence.
This is shown when we ask an AP to show the version:
Reboot Time and Cause: AP rebooted Thu Feb 7 07:58:16 UTC 2036; System clock is too far ahead of NTP sync result: 2085980296.100801 vs 1516703527.385096
I have checked and verified that when an AP reboots it did an NTP request just before the reboot. The NTP server resides in the same netwerk and responds to NTP requests. In fact, when I ask an AP to show its time it's always correct, like:
Current Time :2018-01-23 11:59:27
There is apparently no option to not use an NTP server and set the time manually.
Just for the heck of it we changed the NTP server from a Windows based one to a FreeBSD one. After that tried to use the default setting which uses ntp.pool.org. The reboots continue.
Any suggestions how to solve this issue?
Solved! Go to Solution.