Last Modified: Jul 15, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Fixed In:
2.1.0
Opened: Jul 24, 2025 Severity: 2-Critical
To ensure a deterministic name for the internal trunk object, the internal trunk ID format has been updated. This improvement enhances the TMM (dataplane) configuration process, ensuring consistent behavior across data plane and control plane (F5Ingress controller) restarts. However, this change may lead to traffic disruption during the upgrade from a version using the old ID format to one using the new format. The disruption occurs during the upgrade window when the new F5Ingress controller starts and reconfigures the old TMMs. The updated configuration, which uses the new trunk ID format, conflicts with the existing configuration on the old TMMs, causing traffic failures. Traffic is restored once the old TMMs are upgraded to the new version, resolving the mismatch between configurations. Once the setup is upgraded to the version using the new format, all future upgrades will not have this specific issue.
Partial network traffic disruption (traffic drop) observed during upgrade.
SPK Upgrade from versions that use the old trunk ID format for internal trunk objects to versions (v2.0.2) that use the updated trunk ID format.
None
None