Last Modified: Oct 27, 2026
Affected Product(s):
BIG-IP NEXT BNK (all modules)
Known Affected Versions:
2.1.0, 2.1.1
Opened: Jul 25, 2025 Severity: 3-Major
AFM blob is not sent to TMM when both the TMM container and another container within the same pod are restarted, preventing NAT/Firewall from working. Subsequent TMM container restarts do not help the issue.
Traffic will fail when a NAT Policy is attached to a SecureContext and only the default action will take affect if a Firewall Policy is attached.
-- AFM pod is installed on the cluster. -- At least two TMM containers, one of which is TMM itself and not all containers, are restarted either through a crash or manually. -- Subsequent restarts of just the TMM container.
1. Modify NAT/Firewall Policy which is attached to any SecureContext/GatewayAPI CR. OR 2. Re-attach NAT/Firewall Policy to SecureContext/GatewayAPI CR. OR 3. Re-create SecureContext CR that has a NAT/Firewall Policy. OR 4. Re-create any GatewayAPI CR that has a Firewall Policy CR.
None