EAP610 Wrong Time in Logs

I am using the EAP610 with an OC300 hardware controller. In the controller, I enabled client detail logging and I now receive the AP's logs on my syslog server. However, the time is off by 1 hour due to DST. DST was set manually in the controller, both under global and site settings. I disabled DST in the controller and readjusted the time zone to add an hour. Now the EAP610 logs are correct. This appears to be a problem in the EAP610 firmware as logs from other devices, such as the controller and gateway display the correct time in their logs when DST is enabled.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @jra11500
Thank you for posting here.
You mentioned that it only appears on the EAP610.
To confirm, the logs from the EAP650 are correct, right?
If so, please download the EAP610 to version 1.5.0 for comparison testing.
This will help us determine if the issue is related to specific firmware or configuration settings, or something else.
Thanks.
Site View > Device page > choose the device EAP610 > Config > Manage Device > Custom Upgrade > Browse
- Copy Link
- Report Inappropriate Content
The issue is only with the EAP610 logs. The gateway and controller logs show the correct time. On another thread, I posted that I am not receiving any EAP650 logs.
I just downgraded the firmware in the EAP610, changed the time zone in the controller and enabled the manual settings for DST, and finally re-enabled client logging. The problem persists, i.e. the EAP610 logs are off by 1 hour.
- Copy Link
- Report Inappropriate Content
Hi @jra11500
May I ask how you determined there's a 1-hour time discrepancy in the EAP610 logs while the router and switch logs remain accurate?
Did you perform any simultaneous operations on these devices (e.g., a reboot) where the router/switch showed correct timestamps but the EAP610 displayed incorrect ones?
Alternatively, did you reboot the EAP610 at a specific time but found the logged reboot time was off by 1 hour?
Please provide details of the actual network activities to help us investigate. Thank you.
jra11500 wrote
The issue is only with the EAP610 logs. The gateway and controller logs show the correct time. On another thread, I posted that I am not receiving any EAP650 logs.
I just downgraded the firmware in the EAP610, changed the time zone in the controller and enabled the manual settings for DST, and finally re-enabled client logging. The problem persists, i.e. the EAP610 logs are off by 1 hour.
- Copy Link
- Report Inappropriate Content
The NAS Log Center keeps a separate log for each IP address that sends a log. I have separate logs for the ER706W (192.168.20.1), the OC300 (192.168.10.254), and the EAP610 (IP 192.168.10.11). The ER706W default LAN IP is 192.168.10.1 but it sends its logs to the NAS via its VLAN interface address.
The individual entries don't have to be the same entries as each log can be viewed in succession on the NAS GUI. Recent entries in each case are within minutes (if not seconds) of the PC time. As the EAP610 logs are sent every 5 seconds, it is easy to see that the timestamps are off by one hour when the controller is configured with DST settings. The EAP610 simply does not advance the clock by one hour if DST is active on the controller. Disabling the DST on the controller and setting the time to the next time zone fixes the timestamps. I just retested this and that is the way it is working. I did reboot the EAP610 several times to see if the problem would cure itself but no, the reboots did not fix the problem.
I do remember when the EAP610 was working in standalone mode before I installed the controller. There was a DST setting and it worked OK if my memory serves me correctly. It was only after the controller was installed that I noticed the time was wrong in the logs.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 187
Replies: 5
Voters 0
No one has voted for it yet.