Last Modified: Nov 29, 2025
Affected Product(s):
BIG_IP_NEXT(CNF) CNF
Known Affected Versions:
1.3.0
Fixed In:
1.3.1
Opened: Jun 21, 2024 Severity: 1-Blocking
During TMM Pod scale-up or TMM Pod restart event, Secure Context configuration is not successfully applied in TMM. Virtual server statistics have the secure context in EDENY status.
Newly brought-up TMM pods will not serve traffic.
- Secure context CRs with or without default profiles. - Scale-up or restart TMM Pods.
Delete and apply the secure context CRs once the TMM's secure contexts are in EDENY state.
Always regenerate secure context protobuf during TMM Pod events.