Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP Install/Upgrade, LTM
Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2, 11.4.1 HF10
Opened: Dec 15, 2014 Severity: 3-Major Related Article:
K16465
When configuring both a monitor and a child monitor, if the two monitors are saved in reverse order, the default monitor parameters will not be created. For example: ltm monitor tcp /Common/child { defaults-from /Common/parent destination *.990 interval 5 ip-dscp 0 time-until-up 0 timeout 16 } ltm monitor tcp /Common/parent { defaults-from /Common/tcp destination *:* interval 5 ip-dscp 0 time-until-up 0 timeout 16 } Some of the default parameters for the above configuration will not be created upon loading config.
Possible undefined behavior in bigd, and failing iControl calls. On performing a 'tmsh load sys config verify' the system posts an error message similar to the following: 01070740:3: Performance monitor /Common/http-a may not have the manual resume feature. Unexpected Error: Validating configuration process failed.
This occurs when there are at least two monitors, and the child custom monitor appears before the parent monitor. Must have a parent that derives from a root monitor, and a child that derives from the parent monitor.
A possible workaround involves switching the order of the monitors in the config file. This can either be accomplished manually, or by naming things in alphabetical order, such that the parent precedes the child: ltm monitor tcp /Common/aaa_parent { defaults-from /Common/tcp destination *:* interval 5 ip-dscp 0 time-until-up 0 timeout 16 } ltm monitor tcp /Common/bbb_child { defaults-from /Common/aaa_parent destination *.990 interval 5 ip-dscp 0 time-until-up 0 timeout 16 }
The system now handles a configuration in which a child custom monitor precedes the parent's, so that monitor parameters are constructed properly.
