Bug ID 1023937: L2 Listener entries are not created for tenants sharing the same VLAN

Last Modified: Sep 22, 2021

Bug Tracker

Affected Product:  See more info
F5OS Velos(all modules)

Known Affected Versions:
1.1.0, 1.1.1, 1.1.2, 1.1.3

Fixed In:
1.1.4

Opened: Jun 08, 2021
Severity: 3-Major

Symptoms

After creating two tenants that share a VLAN, the L2 Listener entries for these tenants were not created. This results in all tenant traffic matching the RBCAST-LISTENER vlan-listener where it is handled by the Software Rebroadcaster.

Impact

This issue results in all tenant traffic matching the RBCAST-LISTENER vlan-listener where it is handled by the Software Rebroadcaster.

Conditions

STEPS TO REPRODUCE: - Here used the default partition - Create a vlan default-2(config)# vlans vlan range 1155 config name lab-vlan - Assign vlan to an interface default-2(config)# interfaces interface 1/1.0 ethernet switched-vlan config trunk-vlans 1155 - Create two tenants that share vlan 1155. default-2(config)# tenants tenant foo-tenant config image BIGIP-14.1.4.3-0.0.8.ALL-VELOS.qcow2.zip.bundle cryptos enabled nodes 1 mgmt-ip 10.10.10.1 prefix-length 24 gateway 10.10.10.254 running-state deployed vlans 1155 default-2(config-tenant-foo-tenant)# default-2(config)# tenants tenant bar-tenant config image BIGIP-14.1.4.3-0.0.8.ALL-VELOS.qcow2.zip.bundle cryptos enabled nodes 1 mgmt-ip 10.10.10.2 prefix-length 24 gateway 10.10.10.254 running-state deployed vlans 1155 default-2(config-tenant-bar-tenant)# commit - Run "show fdb" to see if L2 listener entries were created for the tenants.

Workaround

NA

Fix Information

Fixed an issue where L2 Listener entries were not created after creating two tenants that share a VLAN.

Behavior Change