Check manual page of cisco_mem_asa64
Cisco Adaptive Security Appliances Version 9.x: System Memory
|Distribution: ||official part of Check_MK|
|Supported Agents: ||SNMP|
This Check does the same as the normal cisco_mem check. The only difference is
that this check only monitors the System memory. The reason is a
bug in the ASA firmware: http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/116423-troubleshoot-asa-snmp.html
Moreover there are problems with newer ASA version 9.x: from cisco
Deprecate 32-bit SNMP OIDs for Memory UtilizationCSCuu46705DescriptionSymptom:
Currently the ASA has two ways to check memory via SNMP. 220.127.116.11.18.104.22.168.48 can be polled
and the OIDs under that will dig into each individual memory pool, including DMA and
GLOBAL SHARED but all the counters are 32-bit which means that the information contained
in them is wrong for some of the modern ASAs that run with more memory. Also, polling some
of these OIDs will cause CPU-hogs on the ASA, as per CSCtx43501.
In recent codes, you can poll the CISCO-ENHANCED-MEMPOOL-MIB, 22.214.171.124.126.96.36.199.221, and it
will provide overall system memory, but it does so with 64-bit counters as well. This is
the only way to get valid memory numbers on platforms with more than 4GB of RAM.
Also, polling this MIB has not caused CPU-hogs for the SNMP process.
Monitoring memory via SNMP polling
The sytem memory.
One service is created.