Cloud Managed Networks

Which log are you reading: the AP's own (show log system), an external syslog server, or the events in Central? My read is that the AP stamps its log lines in UTC whatever zone you set, and the zone only changes what show clock prints and when schedules fire. None of the AOS 10 pages say the zone applies to log timestamps, so treat that as my read rather than documented behaviour.

Here's a quick check. If show clock gives you CEST while the log lines sit two hours behind, the clock's fine and only the stamping is off. Then convert at the collector (most syslog servers can take the incoming time as UTC and show local), or use Central's event view, which as far as I know shows your browser's local time.

If you set the zone from the AP CLI, set it in the group's System settings in Central as well (Timezone, just above NTP Server): https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/aos10x/cfg/aps/conf_sys_params.htm

------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
www.wei.com

- - -
The comments I post here are my own, and not my employers
If my post was useful accept solution and/or give kudos
Personal Blog: www.networkfieldnotes.com
- - -
------------------------------

Both the logs directly on the AP (CLI) and in my remote syslog (loges shipped there). They are all stamped UTC time even though I'm en CEST.
"Show clock" on the AP also shows UTC time regardless of what I do. "show clock timezone" does show Europe/Copenhagen (CEST) as expected.

I have hundreds of different systems (switches, firewalls and APs from different vendors), and the Aruba AOS APs are the only only ones incapable of setting the correct time on anything. It can't be intended you have to setup converter logic at the Syslog receiver, or instruct admins in "interpreting" the local log with a time offset?

Original Message:
Sent: Sep 29, 2026 09:16 AM
From: DB86
Subject: AOS 10 Timezone and logged time

Which log are you reading: the AP's own (show log system), an external syslog server, or the events in Central? My read is that the AP stamps its log lines in UTC whatever zone you set, and the zone only changes what show clock prints and when schedules fire. None of the AOS 10 pages say the zone applies to log timestamps, so treat that as my read rather than documented behaviour.

Here's a quick check. If show clock gives you CEST while the log lines sit two hours behind, the clock's fine and only the stamping is off. Then convert at the collector (most syslog servers can take the incoming time as UTC and show local), or use Central's event view, which as far as I know shows your browser's local time.

If you set the zone from the AP CLI, set it in the group's System settings in Central as well (Timezone, just above NTP Server): https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/aos10x/cfg/aps/conf_sys_params.htm

------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
www.wei.com

- - -
The comments I post here are my own, and not my employers
If my post was useful accept solution and/or give kudos
Personal Blog: www.networkfieldnotes.com
- - -
------------------------------

Maybe it should be said that AOS10 APs logs in general is a complete mess as it logs in several different formats (some completely nonstandard), and every AP has hundreds of complete meaningless garbage events everyday about something that is unfixable and quite useless: fx:

snmp[4950]: [4950]: PAPI_Send: To: 127.0.0.1:15200 Type:0x4 Timed out

Incorrect format for message type 0:5:0:0:127.0.0.1:8236:0x422 reply unexpected

cli[4877]: [4877]: PAPI_Send: To: 127.0.0.1:8236 Type:0x4 Timed out

There seems to be little interest from HPE in fixing the log/syslog output from AOS10 as this has been a massive issue since its release.
I guess no-one at HPE themselves use the syslog output.

Both the logs directly on the AP (CLI) and in my remote syslog (loges shipped there). They are all stamped UTC time even though I'm en CEST.
"Show clock" on the AP also shows UTC time regardless of what I do. "show clock timezone" does show Europe/Copenhagen (CEST) as expected.

I have hundreds of different systems (switches, firewalls and APs from different vendors), and the Aruba AOS APs are the only only ones incapable of setting the correct time on anything. It can't be intended you have to setup converter logic at the Syslog receiver, or instruct admins in "interpreting" the local log with a time offset?

Original Message:
Sent: Sep 29, 2026 09:16 AM
From: DB86
Subject: AOS 10 Timezone and logged time

