Memory - Cisco service

When this service has a scan interval of less than 5 minutes, the agent may take longer than the scan interval to gather the metrics. As a result, you may notice some scan intervals are not populated.

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.

Service TypeSNMP
Instances on a Device1
Device ClassSwitch/Router
Monitored BySNMP (Windows probe)
Scan Interval15 minutes
Minimum Scan Interval1 minute
Cisco Memory Pool Name IndexThe index of the textual name assigned to the memory pool, which is determined by performing an SNMP walk on ciscoMemoryPoolName (.1.3.6.1.4.1.9.9.48.1.1.1.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 (.1.3.6.1.4.1.9.9.48.1.1.1.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.

OID/Calculation

N-able N-central services use Reverse Polish Notation (RPN) for all calculation formulae.

Metric NameOID/CalculationDescription
Name 1.3.6.1.4.1.9.9.48.1.1.1.2The name of the memory pool being monitored.
Used 1.3.6.1.4.1.9.9.48.1.1.1.5The amount of used memory.
Free 1.3.6.1.4.1.9.9.48.1.1.1.6 The amount of free memory.
TotalUsed + FreeThe total memory for that memory pool.
% Memory Utilization[Used / (Used + Free)] x 100The utilization of memory as a percentage of total memory.