Last Modified: Jul 28, 2026
Affected Product(s):
F5OS F5OS-A
Known Affected Versions:
F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-A 1.8.4, F5OS-A 1.8.4-HR1
Fixed In:
F5OS v2.0.0
Opened: May 16, 2024 Severity: 3-Major
In Platform Event Log (r10k/r5k) and System Event Logs (r4k/r2k) there was a difference in how the timestamps were reported. In r4k/r2k appliances, a time zone suffix was added causing confusion with when events occurred.
There is no functional impact to this difference.
On F5OS appliance running 1.8 or lower the output from the different platforms is is different. Output format for r10k/r5k: [root@appliance-1:Active] ~ # docker exec platform-hal psf call GET:lop/pel direction | event | sequence | sequenceNext | severity | severityId | slotID | slotId | source | timestamp -------------+----------------------------------------------------+----------+--------------+----------+------------+--------+--------+--------+---------------------- Na | ASW_3 action: fan step 3 | 52239 | 52240 | Info | 6 | 255 | 255 | AOM | 11/05/2024 01:00:20 Output format for r4k/2k: [root@appliance-1:Waiting for cluster service] config # docker exec platform-hal psf call GET:bmc/sel evMRev | event | eventData | eventDir | eventType | nextRecord | recordNumber | recordType | sensorNumber | sensorType | severity | sourceId | timestamp ---------+--------------------------------------+------------------------+------------+-----------------+------------+--------------+------------+--------------+-----------------------+----------+----------+-------------------------------- 4 | | [0xf7 0x1 0x1 ] | Asserted | Sensor-specific | 4 | 3 | 0x2 | #b | System Boot Initiated | Info | BMC | 2024-10-15 16:05:36 +0000 UTC
None
After upgrading to F5OS 2.0 or later, the output for PEL and SEL timestamps will be the same.