On 22 November 2017 at 09:17, Christian Kratzer <[email protected]> wrote: > On Wed, 22 Nov 2017, James Bensley wrote: >> I believe that the IOSd process is a 32-bit process so it can't use >> more than 4GBs of RAM. > > > does not look like it on this box: > > Router#show version | i mem > cisco ASR1001 (1RU) processor with 6848986K/6147K bytes of memory. > 32768K bytes of non-volatile configuration memory. > 16777216K bytes of physical memory. > Router#
Looks like you are right. I OP has an ASR1002-X, check one here: #show ver | inc mem cisco ASR1002-X (2RU-X) processor (revision 2KP) with 3729028K/6147K bytes of memory. ... 8388608K bytes of physical memory. ^ This only has 8GB of RAM and it is using roughly half as expected. Although not using half isn't exactly a bad sign in its self, the Linux virtual memory manager allows for memory overcommit: #show platform software status control-processor Memory (kb): healthy Total: 8091848 Used: 3885636 (48%) Free: 4206212 (52%) Committed: 5328504 (66%), status: healthy, under 95% So it maybe that IOSd on OP's system would simply grow more when needed? Cheers, James. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
