Last Modified: Jul 22, 2021
See more info
Known Affected Versions:
14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.1.2, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.3, 220.127.116.11, 14.1.4, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Mar 02, 2021
If there are hundreds of virtual addresses and hundreds of address entries spanning one or more address lists, mcpd might take seconds to reply to a query for virtual address statistics. One of the more commonly visible signs of this is high CPU usage by mcpd if it's processing a large number of queries for virtual address statistics. It is also likely that snmpd responses will be severely delayed to SNMP agent requests.
-- High CPU usage by mcpd. -- SNMP requests/polling timeouts occur because mcpd takes hundreds of milliseconds to respond. Note: If the address lists that contain the entries are not used in traffic-matching-criteria (and therefore do not increase the size of the tmstat virtual_address_stat table), mcpd response time is in the tens of milliseconds.
-- Hundreds of virtual servers. -- Hundreds of address entries spanning one or many address lists. -- Running SNMP queries for virtual address statistics.