Bug ID 478448: LTM v11.4.1 device time-zone is not updated upon timezone change when single configuration file (SCF) restored

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
12.0.0

Opened: Sep 08, 2014
Severity: 3-Major
Related AskF5 Article:
K17016

Symptoms

The command 'tmsh show cm device' still shows old timezone after load single configuration file (SCF) with timezone change.

Impact

The device timezone shows incorrect information.

Conditions

Check current timezone, say default timezone is PDT # tmsh show cm device will show time zone PDT <- newer versions say America/Los_Angeles Change timezone to JST <- and Japan # tmsh modify sys ntp timezone JST Check cm device time-zone again, it will still show PDT.

Workaround

After loading an SCF, issue 'tmsh modify sys ntp timezone timezone_name' from the command line, where <timezone> is the same value as that which is found in the SCF file. Otherwise, if just modifying the sys.ntp.timezone, issue the command "tmsh modify sys ntp timezone timezone_name' command twice, where <timezone> is the same in both instances. Also, 'timezone' values must be able to be found in the /usr/share/zoneinfo directory. They are now used in long form, for example, JST = Japan.

Fix Information

cm.device is now updated with the same information as sys.ntp.timezone upon modification or load of SCF file.

Behavior Change