07-07-2018 01:58 AM - edited 02-21-2020 07:57 AM
Over the last week we have been experiencing problems with our ASA 5512. The Firewall has went down 3 times over the past week with no knowledge a to why. In an attempt to diagnose the problem I configured syslog (PRTG) and setup debugging. The device still remains up with traffic passing through it.
Today I received a notification from the syslog which may point to the route cause:
System is low on free memory blocks of size 256 (1 CNT out of 20000 MAX)
I can see from the messages delivered by PRTG
I can see memory utilisation is sitting at 50-54% constantly (Even after configuring Netflow and SNMPv3 recently) - Severity (Error)
CPU remains low at around 10-20% utilisation.
Not sure what the current CPU and memory utilisation is after debugging being turned on but I haven't received any triggers alerting me after a day of debug being switched on.
I am trying to get my head around what could be using the memory blocks of size 256. I can see from the below post the possible cause could be cosmetic. Not entirely sure what the responder meant by that.
The revisions we are currently running:
Cisco Adaptive Security Appliance Software Version 9.8(1)
Device Manager Version 7.8(1)
I understand that our software is outdated and this will be addressed next week as I understand it is vulnerable particularly to CVE-2018-0101. This may also address the problems.
Any suggestions to what could be causing the issues of the memory block being depleted?
Solved! Go to Solution.
07-09-2018 05:13 AM
The ASA 9.8 release notes points to an open bug related to 256 block size depletion.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva80364
Bug notes indicate the root cause as excessive syslog logging. This might be one Avenue to check. I would suggest opening a tac case if the problem persists after upgrading to the latest 9.8 or 9.9 interim release.
07-09-2018 05:13 AM
The ASA 9.8 release notes points to an open bug related to 256 block size depletion.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva80364
Bug notes indicate the root cause as excessive syslog logging. This might be one Avenue to check. I would suggest opening a tac case if the problem persists after upgrading to the latest 9.8 or 9.9 interim release.
07-09-2018 05:56 AM
Thanks. This would make sense. It was the syslog that would go down before the Firewall device ground to a halt completely, with no flow of traffic. I updated it on Saturday afternoon to the latest version and so far so good. Debugging has also been turned off with only errors now being collected. I'll keep an eye on this for sure.
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