Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.4.1, 11.5.1, 11.5.2, 11.5.3, 11.6.0, 12.0.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0, 12.0.0 HF1, 11.6.1, 11.5.4, 11.4.1 HF10
Opened: Aug 05, 2015 Severity: 3-Major Related Article:
K17388
After performing a configuration merge load (for example, "tmsh load sys config merge ...") that changes an existing pool's monitor, old monitor instances may not get deleted. This can result in a system generating monitor requests that are no longer part of the configuration. It can also result in the system logging messages such as the following: err mcpd[8793]: 01070712:3: Caught configuration exception (0), Can't find monitor rule: 42.
Multiple monitor instances may be active on some pool members. This may result in incorrect monitoring status.
Pools with monitors configured must exist. The merge load must replace the pool's monitor.
Once a system is affected by this issue, the misbehavior can be resolved by doing the following: 1. Save and re-load the configuration to correct the incorrect information in mcpd: tmsh save sys config partitions all && tmsh load sys config partitions all 2. Restart bigd: On an appliance: bigstart restart bigd On a chassis: clsh bigstart restart bigd
Ensure that all relevant monitor instances are deleted when replacing a pool's monitor.