Bug ID 838405: Listener traffic-group may not be updated properly when spanning is in use.

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Opened: Oct 14, 2019
Severity: 4-Minor

Symptoms

BIG-IP may fail to update configuration of a virtual server when disabling or enabling spanning on the virtual address.

Impact

Disabling or enabling spanning on a virtual address has no effect on the virtual-server configuration. Depending on the configuration, virtual server may or may not forward the traffic when expected.

Conditions

Spanning is disabled or enabled on a virtual address.

Workaround

Enable/Disable spanning together with changing a traffic-group: > modify ltm virtual-address 0.0.0.0 traffic-group none spanning enabled > modify ltm virtual-address 0.0.0.0 traffic-group traffic-group-1 spanning enabled

Fix Information

None

Behavior Change