Loading...
Loading...
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.
None
Improved performance for query for virtual address statistics when there are hundreds of virtual address and address lists entries.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.