Last Modified: Jul 15, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Fixed In:
2.1.0
Opened: Jun 24, 2025 Severity: 2-Critical
Multiple TMM pods reserve and utilize identical NAT IPs. This can be observed in TMM stats, specifically in the 'fw_nat_reserv_ip_range_stat' table, and in the MRFDB output.
Duplicate NAT IP reservations can lead to client connection failures. This occurs because the server-side router might route return traffic to the incorrect TMM pod.
This issue arises when a TMM pod releases previously reserved NAT IPs and is subsequently deleted. The exact timing of deletion is not significant.
Delete the NAT Custom Resource (CR) and recreate it. However, this should not be done within the NAT IP reservation timeout period (default: 15 minutes) following the deletion of a TMM pod.
NAT IPs are no longer duplicated.