Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP CGN, LTM
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 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, 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, 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
Fixed In:
12.1.0
Opened: Mar 22, 2015 Severity: 3-Major Related Article:
K33126159
Syslog message: 'Inet port exhaustion' message is marked as 'crit' when it should be a 'warning'. The following message appears via syslog: -- crit tmm3[12240]: 01010201:2: Inet port exhaustion on addr1 to addr2:53 (proto 17).
This is reported as a critical event, when it is not a critical event. The 'crit' message designation usually means a critical event has occurred and the system is in imminent danger. That is not the case here. This message should be a 'warning' because it means a connection might have failed to find a port when performing NAT functions.
SNAT or CGNAT are configured.
None.
The system now correctly reports the following syslog message as a warning: Inet port exhaustion.