Which log are you reading: the AP's own (show log system), an external syslog server, or the events in Central? My read is that the AP stamps its log lines in UTC whatever zone you set, and the zone only changes what show clock prints and when schedules fire. None of the AOS 10 pages say the zone applies to log timestamps, so treat that as my read rather than documented behaviour.

Here's a quick check. If show clock gives you CEST while the log lines sit two hours behind, the clock's fine and only the stamping is off. Then convert at the collector (most syslog servers can take the incoming time as UTC and show local), or use Central's event view, which as far as I know shows your browser's local time.

If you set the zone from the AP CLI, set it in the group's System settings in Central as well (Timezone, just above NTP Server): https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/aos10x/cfg/aps/conf_sys_params.htm

------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
www.wei.com

- - -
The comments I post here are my own, and not my employers
If my post was useful accept solution and/or give kudos
Personal Blog: www.networkfieldnotes.com
- - -
------------------------------

"show clock" itself prints UTC while "show clock timezone" reports Copenhagen, so the zone is stored but never applied to the running clock, and the logs just follow the clock. Agreed, that isn't something you should have to fix at the collector. One correction to my first reply: the AOS-10.x CLI Reference says the AOS 10 CLI only has show commands (https://arubanetworking.hpe.com/techdocs/CLI-Bank/Content/aos10/preface/about-this-guide.htm), so the zone can only come from the Timezone field in the group's System settings in Central.

Is it set there, and which AOS 10 build are the APs on? If the group has it and show clock still reads UTC, that's a TAC case: send show clock, show clock timezone and show version from one AP.

The PAPI_Send timeouts to 127.0.0.1 are the AP's own processes talking to each other, so there's nothing to fix on your end. The Classic Central logging page sets Syslog Facility Levels per facility, Notice by default (https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/aos10x/cfg/aps/conf_log_servers.htm). I'd try AP-Debug and System at Warning.

Maybe it should be said that AOS10 APs logs in general is a complete mess as it logs in several different formats (some completely nonstandard), and every AP has hundreds of complete meaningless garbage events everyday about something that is unfixable and quite useless: fx:

snmp[4950]: [4950]: PAPI_Send: To: 127.0.0.1:15200 Type:0x4 Timed out

Incorrect format for message type 0:5:0:0:127.0.0.1:8236:0x422 reply unexpected

cli[4877]: [4877]: PAPI_Send: To: 127.0.0.1:8236 Type:0x4 Timed out

There seems to be little interest from HPE in fixing the log/syslog output from AOS10 as this has been a massive issue since its release.
I guess no-one at HPE themselves use the syslog output.

Both the logs directly on the AP (CLI) and in my remote syslog (loges shipped there). They are all stamped UTC time even though I'm en CEST.
"Show clock" on the AP also shows UTC time regardless of what I do. "show clock timezone" does show Europe/Copenhagen (CEST) as expected.

I have hundreds of different systems (switches, firewalls and APs from different vendors), and the Aruba AOS APs are the only only ones incapable of setting the correct time on anything. It can't be intended you have to setup converter logic at the Syslog receiver, or instruct admins in "interpreting" the local log with a time offset?

Original Message:
Sent: Sep 29, 2026 09:16 AM
From: DB86
Subject: AOS 10 Timezone and logged time

Which log are you reading: the AP's own (show log system), an external syslog server, or the events in Central? My read is that the AP stamps its log lines in UTC whatever zone you set, and the zone only changes what show clock prints and when schedules fire. None of the AOS 10 pages say the zone applies to log timestamps, so treat that as my read rather than documented behaviour.

Here's a quick check. If show clock gives you CEST while the log lines sit two hours behind, the clock's fine and only the stamping is off. Then convert at the collector (most syslog servers can take the incoming time as UTC and show local), or use Central's event view, which as far as I know shows your browser's local time.

If you set the zone from the AP CLI, set it in the group's System settings in Central as well (Timezone, just above NTP Server): https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/aos10x/cfg/aps/conf_sys_params.htm

------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
www.wei.com

- - -
The comments I post here are my own, and not my employers
If my post was useful accept solution and/or give kudos
Personal Blog: www.networkfieldnotes.com
- - -
------------------------------