Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS
Known Affected Versions:
20.0.1, 20.0.2, 20.1.0, 20.1.1
Opened: Feb 16, 2024 Severity: 2-Critical
If a BIG-IP Next VE instance is deployed and the instance receives a DHCP address at startup, it will immediately configure and form a Kubernetes cluster. If the setup script is run after that and if VLANs are configured by the script, TMM will not have the VLANs assigned to it. The problem is not immediately obvious, because the API will return the configured state, showing VLANs assigned to interfaces.
The BIG-IP Next instance will be unable to handle data-plane traffic.
- BIG-IP Next VE. - Versions 20.0 or 20.1. - DHCP assigns address to mgmt. - The setup script is run and VLANs are configured by it.
Do not assign DHCP addresses to the Next instance. Or, if an address is already assigned to mgmt, do not configure VLANs when running the setup script.
None