Last Modified: Sep 13, 2023
Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
13.1.0, 12.1.3, 11.6.4
Opened: Apr 10, 2017 Severity: 2-Critical Related Article:
Related Article: K05052273
As a result of this issue, you may encounter one or more of the following symptoms: -- TMM generates a core file in the /shared/core directory. -- Your BIG-IP system logs a SIGFPE to the /var/log/tmm file at the same time TMM produces a core file and restarts. -- In one of the /var/log/tmm log files, you may observe error messages similar to the following example: notice panic: ../modules/hudfilter/hudfilter.c:1063: Assertion "valid node" failed. notice ** SIGFPE **
The BIG-IP system temporarily fails to process traffic while the TMM process restarts. If the BIG-IP system is configured for high availability (HA), the system fails over to a peer system.
This issue occurs when either of the following conditions are met: 1. -- Your BIG-IP system is configured to route traffic using a gateway pool. -- Your BIG-IP system is configured with DNS resolver. -- The gateway pool is configured with Action On Service Down = Reject or Action On Service Down = Drop. -- The pool monitor marks all members of the gateway pool as unavailable. -- An outstanding DNS request that is pending response. 2. -- Your BIG-IP system is not configured to route traffic using a gateway pool. -- Your BIG-IP system is configured with DNS resolver. -- All pools are configured with Action on Service Down = None.
For the set of Conditions defined in the first scenario, you can use the following workaround: Set service-down-action to Action On Service Down = None or Action On Service Down = Reselect. There is no workaround for the issue described in the second scenario in Conditions.
Gateway pool action no longer triggers TMM to produce a core file and restart.