Hello,
I hope this excerpt will help--
"The ASR1K runs IOS-XE, not the traditional IOS. In IOS-XE, a Linux component runs the kernel, and the IOS runs as a daemon, which hereafter is referred as IOSd (IOS-Daemon). This creates a requirement that the memory be split between the Linux kernel and the IOSd instance.
The memory that is split between IOSd and the rest of the system is fixed at startup and cannot be modified. For a 4-GB system, IOSd is allocated approximately 2 GB, and for a 8-GB system, the IOSd is allocated approximately 4 GB (with software redundancy disabled).
Since the ASR1K has a 64-bit architecture, any pointer that is in every data structure in the system consumes double the amount of memory when compared to the traditional single-CPU platforms (8 bytes instead of 4 bytes). The 64-bit addressing enables IOS to overcome the 2-GB addressable memory limitation of IOS, which allows it to scale to millions of routes."
I reckon this should be exepcted, in case you don't see any suspicious log messages or processes failing due to a MALLOC error I believe things are fine. The memory is also split between various other processes as well like the I/O buffer, the buffer used to transfer packets from the RP to the forwarding processor etc.
If you see any errors or any processes breaking then I would suggest to open a TAC case, that'll help isolate any memory leaks or stuck processes not releasing memory.
Regards,
Shaunak
