Bug ID 1304657: Tcam-manager does not support all the possible system network subnets

Last Modified: May 29, 2024

Affected Product(s):
F5OS F5OS(all modules)

Fixed In:
F5OS-C 1.6.0, F5OS-A 1.7.0, F5OS-A 1.5.1

Opened: Jun 05, 2023

Severity: 2-Critical


The connection from the tenant (TMM) to the tcam-manager is continuously restarts. tcam-mgr logs show the wrong tenant-id and hence rejected connection from the tenant: msg="INFO" MSG="Connection from client address:". msg="ERROR" MSG=" Confd access error obtaining tenant info for tenant:12291 slot:1". msg="INFO" MSG="neuron_handle_responses: dropping resp to non-existent client". TMM periodically logs neuron client errors, such as: notice hudproxy_neuron_client_closed_cb: Neuron client connection terminated notice pva_sc_frs_neuron_stopped_cb/2373: FRS SC: Neuron client stopped.


TCAM based features don't work.


The 'system network' configuration is changed from its default setting in F5OS to an affected RFC1918 subnet.


Select either the default RFC6598 subnet or any of the unaffected RFC1918 subnets (prefix: 0, 4, 8, 12).

Fix Information

Tcam-manager now correctly calculates the tenant-id for all possible system network subnets.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips