Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The issue is seen on a ISR4451 running in 17.6.2 as controller mode in SDWAN but it may appear on older versions and not SDWAN and other ISR4K routers or even other routers. The following log is reporting a high memory utilization: %PLATFORM-4-ELEMENT_WARNING: R0/0: smand: RP/0: Used Memory value 90% exceeds warning level 88%. The memory from the Kernel perspective is mostly used by linux_iosd-image: #show process memory platform sorted System memory: 4018572K total, 3631316K used, 387256K free, Lowest: 336512K Pid Text Data Stack Dynamic RSS Name ---------------------------------------------------------------------- 3093 362018 1748532 136 156 1748532 linux_iosd-imag 22031 284 213856 136 156 213856 cpp_cp_svr From the IOS perspective the top process consuming memory is malloclite: #show process memory sorted Processor Pool Total: 1739747564 Used: 1316988792 Free: 422758772 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 918588344 0 0 *MallocLite* 0 0 337317264 133466088 161873104 0 0 *Init* 823 0 127242648 55362016 35547024 0 0 CCSIP_UDP_SOCKET
When reviewing the allocators it can be confirmed the top one owns to malloclite: #sh mem all totals Tracekey : 1#05c14dca07ca800fd29ea1b4557745a4 Head Total(b) Used(b) Free(b) Lowest(b) Largest(b) Processor 7F615D00B048 1739747564 1315644860 424102704 408527328 377475748 reserve P 7F615D00B0A0 102404 92 102312 102312 102312 lsmpi_io 7F61470C31A8 6295128 6294304 824 824 412 Dynamic heap limit(MB) 1000 Use(MB) 640 Allocator PC Summary for: Processor Total Count Name PC 906510072 13812 MallocLite :55B2F7016000+5CD4FB6 <<< 41459280 15684 sip_msgs :55B2F7016000+FC3EF34 34295616 854 *Init* :55B2F7016000+9FB10B8
Reloading the device releases the memory to the minimum usage required for the device operation but it is expected the memory utilization will be in constant increment until consume all the memory again.
It is required to decode the PC owned by Malloclite to confirm if the device is hitting this bug, TAC can decode it and confirm if the device is hitting this bug. Malloclite is a process used to provide memory to other processes, therefore we don’t expect this process to hold a high amount of memory unless another process is using that memory under *MallocLite* There are other bugs like CSCvy65630 which are reporting a similar behavior but they are fixed in 17.6.2.