Loading...
Loading...
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
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.