Symptom

Due to memory exhaustion, the device experiencing the memory leak can eventually crash. You can also verify the memory utilization of the whole device and of the process MallocLite increasing everyday by monitoring the device through the following command: ## Day 1: #show platform software status control-processor brief Load Average Slot Status 1-Min 5-Min 15-Min RP0 Healthy 4.28 3.10 2.40 Memory (kB) Slot Status Total Used (Pct) Free (Pct) Committed (Pct) RP0 Healthy 8119648 4470284 (55%) 3649364 (45%) 5088228 (63% <<<<<<<<< #show processes memory sorted Processor Pool Total: 2018961472 Used: 1004686192 Free: 1014275280 reserve P Pool Total: 102404 Used: 88 Free: 102316 lsmpi_io Pool Total: 6295128 Used: 6294296 Free: 832 PID TTY Allocated Freed Holding Getbufs Retbufs Process 0 0 0 0 747878176 0 0 *MallocLite* <<<<<<<<< 0 0 402903384 200387360 173280280 0 0 *Init* 92 0 437303208 341474064 11551104 0 0 IOSD ipc task 763 64 75289168 64230296 11492880 0 0 iosp_dmiauthd_co ## Day 2: site_202_PhaDejvic11#show platform software status control-processor brief Load Average Slot Status 1-Min 5-Min 15-Min RP0 Healthy 1.44 1.83 1.90 Memory (kB) Slot Status Total Used (Pct) Free (Pct) Committed (Pct) RP0 Healthy 8119648 4522056 (56%) 3597592 (44%) 5127196 (63%) <<<<<<<<< site_202_PhaDejvic11#show processes memory sorted Processor Pool Total: 2018960896 Used: 1042315432 Free: 976645464 reserve P Pool Total: 102404 Used: 88 Free: 102316 lsmpi_io Pool Total: 6295128 Used: 6294296 Free: 832 PID TTY Allocated Freed Holding Getbufs Retbufs Process 0 0 0 0 785485312 0 0 *MallocLite* <<<<<<<<< 0 0 402903384 200387360 173280280 0 0 *Init* 92 0 458013488 358659992 11551104 0 0 IOSD ipc task 763 64 75289168 64230296 11492880 0 0 iosp_dmiauthd_co ## Day 3: #show platform software status control-processor brief Load Average Slot Status 1-Min 5-Min 15-Min RP0 Healthy 1.84 2.11 2.06 Memory (kB) Slot Status Total Used (Pct) Free (Pct) Committed (Pct) RP0 Healthy 8119648 4570488 (56%) 3549160 (44%) 5180232 (64%) <<<<<<<<< #show processes memory sorted Processor Pool Total: 2018960320 Used: 1081098336 Free: 937861984 reserve P Pool Total: 102404 Used: 88 Free: 102316 lsmpi_io Pool Total: 6295128 Used: 6294296 Free: 832 PID TTY Allocated Freed Holding Getbufs Retbufs Process 0 0 0 0 824273824 0 0 *MallocLite* <<<<<<<<< 0 0 402903384 200387360 173280280 0 0 *Init* 92 0 479148160 376176296 11551104 0 0 IOSD ipc task 763 64 75289168 64230296 11492880 0 0 iosp_dmiauthd_co

Conditions

The conditions to hit trigger the memory leak are the following: 1. Configure snmp-server community with type 6 encrypted string. 2. Perform snmpwalk using the community name in plain text. After that, the memory leak will start being visible.

Workaround

A possible workaround to avoid hitting the memory leak is to not use a snmp-server community with type 6 encrypted string. You can change it to type 0 instead. Since the "0" is implicit there is no need to add it to the command string. EG. "snmp-server community test3 view capture_alerts R0" Please follow this document, and search for Configure SNMP with Encrypted Strings Using CLI Templates https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/snmp/snmp-book/snmp-book_2.html ** Note: A device in controller managed mode cannot be configured to use type 7.

Further Problem Description