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

Cisco 6500/Sup720 CPU monitoring WAY off

Our CPU was running at 98-99% utilization for over 72 hours. Solarwinds was reporting the utilization at 60%. Isolated the issue down to IP redirects. Fixed the problem the CPU drops to 5%. Solarwinds is reporting the utilization as 46%. I downloaded a trial of 3dSNMP and they show CPU utilization of 5%. Has anyone had similar issues or know of a bug with Solarwinds CPU polling?

Find more posts tagged with

Accepted answers

All comments

sedmo

See if this thread is helpful.

slinky103

It is helpful, but why would this fall back on the IOS configuration? To me this is a Solarwinds polling issue that needs to be resolved. We have 1000+ devices and shouldn't have to make this change to get accurate CPU polling.

Not trying to jump on you Just a little bit frustrated. We have alerts setup to trigger when CPU exceeds 85%. This could have been caught a long time ago but wasn't due to this issue.

Donald_Francis

I have not had this issue myself but I can tell you from experience sometimes less used MIBs on Cisco's end do not get the highest level of attention in every release of IOS.

Also, what is going to make it even sillier is you are only monitoring the RP and not the SP, only half the game on a 6500.

sedmo

I agree. It would be nice if NPM handled cpu utilization for devices with multiple cpu's differently. Here is a link to Cisco's web site that has some good information regarding cpu utilization collection with SNMP.

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a94.shtml

sedmo

I guess they could argue that both the RP and SP utilization are being monitored since NPM is retrieving the utilization data for both of them. The problem is that the two values get averaged together. So if the RP is running at 80% and the SP is running at 4% NPM will show the CPU utilization for the device as 42%.

epenney

We are experiencing a very similiar issue. Through process of elimination we discovered it was Openview NNM polling that was having the greatest negative effect on 6513 cpu. Orion did not appear to be a neg factor. Our chassis is pretty loaded, so our Orion polling is 120sec for polling and 10min for statistics. This topic is of interest and I will be following it for further insight/experiences from other customers.

jonchill

After spending the morning working my way through it I've produced a pair of UnDP pollers one for Route and the other for Switch processor utilisation.

They may work with standalone 6500's but they were created from a VSS pair so may need tweaking to get working exactly how you want them.

Normally the Solarwinds chart would show flat at around 10 - 12% utilisation once I'd left the UnDP charts for a while it gave a true representation of utilisation at the time RP was at 18% and SP was at 8%.

I do think that Solarwinds needs to put some form of warning on there CPU charts as this issue is the same for multi core servers.

Jon