Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(VE/HW) All
Known Affected Versions:
20.0.1, 20.0.2
Opened: Sep 19, 2023 Severity: 1-Blocking
1) Containers that belong to the BIG-IP Next Access module keep running on BIG-IP Next all the time on VELOS & rSeries. 2) On VE, the containers run only if the BIG-IP Next Access module is provisioned using: /api/v1/systems/{systemID}/provisioning api
Containers that belong to the BIG-IP Next Access module keep running all the time and this can lead to wastage of resources on VELOS & rSeries.
This is observed all the time when BIG-IP Next is deployed on VELOS/r-series.
If you do not want to run BIG-IP Next Access containers as part of a BIG-IP Next tenant deployment, you can use this workaround before installing the tenant: 1) Run the following command on the standby controller: sed -i 's/access: true/access: false/g' /var/F5/partition<partition-ID>/SPEC/<IMAGE_VERSION>. yaml 2) Trigger failover from partition cli ->: system redundancy go-standby 3) Install the tenant.
None