Bug ID 1022637: A partition other than /Common may fail to save the configuration to disk

Last Modified: Feb 07, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:
17.0.0,, 15.1.5,, 13.1.5

Opened: Jun 01, 2021

Severity: 3-Major


A mismatch between the running-configuration (i.e. what is returned by "tmsh list ...") and the saved-configuration (i.e. what is stored in the flat configuration files) for a partition other than /Common, despite a "tmsh save config" operation was just performed (either by the user or as a result of a config-sync).


Should a BIG-IP Administrator notice the mismatch, the only immediate impact is confusion as to why the config save operation was not effective. However, as the flat config files are now out-of-date, performing a config load operation on a unit in this state will resurrect old configuration objects that had been previously deleted. On an Active unit, this may affect traffic handling. On a redundant pair, there is the risk that the resurrected objects may make it to the Active unit after a future config-sync operation.


- One or more partitions other than /Common exist on the system. - One or more of said partitions have no more configuration objects defined in them (i.e. are empty). - A config save operation similar to "tmsh save sys config partitions { Common part1 [...] }" occurs, either manually initiated by an Administrator or as a result of a config-sync operation (in which case the device-group must be configured for manual synchronization).


If you notice the mismatch, you can resolve it by performing a config save operation for all partitions (i.e. "tmsh save sys config").

Fix Information

Non /Common partitions now get saved to disk as intended.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips