...
The mibd_interface process leaks memory in sysdb_lib_rply_list_interpret and sysdb_lib_send_opt_v, eventually hits its rlimit and is restarted
This issue can occur if the user is running large numbers of CFM LMM probes and running multiple concurrent SNMP requests that walk over both the CFM MIB and the MEF SOAM PM MIB: OIDs 1.3.111.2.802.1.1.8 and 1.3.6.1.4.1.15007.1.3.
There is no true workaround. Some mitigating factors: Do not run concurrent requests (poll small areas of the PM MIB at separate times from polling the CFM MIB) Monitor mibd_interface memory use via 'show mem heap dll ' and check for leaks in the above two functions. If leaks are seen, monitor the speed of the leak over time and consider pro-actively restarting the mibd_interface process prior to it reaching its rlimit.
The mibd_interface leak locations sysdb_lib_rply_list_interpret and sysdb_lib_send_opt_v are very generic places for leaks and may not be caused by this issue. If leaks in these locations are encountered without CFM configuration or the CFM MIB being polled you are encountering a different issue. Running 'follow process' on the mibd_interface process and seeing MIB retrieval for the 'k_mefSoam*' tables means you are likely to be hitting this issue.
Cisco 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.