Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

High Device Memory Utilization After Upgrading from NPM 9.0 up to 9.5

Has anyone else seen any of their managed nodes start reporting a steady increase in memory utilization after an upgrade of the NPM?

I've got a few legacy 3500XL switches that have shown a steady increase in memory utilization that appears to have started at exactly the same time we worked through the upgrade process from NPM 9.0 to NPM 9.5.

The previous memory utilization was quite steady on each of the boxes now showing the increase and the increase has been on a steady upward trend since the upgrade.

My best guess is that it is the SNMP process on these boxes that is consuming the memory and it has been doing so steadily over the past several days.

We are now hitting 80% memory utilization and I'm wondering if NPM 9.5 does something different in the polling or with SNMP that could explain this.

Otherwise, the upgrade went quite smoothly.

Find more posts tagged with

memory_utilization

Accepted answers

consipio

As it turns out, both Solarwinds and Cisco were aware of this issue...

Solarwinds changed the OID's they poll from NPM 9.1 to NPM 9.5 and these legacy Cisco 3524's are on a list of devices known to have problems with these new OID's. The memory leak we are seeing in the IP SNMP process on our 3524's running older code was covered under Cisco bug CSCdt00963 and is corrected in newer IOS.

It looks like unmanaging the node in Orion, removing all SNMP configuration, and deleting the SNMP Engine ID file from flash may have slowed or stabilized the memory leak, but the fix is ultimately an IOS upgrade requiring a reboot.

tools.cisco.com/.../getBugDetails.do

Hopefully that information will help if someone else runs in to this down the road...

All comments

consipio

As it turns out, both Solarwinds and Cisco were aware of this issue...

tools.cisco.com/.../getBugDetails.do

Hopefully that information will help if someone else runs in to this down the road...

Koreets

We've seen this as well, with older cisco routers - 1700 series, upgrade to later IOS ver fixed the leak.