A report on another minor bug.
While delving into log outputs I found that the switches and (possibly the AP as well) timestamped entries one hour behind those of the Route10. I believe entries for Route10 show the correct time. I’m at UTC+1 if that might have any impact, even though timestamps showed the correct offset.
Probably only a minor issue, but I got a bit confused at first and who knows if this might have any adverse effects elsewhere in the system.
I can confirm that APs and switches currently log in UTC, whereas Route10 is local. Beyond that, I will have to follow up. Personally I think they should be the same (emphasis on that being a personal comment).
That said, if multiple devices are logging to a syslog collector, they’ll still be in order, just reading the time stamps can be jarring, per se. I’ll circle back.
I’m always confused by timestamps and timezones. But, from what I see, when the clock on the wall here says 4 P.M. local time in CET (Central European Time) timezone, timestamps say for
so I would say Route10 shows correct local time and correct timezone (offset +1 from UTC) while APs and switches show wrong local time (one hour behind, which happens to correspond to UTC) but correct timezone (offset +1 from UTC).
That’s kind of what I would have thought as well as they (the network devices) would most certainly physically be in the same location (timezone).
Yes, that’s what caught my eye.
This one is now, supposedly, solved in Route10, firmware 1.4h.
Though, I haven’t confirmed it myself yet.
@Alta-MikeD, seems like there are inconsistencies still, and I believe things actually got worse.
For example, timestamp 2025-07-26T22:37:11+02:00 occured at wall clock time 00:37. Timestamp indicates 22:37 at CEST (+2 hrs from UTC), so we are 2 hrs behind for Route10. This is consistent for all network devices now.
Unfortunately, this has, if understand it correctly, not fixed the error, but rather introduced an error for Route10 syslog entries (which was actually correct) and the issue for other network devices remain.
If it would be presented as UTC (as stated in the firmware release notes), it should have shown 2025-07-26T22:37:11+00:00 or 2025-07-26T22:37:11Z.
If it was in local time (CEST), it should have been 2025-07-27T00:37:11+02:00.
All according to ISO8601, e.g. ISO 8601 - Wikipedia.