Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
12.1.2, 12.1.1, 12.1.0, 12.0.0, 11.6.1, 11.6.0, 11.5.4
Fixed In:
12.1.3.6
Opened: May 30, 2017 Severity: 3-Major
Nested objects are removed when newer objects are merged in. Configuration objects can contain nested objects. The merge option for tmsh load sys config command expects the nested-objects passed in to be merged alongside existing objects. example: Initial configuration [root@plate:Active:Standalone] config # tmsh list ltm pool ltm pool test-pool-mcconfig { members { test-mc1:http { address 10.13.14.15 priority-group 1 session monitor-enabled state checking } test-mc2:http { address 10.13.14.16 priority-group 4 session monitor-enabled state down } } monitor tcp } Run load merge command: [root@plate:Active:Standalone] config # tmsh -m root@(plate)(cfg-sync Standalone)(Active)(/Common)(tmos)# load sys config merge from-terminal Enter configuration. Press CTRL-D to submit or CTRL-C to cancel. ltm pool test-pool-mcconfig { members { test-mc2:http { priority-group 0 } } } Loading configuration... root@(plate)(cfg-sync Standalone)(Active)(/Common)(tmos)# ^D New configuration, not merged: [root@plate:Active:Standalone] config # tmsh list ltm pool ltm pool test-pool-mcconfig { members { test-mc2:http { address 10.13.14.16 session monitor-enabled state down } } monitor tcp }
Configuration loss: Post merge the existing nested configuration objects are deleted.
Execute tmsh load sys config merge from-terminal command. The configuration contains nested objects. The configuration that is being merged in contains nested objects of the same type as the existing configuration.
None.
The behavior for the merge option of tmsh load sys config is corrected. The nested objects in the existing configuration are not deleted.