Last Modified: Oct 19, 2025
Affected Product(s):
F5OS F5OS-A, F5OS-C
Known Affected Versions:
F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.5.4, F5OS-A 1.7.0, F5OS-A 1.8.0, F5OS-A 1.8.3, F5OS-C 1.6.2, F5OS-C 1.6.4
Opened: Sep 20, 2024 Severity: 3-Major
In rare situations, changing the vlan assignment of a running BIG-IP tenant via the GUI may cause F5OS to release the base MAC address of the tenant and re-assign it. If this happens, there are two possibilities: A) F5OS assigns the tenant the same mac address it had before. B) F5OS assigns the tenant a new mac address. If 'A' occurs, there is no impact. But if 'B' occurs, the running tenant continues to use its former mac address even though F5OS has changed it. This persists until the tenant is stopped and re-deployed.
Tenants may not have connectivity on new vlans that are added, since the FDB listener creation will fail with the following error: api-svc-gateway[14]: priority="Err" version=1.0 msgid=0x5804000000000087 msg="Error occurred while processing listener request" TENANT="mytenant" REASON="bad mac address" VALUE="00:94:a1:aa:bb:cc" If a new tenant or LAG is subsequently created, F5OS may assign it the MAC address that the previous tenant is still using. This may result in traffic disruption due to a duplicate mac address in use until the previous tenant is stopped.
Using the F5OS GUI to change the vlans assigned to a tenant that is running.
Although this issue happens rarely, it can be avoided by using the F5OS CLI when changing the vlan assignments of a running tenant. To recover from this issue, stop the tenant by setting its running state to 'provisioned', and then start it again. It will begin using the newer MAC address assigned to it.
None