Bug ID 1079237: After certain configuration tasks are performed, TMM may run with stale SNAT translation parameters.

Last Modified: Apr 24, 2024

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,

Opened: Feb 08, 2022

Severity: 3-Major


A SNAT translation object instantiated by performing specific configuration tasks (see Conditions) does not work. For example: - Connections might be reset with cause "No available SNAT addr". - An unexpected IP address might be used to SNAT the outgoing traffic.


The system does not use the configured SNAT translation address. Traffic will be impacted as a result (for example, reset connections or incorrect source IP address in outgoing traffic).


This issue is known to occur when one of the following operations is performed: - Restoring a UCS or SCF archive in which a SNAT translation with a specific name specifies a different IP address or route domain. - Performing a config-sync between redundant units in which the sender changes a SNAT translation with a specific name to use a different IP address or route domain. - Performing specific tmsh CLI transactions involving SNAT translation modifications.


Restart TMM (bigstart restart tmm) on affected units.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips