Last Modified: Apr 28, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.2.1, F5OS-C 1.2.2, F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2
Opened: Jan 18, 2022 Severity: 2-Critical Related Article:
K50315713
VLAN listeners and/or FDB entries fail to be automatically created in the partition configuration. VLAN listeners and FDB entries are required in order for the VELOS data path to function correctly. Because tenant deployment can take 5-to-10 minutes, the FDB and VLAN listener entries might not exist immediately.
Traffic on the affected VLAN does not function correctly.
A VLAN listener or FDB entry may intermittently fail to be created when all of the following conditions are met: - The BIG-IP tenant version is 14.1.x. - The tenant is deployed OR a new VLAN is added to the tenant configuration.
You can work around the issue by one of the following: - Deploy/Upgrade the BIG-IP tenant to a later version than BIG-IP 14.1.x - Remove and re-add the affected VLANs from the tenant in the partition configuration. This triggers a re-creation of the FDB and VLAN listener entries. 1. Login to the command line of the VELOS partition floating management IP address as the partition administrator. 2. Enter the configuration mode terminal by entering the following command: config 3. Use the following command syntax to display the VLANs associated to a tenant. show full-configuration tenants tenant <tenant name> config vlans 4. Use the following command syntax to remove a VLAN from a tenant: no tenants tenant <tenant name> config vlans <vlan number> For example, enter the following command: no tenants tenant exampleTenant config vlans 101 5. Enter the following command to commit the changes: commit 6. Use the following command syntax to re-add the VLAN to the tenant: tenants tenant exampleTenant config vlans <vlan number> For example, enter the following command: tenants tenant exampleTenant config vlans 101 7. Enter the following command to commit the changes: commit
None