Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AOM
Known Affected Versions:
10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Opened: Apr 02, 2015 Severity: 4-Minor
When configuring the time zone for a BIG-IP system, the time zone selection may not be applied to the AOM subsystem. In this case, the time zone for the AOM subsystem will be set to UTC instead. For example: # tmsh lis sys ntp sys ntp { timezone US/Pacific } # date Fri Apr 3 11:01:55 PDT 2015 # ssh aom date Fri Apr 3 18:01:55 UTC 2015 # tmsh lis sys ntp sys ntp { timezone Japan } # date Fri Apr 3 07:32:08 JST 2015 # ssh aom date Thu Apr 2 22:32:08 UTC 2015
Timestamps associated with events logged by the AOM may be encoded to a different time zone (UTC) from events logged by the BIG-IP/EM host system. In circumstances where AOM-generated logs are analyzed and compared with BIG-IP/EM logs, the time zone differences will have to be reconciled/accounted-for manually.
This issue may affect the following F5 appliances which use the "AOM" type of Always-On Manager subsystem: BIG-IP 1600, 3600, 3900, 6900, 6900S, 8900, 8950, 8950S, 11000, 10050 appliances Enterprise Manager EM-4000 appliance
In circumstances where AOM-generated logs are analyzed and compared with BIG-IP/EM logs, the time zone differences will have to be reconciled/accounted-for manually.
None