Bug ID 642122: Cannot delete a SNAT pool and SNAT translation address in a single transaction.

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
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

Opened: Jan 29, 2017
Severity: 3-Major

Symptoms

When attempting to delete an in-use SNAT translation and SNAT pool in a single transaction, tmsh will report that the SNAT translation object is in use, even though it is up for deletion in the current transaction. The system posts an error similar to the following: SNAT translation address <address> is still referenced by a snat pool

Impact

Configuration scripts must order object deletion so that the SNAT translation object is removed before the SNAT pool.

Conditions

Attempt to delete a SNAT pool and SNAT translation object in the same transaction.

Workaround

Delete the SNAT translation first, then delete the SNAT pool.

Fix Information

None

Behavior Change