Last Modified: Feb 07, 2024
Affected Product(s):
BIG-IP LTM, TMOS
Known Affected Versions:
17.0.0, 16.1.3, 16.1.2.2, 16.1.2.1, 15.1.8, 15.1.7, 15.1.6, 15.1.5.1, 14.1.5, 14.1.4.6, 14.1.4.5, 13.1.5
Fixed In:
17.1.0, 16.1.4, 15.1.9
Opened: Jun 01, 2022 Severity: 3-Major
Log messages similar to the following may be observed in /var/log/ltm: bigip1 err mcpd[4783]: 01070712:3: Caught configuration exception (0), Invalid monitor rule instance identifier: 29. This may also result in a few unresponsive monitors in checking state. If this occurs on a VIPRION system or a multi-slot tenant on a VELOS system, one or more secondary blades may reboot repeatedly while logging messages similar to the following: err mcpd[####]: 01020036:3: The requested monitor instance (/Common/?????? ##.##.##.## ### ?????????) was not found. err mcpd[####]: 01070734:3: Configuration error: Configuration from primary failed validation: 01020036:3: The requested monitor instance (/Common/?????? ##.##.##.## ### ?????????) was not found.... failed validation with error 16908342.
-- A few monitor statuses may not be correctly reported. -- A few monitors may be unresponsive in checking state. -- On VIPRION or VELOS systems, one or more secondary blades may be unresponsive in a reboot loop.
The initial "requested monitor instance ... was not found" message may occur when: -- FQDN nodes exist on the configuration. -- A full config sync occurs. -- Device contains a fix for Bug ID 1017513. -- May happen regardless of bigd or in-tmm monitoring. In addition, the message "Configuration error: Configuration from primary failed validation" and secondary blade/slot reboot loop may occur on VIPRION or VELOS systems.
Force the MCPD process to reload the BIG-IP configuration. For more information refer K13030.
The monitors are responsive, no errors are recorded.