Last Modified: Dec 07, 2023
Affected Product(s):
F5OS All, Velos
Fixed In:
F5OS-C 1.1.1
Opened: Apr 09, 2021 Severity: 2-Critical
After rebooting a tenant, the tenant might receive some erratic VLAN assignment requests, but the VLANs are not associated with this tenant. This spurious VLAN assignment may impact traffic.
Application traffic through the chassis could be impacted.
1. A tenant is created without an assigned VLAN 2. Reboot the blade that tenant is assigned to The second step is not required every time, but it is triggered due to the first step.
There are 2 workarounds: 1. Assign VLAN(s) to the tenant which does not have assigned VLANs and reboot all the blades of this tenant 2. Assign VLAN(s) to the tenant which does not have assigned VLAN and run 'docker restart of API_SERVICE_GW container' on all blades
When a tenant is not configured with any VLANs, the tenant will no longer receive incorrect VLANs when a blade is rebooted.