Loading...
Loading...
TMM with a DNS Virtual server and attached DNS Cache cores with a specific backtrace.
TMM will restart and traffic flow will be disrupted.
A DNS cache is configured with one or more very large sub-caches (RRset, msg, nameserver, key).
Lower DNS sub-cache (RRset, msg, key) sizes to 150mb or less (nameserver should be < 1 million entries), that is do not over-provision memory available on BIGIP.
TMM will no longer core/restart with this backtrace due to large DNS sub-cache sizes. Please note that it is still advised to restrict cache size to fit within available memory. Be conservative and size up given available memory. Note for EACH configured cache, the sum of the sub-cache sizes (rrset + msg + nameserver + key), times the number of TMM threads, is approximately the size the cache may occupy in memory (it will actually occupy slightly more). Each configured cache consumes its own amount of memory -- configured caches do not share memory. Their sum must not exceed available memory of TMM. Note also TMM does not have control over all available system memory -- some is left available for the host; this is platform dependent.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.