Bug ID 955617: Cannot modify properties of a monitor that is already in use by a pool

Last Modified: May 29, 2024

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

Known Affected Versions:
16.1.0, 16.0.1.2, 16.0.1.1, 16.0.1, 16.0.0, 15.1.3, 15.1.2, 15.1.1, 15.1.0.5, 15.0.1.4, 14.1.4.3, 14.1.4.2, 14.1.4.1, 14.1.4, 14.1.3.1, 14.1.3, 13.1.4.1, 13.1.4, 13.1.3.6, 13.1.3.5

Fixed In:
17.0.0, 16.1.2.2, 15.1.5.1, 14.1.4.6, 13.1.5

Opened: Oct 14, 2020

Severity: 3-Major

Symptoms

If the monitor is associated with a node or pool, then modifying monitor properties other than the destination address is displaying incorrect error. For example, modifying the receive string results in following error: 0107082c:3: Cannot modify the destination address of monitor /Common/my_monitor This error should only be generated if the destination address of an associated monitor is being modified, but this error message is generated when other parameters are modified.

Impact

Monitor properties cannot be modified if they are in use by a pool.

Conditions

-- Monitor with alias address field as default properties. -- Pool containing a node or pool member. -- Monitor is attached to the pool.

Workaround

Remove the monitor, modify it, and then add it again.

Fix Information

Monitor properties can be modified even when the monitor is attached to the node or pool, updated values reflect in the node or pool.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips