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
Store

Cisco CPU spiking related to SW NPM?

Has anyone reading this experienced CPU spiking (90%+) on a Cisco device as a direct result of regular SNMP polling? Every 5 minutes (to the second), I'm getting a CPU utilization spike on the device to which our NPM server is connected... but not any of the other, virtually identical (as in models, configs, loads, connections, etc) devices.

Reading Cisco documentation, it sounds like it's nothing to be concerned about as process prioritization won't allow low-priority stuff to affect routing, etc. I also recognize that there's a difference between how things should work and what's actually going on.

If anyone has had experience with this and has found a workaround/fix, I would love to hear about it. Thanks all.

Find more posts tagged with

Accepted answers

All comments

Mithrilhall

You say virtually identical devices; what IOS are you running on the affected device and the identical devices?

FormerMember

quote:Originally posted by Mithrilhall

You say virtually identical devices; what IOS are you running on the affected device and the identical devices?

12.2(25)EWA8 on everything.

FormerMember

quote:Originally posted by nwood

Has anyone reading this experienced CPU spiking (90%+) on a Cisco device as a direct result of regular SNMP polling? Every 5 minutes (to the second), I'm getting a CPU utilization spike on the device to which our NPM server is connected... but not any of the other, virtually identical (as in models, configs, loads, connections, etc) devices.

Reading Cisco documentation, it sounds like it's nothing to be concerned about as process prioritization won't allow low-priority stuff to affect routing, etc. I also recognize that there's a difference between how things should work and what's actually going on.

If anyone has had experience with this and has found a workaround/fix, I would love to hear about it. Thanks all.

I had what sounds as something very simular. I Upgraded the Orion server to Server 2003. The problem still occurred. For the past week I've been exiting the Orion system managered when I've been finshed with it. I used to just minimize it. It's been better this week. I easiest way to clear the problem was to reboot the Orion server.

Brain Riess
Hamilton, Ontario
Canada

FormerMember

quote:I had what sounds as something very simular. I Upgraded the Orion server to Server 2003. The problem still occurred. For the past week I've been exiting the Orion system managered when I've been finshed with it. I used to just minimize it. It's been better this week. I easiest way to clear the problem was to reboot the Orion server.

Brain Riess
Hamilton, Ontario
Canada

So you saw the spiking go away with a reboot of the Orion server?