Last Modified: Mar 22, 2025
Affected Product(s):
BIG-IP AFM, APM, ASM, AVR, DNS, Install/Upgrade, LTM, PEM, TMOS
Known Affected Versions:
16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2
Opened: Jan 15, 2025 Severity: 4-Minor
On Microsoft Hyper-V BIG-IP Virtual Editions and on TMOS versions from 14.1.0 and more recent, if the configuration file /etc/adjclock is configured with the "LOCAL" keyword, after a reboot the VE system clock picks the wrong time zone from the hypervisor (hardware) clock. This might result in a big system clock time skew on the VE, that lasts until the VE synchs its time with the correct time from the NTP servers configured under "tmsh sys ntp". Symptoms: After a reboot: - the /var/log/dmesg configuration log file contains a line similar to this one: [ 1.754030] systemd[1]: RTC configured in localtime, applying delta of -360 minutes to system time; - the system time is changed to one or more hours in the future.
A significant system clock time skew, that lasts until the VE synchs its time with the correct time from the NTP servers configured under "tmsh sys ntp". Some services like bigd monitoring can be affected.
- BIG-IP Virtual Edition running on a Microsoft Hyper-V hypervisor. - The Virtual Edition is upgraded from a TMOS version older than 14.1.0 to a version equal or newer than 14.1.0 . As a consequence of the upgrade, the "/etc/adjclock" system file is configured with the "LOCAL" setting when it shouldn't. - The Virtual Edition is rebooted.
Edit the "/etc/adjtime" configuration file and remove the "LOCAL" line.
None