Bug ID 807337: Config utility (web UI) output differs between tmsh and AS3 when the pool monitor is changed.

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 16.0.0,, 16.0.1

Fixed In:
16.1.0,, 15.1.1,

Opened: Jul 19, 2019

Severity: 3-Major


When a transaction attempts multiple commands (delete, create, modify) for the same object in the same transaction, the results can be unexpected or undefined. A common example is: 'transaction { delete key create_if key }' where the transaction attempts 'delete key', and then 'create_if key', which unmarks the delete operation on the key (so in this case the key remains unmodified). In other cases it is possible that monitoring stops for the associated object, such as for: pool, pool_member, node_address, monitor.


The GUI shows misleading info about the pool monitor.The monitor-related object may be unchanged, or monitoring may stop for that object.


A user-initiated transaction attempts multiple commands for the same monitor-related object (such as delete, create, modify).


Transactions modifying a monitor-related object (pool, pool_member, node_address, monitor) should perform a single command upon that object (such as one of: 'delete', 'create', 'modify').

Fix Information

Behavior is as-expected when a transaction executes multiple commands (such as 'delete', 'create', 'modify') upon the same monitor-related object (pool, pool_member, node_address, monitor).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips