Operational Defect Database
BugZero found this defect 466 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1231889
Mismatched VLAN names (or VLANs in non-Common partitions) do not work properly in BIG-IP tenants running on r2000 / r4000-series appliances
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP All
BIG-IP F5OS
BIG-IP F5OS-A
Affected releases:
15.1.10
15.1.10.2
15.1.10.3
15.1.10.4
17.1.1
17.1.1.1
17.1.1.2
17.1.1.3
F5OS-A 1.3.1
F5OS-A 1.3.2
F5OS-A 1.5.0
F5OS-A 1.5.1
Fixed releases:
No fixed releases provided.
Description:
Symptoms ... When a VLAN configured in the tenant does not have the same name as the VLAN on in F5OS, or the VLAN in the tenant is created in a partition other than "Common", the VLAN may not pass traffic properly. ... For tenants running on an r2000 or r4000-series appliance, the tenant needs to know the VLAN<>interface mapping, but the system is not able to populate this information when the VLAN is not in the Common partition. ... The system may have log messages similar to the following: Feb 15 15:39:49 r4000-1.example.com err mcpd[19522]: 01070094:3: Referenced vlan (/Common/external) is hidden, does not exist, or is already on another instance. ... Partitions other than the common partition cannot have VLANs. ... VLANs created in other partitions will not be operational in the data path. ... Conditions ... - r2000 and r4000-series platforms - BIG-IP tenant - VLANs moved to partitions other than "Common", or renamed so that the name does not match between hypervisor and tenant.
