Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
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.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Feb 10, 2015
Severity: 3-Major
Related Article:
K16369
Monitored node/pool member flaps even when the services are not down.
Monitored node/pool member might flap even when the services are not down. This might require the bigd process to be killed and restarted.
With many thousands of monitor instances, bigd might reach a state where it cannot keep up with the load.
Increase probe times (decrease frequency) or switch to simpler monitor types (for example, ICMP or TCP Half-Open instead of HTTP or HTTPS).
Monitoring daemon, bigd, may now run as multiple processes for distributed monitoring load. Previously, bigd (the primary monitoring daemon) ran as a single instance per BIG-IP system. By default, the system now runs multiple bigd processes per BIG-IP system if there are enough processor cores to support doing so. Monitor instances are divided among the processes, allowing each to do a subset of the monitoring work. A new sys db variable has been added to control this behavior: Bigd.NumProcs. This variable defaults to 0, which instructs the system to select a reasonable default. When set to 1, bigd runs a single process, very much like it always has. Any value greater than 1, and less than or equal to the number of available processor cores, causes that number of bigd processes to be started. Note that bigd must be restarted with bigstart whenever this variable is changed.
Previously, bigd (the primary monitoring daemon) ran as a single instance per BIG-IP system. By default, the system now runs multiple bigd processes per BIG-IP system if there are enough processor cores to support doing so. Monitor instances are divided among the processes, allowing each to do a subset of the monitoring work. A new sys db variable has been added to control this behavior: Bigd.NumProcs. This variable defaults to 0, which instructs the system to select a reasonable default. When set to 1, bigd runs a single process, very much like it always has. Any value greater than 1, and less than or equal to the number of available processor cores, causes that number of bigd processes to be started. Note that bigd must be restarted with bigstart whenever this variable is changed.
