Bug ID 1042009: Mcpd fails to reply if a request is proxied to another daemon and the connection to that daemon closes

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,

Fixed In:
17.0.0,,,, 13.1.5

Opened: Aug 20, 2021
Severity: 3-Major


Mcpd does not reply to the request if the publisher's connection closes/fails, in this case when bcm56xxd is restarted. The perceivable signs of the failure are the snmpwalk failing with a timeout and the "MCPD query response exceeding" log messages


SNMP stopped responding to queries after upgrade


1) Configure snmp on the BIG-IP so you can run snmpwalk locally on the BIG-IP. 2) From one session on the BIG-IP, run a snmpwalk in the while loop. while true;do date; snmpwalk -v2c -c public sysDot1dbaseStat;sleep 2;done Sample output: Sat Aug 21 00:57:23 PDT 2021 F5-BIGIP-SYSTEM-MIB::sysDot1dbaseStatResetStats.0 = INTEGER: 0 F5-BIGIP-SYSTEM-MIB::sysDot1dbaseStatMacAddr.0 = STRING: 0:23:e9:e3:8b:41 F5-BIGIP-SYSTEM-MIB::sysDot1dbaseStatNumPorts.0 = INTEGER: 12 F5-BIGIP-SYSTEM-MIB::sysDot1dbaseStatType.0 = INTEGER: transparentonly(2) 3) From a second session on the BIG-IP restart bcm56xxd bigstart restart bcm56xxd 4a) the snmpwalk will continually report the following: Timeout: No Response from And snmpd will continually log "MCPD query response exceeding" every 30 seconds in /var/log/ltm


Snmpd restart

Fix Information


Behavior Change