Loading...
Loading...
Prior to v12.1.3.4, the 'merge' command merged a specified config with the existing config, replacing certain conflicting values. In this release, the merge command operates differently, so there is a new command, 'replace', to now perform the operation previously accomplished with 'merge'.
Operation does not work like it did in previous releases.
Running the following command: tmsh load /sys config file <scf-filename> merge
None.
This release restores the merge functionally from v12.x and earlier with a new tmsh verb: replace. The new TMSH command is as follows: tmsh load sys config file <filepath> replace
This release restores the merge functionally from v12.x and earlier with a new tmsh verb: replace. The new TMSH command is as follows: tmsh load sys config file <filepath> replace The merge command now operates as follows: -- Previously: if a top-level object (virtual server) existed in the config and also in the merge file, the top-level object was replaced. -- Now: if a top-level object (virtual server) exists in both, the top-level object is recursively merged. (Pool members are merged together. LTM virtual server profiles are merged together (appended vs. replace-all-with)).
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.