Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Cisco ASR Showing 95% - 98% Memory Used

Cisco ASR Showing 95% - 98% Memory Used

Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 49 Votes: 6 Revisions: 11

Overview

 

You  have an issue with  ASR Memory Consumption showing 100% in Orion . 

Cisco ASR.PNG

Environment

NPM 11.5 and later

Cause

The PollerChecker Tool reflects no other Memory Poller are been responded by the Device.

 

SolarWinds Knowledge Base :: How to Use the Poller Checker Tool

pollerchecker.PNG

ONLY Responded Memory Poller is CiscoGen3.

 

We then checked from the CiscoGen3 Memory poller i found following .

 

EXPLANATION OF EACH OID TABLE FUNCTION 

cisco MemoryPoolName 1.3.6.1.4.1.9.9.48.1.1.1.2

Cisco ciscoMemoryPoolUsed 1.3.6.1.4.1.9.9.48.1.1.1.5

Cisco CiscoMemoryPoolFree 1.3.6.1.4.1.9.9.48.1.1.1.6

 

NAME OF MEMORY

.1.3.6.1.4.1.9.9.48.1.1.1.2.1 = STRING: "processor"

.1.3.6.1.4.1.9.9.48.1.1.1.2.6 = STRING: "reserved"

.1.3.6.1.4.1.9.9.48.1.1.1.2.7 = STRING: "image"

 

TOTAL MEMORY USED BY EACH NAME

.1.3.6.1.4.1.9.9.48.1.1.1.5.1 = GAUGE32: 1791774344

.1.3.6.1.4.1.9.9.48.1.1.1.5.6 = GAUGE32: 134217728

.1.3.6.1.4.1.9.9.48.1.1.1.5.7 = GAUGE32: 66994200

 

TOTAL PORTION OF MEMORY FREE

.1.3.6.1.4.1.9.9.48.1.1.1.6.1 = GAUGE32: 86892544

.1.3.6.1.4.1.9.9.48.1.1.1.6.6 = GAUGE32: 0

.1.3.6.1.4.1.9.9.48.1.1.1.6.7 = GAUGE32: 0

 

CALCULATION :

 

TOTAL USED MEMORY

1791774344 + 134217728 + 66994200 = 1992386272

TOTAL FREE MEMORY

0+0+86892544 = 86892544

TOTAL MEMORY

1992386272 + 86892544 = 2079278816

% MEMORY  UTILIZATION

1992386272 % 2079278816  = 95.8 %

 

Summary:

  • Memory poller for devices which support CISCO-MEMORY-POOL MIB (various Cisco devices)
  • <support pollertype="N.Memory.SNMP.CiscoGen3">
  • Poller utilizes GetSubtree request to gather used memory using OID:
  • ciscoMemoryPoolUsed = 1.3.6.1.4.1.9.9.48.1.1.1.5
  • Poller utilizes GetSubtree request to gather free memory using OID:
  • ciscoMemoryPoolFree = 1.3.6.1.4.1.9.9.48.1.1.1.6
  • Used memory is computed as SUM of all ciscoMemoryPoolUsed returned values.
  • Free memory is computed as SUM of all ciscoMemoryPoolFree returned values.
  • Total memory is computed as SUM of used and free memory.

 

 

Conclusion:

By calculation above provided by the Node OID tables values .

 

Orion is marked the memory correctly by consuming 95% .

 

However We found the device is responded to following Poller for memory calculation other then the standard Cisco .CISCO-ENHANCED-MEMPOOL-MIB

 

CISCO-ENHANCED-MEMPOOL-MIB

 

Memory Free

Memory Used

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.1 = COUNTER64: 6196785152

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.1 =

COUNTER64: 2198077384

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.2 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.2 =

COUNTER64: 134217728

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.3 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.3 =

COUNTER64: 60565808

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.1 = COUNTER64: 4756275200

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.1 =

COUNTER64: 1417358984

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.2 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.2 =

COUNTER64: 134217728

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.3 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.3 =

COUNTER64: 66994200

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.1 = COUNTER64: 6160363520

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.1 =

COUNTER64: 2234499016

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.2 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.2 =

COUNTER64: 134217728

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.3 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.3 =

COUNTER64: 60565808

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.1 = COUNTER64: 4381138944

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.1 =

COUNTER64: 1792495240

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.2 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.2 =

COUNTER64: 134217728

.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.3 = COUNTER64: 0

.1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.3 =

COUNTER64: 66994200

Resolution

 

We have created Device Poller for such devices 

(Download from below thwack post )
  1. https://thwack.solarwinds.com/docs/DOC-186977

 

Cisco ASR Memory Poller is attached .

Download  .

2. Go to Orion Web page > Settings > Manage Nodes >

pollermg.PNG

Import the Poller

You will Notice "Cisco ASR Devices" poller will be included

importp.PNG

Now go to the Node and do "List Resources "

Select the "Cisco ASR Devices" Poller

asrmem.PNG

> Submit

Leave the System running for 10 ~ 15 min for the polling .

confirmed the system is now showing correct memory .

memoryasr.PNG

 

 

 

 

Last modified
21:53, 22 Jun 2016

Tags

Classifications

Public