Bug ID 1551085: F5-spk-ingresstcp that uses a vlan lists is unavailable

Last Modified: Apr 28, 2025

Affected Product(s):
BIG_IP_NEXT(SPK) SPK(all modules)

Fixed In:
1.9.2, 1.7.7

Opened: Feb 23, 2024

Severity: 3-Major

Symptoms

Connections to a f5-spk-ingresstcp with a vlan list fail. This may occur at startup or when f5ingress or tmm are scaled up. The virtual server, pool and pool member tmm stats tables show the f5-spk-ingresstcp CR related rows. The tmm logs show messages like "Config info: Vlan <vlan name> was not found to be currently configured."

Impact

Traffic to the f5-spk-ingresstcp is dropped by TMM

Conditions

At startup or scale up when the f5-spk-ingresstcp CR already exists, has a vlan list and the necessary f5-spk-vlan CRs already exist.

Workaround

None

Fix Information

The f5-spk-ingresstcp is available.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips