Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.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.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Jan 16, 2016 Severity: 3-Major Related Article:
K08911351
Even though 'auto-sync enabled' and 'save-on-auto-sync true' are set on a device group which has a partition assigned to it, creating an LTM DNS object in the partition is successfully transmitted to the running configuration of the peer device, but not written to bigip.conf.
Changes are not written to conf files as expected.
1. auto-sync and save-on-auto-sync enabled for device group. 2. The device group has a partition assigned to it. 3. Creating a ltm dns partition object.
Save configuration manually at regular intervals on peer box.
Fixed issue where ltm dns objects are not being saved to their proper partition bigip.conf files when in a partition other than /Common/. This means that partitioned objects will be saved automatically when save-on-auto-sync is enabled for corresponding device groups. This affects ltm dns nameservers, zones, and tsig-keys.
LTM DNS objects (zones, tsig-keys, and nameservers) are now partitioned, so they will be saved to their corresponding partitons bigip_gtm.conf file under /config/partitions/. Because these objects are now partitioned, it also means user permissions to read / modify these objects will match the user permissions assigned to that partition.
