Bug ID 1575577: Bcm56xxd will miss sending a heartbeat if the last time it sent a heartbeat took greater than 1 second

Last Modified: Jul 13, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.5.0, 17.5.1

Opened: Apr 03, 2024

Severity: 3-Major

Symptoms

- On average mcpd takes more time to process large firewall rule stats ~20k, but sometimes it takes even longer. - MCPD abruptly removes the LACPD connection causing LACPD to restart. - Multiple MPCD query response exceeding messages and then lead to bcm core. Ex: 010e0004:4: MCPD query response exceeding 60 seconds

Impact

Bcm56xxd process will kill by sod due to the heartbeat missing. It impacts the traffic.

Conditions

-- More(~20k) firewall rules configured along with pccd.overlap.check enabled -- mcpd is constantly busy taking ~20 seconds to process query_stats { fw_rule_stat { } } -- bcm56xxd replies to a query_stats { l2_forward_stat {} } query with every l2 address entry in ARL table

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips