Memory - Cisco service
Memory - Cisco monitors memory pool utilization on any Cisco device using SNMP. The device must publish its memory usage in the CISCO-MEMORY-POOL-MIB.
This service cannot use Self Healing.
|Instances on a Device||1|
|Monitored By||SNMP (Windows probe)|
|Scan Interval||15 minutes|
|Cisco Memory Pool Name Index||The index of the textual name assigned to the memory pool, which is determined by performing an SNMP walk on ciscoMemoryPoolName (.18.104.22.168.22.214.171.124.126.96.36.199.2).|
|Cisco Memory Pool Name Value||The value of the textual name assigned to the memory pool, which is determined by performing an SNMP walk on ciscoMemoryPoolName (.188.8.131.52.184.108.40.206.220.127.116.11.2).|
If the MEMPOOL_GLOBAL_SHARED pool information is queried using SNMP, it results in CPU hogs. It is evident that you might see packet drops/overruns at times of bursty/overloaded traffic when you use SNMP to poll memory statistics that require the ASA to query the information through huge chunks of memory that it is associated which results in SNMP related CPU hogs.
To monitor Cisco ASA memory, use a NRC template.
SolarWinds N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
|Name||18.104.22.168.22.214.171.124.126.96.36.199.2||The name of the memory pool being monitored.|
|Used||188.8.131.52.184.108.40.206.220.127.116.11.5||The amount of used memory.|
|Free||18.104.22.168.22.214.171.124.126.96.36.199.6||The amount of free memory.|
|Total||Used + Free||The total memory for that memory pool.|
|% Memory Utilization||[Used / (Used + Free)] x 100||The utilization of memory as a percentage of total memory.|