- Cisco Community
- Technology and Support
- Security
- Network Security
- Cisco ASA 5510 high memory usage problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Cisco ASA 5510 high memory usage problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2015 06:22 AM - edited 03-11-2019 10:56 PM
Hi all,
in our network we have a Cisco ASA 5510, 256 MB RAM, running on ios verison 8.2(5)48. The problem that started around 10 days ago includes exceptionally high memory usage (around 85-87% which is a considarable spike as before it was no more then 50%). This memory usage stays around this percent the whole time and lowers for several percent at low business hours (but still remains high compering to prior times). The thing that needs to be pointed out is that so far no user and no device that uses this firewall to pass traffic hasn't reported any issue. The problem is that this ASA is not redundant and if at some point it fails do to this memory situation there will be a break in communication.
Show memory commands reviled several troubling data, but I am not sure how to decipher them so I am turning to you guys :) Here are the commands:
show memory
Free memory: 33063656 bytes (12%)
Used memory: 235371800 bytes (88%)
------------- ----------------
Total memory: 268435456 bytes (100%)
show memory detail
Free memory: 33112696 bytes (12%)
Used memory:
Allocated memory in use: 92716424 bytes (35%)
Reserved memory: 142606336 bytes (53%)
----------------------------- ----------------
Total memory: 268435456 bytes (100%)
Dynamic Shared Objects(DSO): 0 bytes
Least free memory: 51512 bytes ( 0%)
Most used memory: 268383944 bytes (100%)
MEMPOOL_DMA POOL STATS:
Non-mmapped bytes allocated = 53248000
Number of free chunks = 66
Number of mmapped regions = 0
Mmapped bytes allocated = 0
Max memory footprint = 53248000
Keepcost = 33063984
Max contiguous free mem = 33063984
Allocated memory in use = 20180936
Free memory = 33067064
----- fragmented memory statistics -----
fragment size count total
(bytes) (bytes)
---------------- ---------- --------------
24 13 312
32 2 64
40 16 640
48 1 48**
48 31 1488
64 1 64
80 1 80
33063984 1 33063984*
* - top most releasable chunk.
** - contiguous memory on top of heap.
----- allocated memory statistics -----
fragment size count total
(bytes) (bytes)
---------------- ---------- --------------
48 2 96
56 1389 77784
64 52 3328
72 1 72
80 6 480
112 7 784
120 3 360
144 6 864
168 2 336
232 1 232
248 1 248
256 5 1280
384 3 1152
512 6 3072
1024 98 100352
2048 1 2048
4096 4 16384
8192 12 98304
16384 1 16384
24576 2 49152
32768 3 98304
65536 6 393216
98304 1 98304
131072 1 131072
196608 2 393216
262144 3 786432
393216 1 393216
524288 3 1572864
786432 1 786432
1048576 2 2097152
1572864 1 1572864
2097152 1 2097152
6291456 1 6291456
MEMPOOL_GLOBAL_SHARED POOL STATS:
Non-mmapped bytes allocated = 125829120
Number of free chunks = 2198
Number of mmapped regions = 0
Mmapped bytes allocated = 0
Max memory footprint = 125829120
Keepcost = 1248
Max contiguous free mem = 262264
Allocated memory in use = 92717784
Free memory = 33111336
----- fragmented memory statistics -----
fragment size count total
(bytes) (bytes)
---------------- ---------- --------------
16 159 2544
24 210 5040
32 82 2624
40 71 2840
48 1 48**
48 96 4608
56 37 2072
64 28 1792
72 49 3528
80 22 1760
88 41 3608
96 18 1728
104 18 1872
112 15 1680
120 22 2640
128 18 2304
136 24 3264
144 15 2160
152 19 2888
160 19 3040
168 20 3360
176 26 4576
184 9 1656
192 9 1728
200 12 2400
208 15 3120
216 11 2376
224 12 2688
232 15 3480
240 8 1920
248 9 2232
256 159 44808
384 10 4624
512 113 67304
768 38 34632
1024 15 18928
1248 1 1248*
1536 13 20904
2048 7 17216
3072 80 292616
4096 114 598168
6144 93 663344
8192 97 937496
12288 18 247896
16384 21 415288
24576 1 25232
32768 1 37776
65536 261 21939920
98304 9 946712
131072 34 5734600
196608 2 456632
262144 2 524864
* - top most releasable chunk.
** - contiguous memory on top of heap.
----- allocated memory statistics -----
fragment size count total
(bytes) (bytes)
---------------- ---------- --------------
48 1394 66912
56 738 41328
64 4380 280320
72 359 25848
80 3672 293760
88 387 34056
96 251 24096
104 1962 204048
112 957 107184
120 506 60720
128 586 75008
136 3291 447576
144 110 15840
152 1065 161880
160 171 27360
168 257 43176
176 193 33968
184 1738 319792
192 1100 211200
200 259 51800
208 5 1040
216 45 9720
224 24 5376
232 33 7656
240 285 68400
248 150 37200
256 11722 3000832
384 644 247296
512 1524 780288
768 33 25344
1024 638 653312
1536 17 26112
2048 772 1581056
3072 65 199680
4096 111 454656
6144 13 79872
8192 87 712704
12288 35 430080
16384 429 7028736
24576 67 1646592
32768 38 1245184
49152 9 442368
65536 567 37158912
98304 2 196608
131072 17 2228224
196608 3 589824
262144 6 1572864
393216 4 1572864
524288 7 3670016
786432 5 3932160
1048576 1 1048576
1572864 1 1572864
2097152 3 6291456
Summary for all pools:
Non-mmapped bytes allocated = 179077120
Number of free chunks = 2264
Number of mmapped regions = 0
Mmapped bytes allocated = 0
Max memory footprint = 179077120
Keepcost = 33065232
Allocated memory in use = 112898720
Free memory = 66178400
And finally the one which shows some failed parts:
show memory app-cache
CACHE NAME LIMIT COUNT ALLOC FAILED BYTES USED
Local block 1024 251 251 0 216864
NP dispatch 325 1 134 0 32696
SNP Conn 325 261 7774 79469508 5597280
netflow data 325 0 0 0 0
DSCP 325 0 0 0 0
SNP Host 325 304 4620 16467386 868560
SNP conn set per-cl 325 0 0 0 0
SNP APP ID 325 283 326 270 32600
SNP RT Inspect 325 279 326 35 76936
NP-CP punt event 325 0 0 0 0
NP-CP identity-traf 325 0 0 0 0
NP-CP event 325 0 0 0 0
NP-CP syslog event 325 0 0 0 0
NP-CP midpath event 325 0 0 0 0
NP-CP SRTP event 325 0 0 0 0
NP-CP ha event 325 0 0 0 0
NP-CP TD event 325 0 0 0 0
NP ACL log cfg 325 0 43 0 2924
NP ACL log flow 325 230 1584 20827 297792
SNP TCB 325 282 4724 0 1209344
SNP Logger block 325 0 0 0 0
SNP MP PF Mod 325 0 0 0 0
SNP MP SVC Conn 325 0 0 0 0
SNP SVC Session 325 0 0 0 0
SNP MP Service 325 0 0 0 0
SNP MP Stack 325 1 3 0 1416
TD Rate stats 500 0 62 0 9424
TD Port stats 100 0 0 0 0
TD Host/Port counte 100 0 0 0 0
CTM SG List 5000 0 0 0 0
CERT API msg cache 100 0 0 0 0
CP Connection 325 322 329 622489 252672
CP APP ID 325 0 0 0 0
PM Bit Mask 325 1 1 0 56
PM Hash table 325 0 0 0 0
Inspect HTTP 325 0 0 0 0
HTTP Result 325 0 0 0 0
TD ACE stats 100 0 20 0 5040
TD Host/Port counte 100 0 20 0 480
==========================================================================
LIMIT COUNT ALLOC FAILED BYTES USED
TOTAL 17099 2215 20217 96580515 8604084
As you can see there are a lot of FAILED numbers in this column but I am not certain what do they mean, and I haven't been able to find much about them on the internet. So if someone had a similiar problem or can advise in some way I would appriciate it.
Best regards,
Stevan
- Labels:
-
NGFW Firewalls
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2015 07:31 AM
Hi,
I think there is something wrong.
Check this:-
show memory detail
Free memory: 33112696 bytes (12%)
Used memory:
Allocated memory in use: 92716424 bytes (35%)
Reserved memory: 142606336 bytes (53%)
----------------------------- ----------------
Total memory: 268435456 bytes (100%)
Share the ASA show tech
Rest , get this output:-
show mem binsize 65536
Thanks and Regards,
Vibhor Amrodia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2015 04:44 AM
Hi Vibhor,
thanks for the answer. Yup it is true this procent for reserved memory constantly stays at that 53% procent, but I thought the failed numbers my point more accurately to the problem, as they do seem pretty specific. I can't post show tech now but here is show mem binisize 65536 output
show memory binsize 65536
MEMPOOL_DMA pool bin stats:
pc = 0x0812b386, size = 65607 , count = 1
pc = 0x0804f0c4, size = 159022 , count = 2
pc = 0x0804f669, size = 249813 , count = 3
MEMPOOL_GLOBAL_SHARED pool bin stats:
pc = 0x09337e6e, size = 44710685 , count = 571
pc = 0x0817680d, size = 262448 , count = 4
pc = 0x08a00960, size = 81920 , count = 1
pc = 0x08c6cff8, size = 7665568 , count = 110
pc = 0x08ad33d9, size = 199008 , count = 3
pc = 0x088fdf2f, size = 91064 , count = 1
pc = 0x0933810a, size = 297116 , count = 4
pc = 0x081e9144, size = 65536 , count = 1
pc = 0x08141928, size = 139264 , count = 2
pc = 0x08141668, size = 69632 , count = 1
pc = 0x08e02e55, size = 65536 , count = 1
pc = 0x08782077, size = 96064 , count = 1
pc = 0x087300af, size = 65536 , count = 1
pc = 0x08c631cb, size = 163968 , count = 2
pc = 0x08531c2d, size = 71136 , count = 1
pc = 0x08aab363, size = 66048 , count = 1
pc = 0x0804fb6c, size = 66496 , count = 1
pc = 0x0804fb97, size = 66496 , count = 1
Generally I was hoping that someone had the same issue, so he could give advice as to what is happening. If not I will open a Cisco TAC, so far this has not caused any real problems but it definitly needs to be checked.
If you have any more input or ideas please share.
Best regards,
Stevan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2015 06:09 PM
Hi,
I think it would be best that you open a TAC. I think you should focus on the Reserved RAM issue.
Thanks and Regards,
Vibhor Amrodia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2016 01:06 AM
Hi Stevan ,
I hope that you are well . Have you resolved this issue. I am experiencing a similar issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2016 05:22 AM
Hi I actually completly forgot about this thread.
Anyway just to write for anyone that stumbels upon it like Dhiran here:
In the end I opened a TAC case, we didn't find the couse for this, but upon advise from TAC engineer an upgrade to newer version of IOS helped resolve the issue completly.
Stevan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide
