Last Modified: Jun 19, 2025
Affected Product(s):
BIG_IP_NEXT(VE/HW) F5OS, F5OS-C, LTM, Velos
Known Affected Versions:
20.3.0, F5OS-C 1.8.0, F5OS-C 1.8.1
Opened: Oct 04, 2024 Severity: 1-Blocking
After reboot of a VELOS chassis, which has both BIG-IP and Next tenants deployed, one or more of the BIG-IP tenants might get into a reboot loop and not come up while the Next tenants come up ok.
BIG-IP tenants do not come back up online after reboot. BIG-IP tenants correctly attempt to use the newly assigned QAT devices after reboot but one or more of these devices are incorrectly being used by Next.
1) VELOS chassis has both BIG-IP and Next tenants deployed on the same blade 2) All the tenants have crypto hardware acceleration enabled 3) Reboot happens 4) BIG-IP Next tenants come back up before BIG-IP tenants (this is usually the case) and incorrectly continue to use the QAT devices that were assigned before the reboot instead of requesting and using new ones 5) F5OS assigns QAT devices to BIG-IP tenants which were assigned to Next prior to reboot 6) BIG-IP tenants are unable to use these QAT devices as they are already being used by Next 7) BIG-IP tenants reboot in an attempt to recover
When the issue is seen: 1) Switch all BIG-IP Next tenants to configured state from the deployed state (This will force the BIG-IP Next tenants to release the QAT devices that were being used by them and will also unlock any BIG-IP tenants attempting to use these devices). 2) Optionally, wait for all BIG-IP tenants to be up and running. 3) Switch all BIG-IP Next tenants to deployed state from the configured state (This will force new non-overlapping device assignment to Next tenants)
None