Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0, 12.1.3.4
Opened: Jun 09, 2016 Severity: 4-Minor
The default configuration for SNMP process monitoring causes an error of "Too many bigd running", and "No tmm process running". snmpwalk -c public -v 2c localhost prErrMessage UCD-SNMP-MIB::prErrMessage.1 = STRING: Too many bigd running (# = 2) ... UCD-SNMP-MIB::prErrMessage.6 = STRING: No tmm process running
SNMP monitoring of system health incorrectly reports error conditions.
Depending on system capacity and configuration, more than one "bigd" process may be running, resulting in the incorrect report of "Too many bigd running". The system does not properly count instances of the "tmm" process. In older releases, the system always detected a single "tmm" process, even if more than one existed. In the affected releases, no "tmm" process is detected.
For the 'bigd' problem, the administrator can change the the process-monitor max-processes to allow for more instances of "bigd". For example: (tmos)# modify sys snmp process-monitors modify { bigd { max-processes infinity } } max-processes should be set to the same value as the sys dbvar bigdb.numprocs or "infinity" if the dbvar is set to "0", allowing bigd to dynamically adjust the number of processes. For tmm process count (twos)# modify sys snap process-monitors modify { tmm { process tmm.0 max-processes 1 } }
The system now correctly counts the number of TMM process instances, which is not the same as the number of TMM threads. but is based on the hardware capabilities. Existing/upgraded configurations need to manually adjust the bigd 'max-processes' attribute as described in the Mitigation section. New configurations will be configured appropriately.