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

SNMP Queries Configurable

We are having issues with layer 2 and layer 3 topology polling spiking the CPU on Catalyst 6500 series switches (with SUP 2, SUP 720 and SUP 2t). It would be nice if the query could be configurable to run specific pieces individually instead of sending a bulk group of queries causing a CPU spike.

Find more posts tagged with

Status: None

Comments

bspencer63

Scott,

You might want to check out this thread: Re: Re: Custom SNMP Device Templates

Short summary:

Create a custom SNMP Device Template using the device OID/MIBs and then apply it to the device instead of the pre-built template.

Hope this help.

BSpencer

rschroeder

I had this same problem--snmp queries were being dropped by my 6509's, resulting in an inability to use Switch Port Mapper from the Engineer's Toolset. Too many devices were incorrectly trying to learn data via snmp from the 6509's.

I called TAC, they told me to identify the sources via a report that can be generated on the 6509's, and determine if those sources were appropriate. I found many other departments using snmp to inappropriately poll many subnet ID's, broadcast addresses, and hardware to which these departments did not have community strings or rights.

Remediating this was time-consuming but it dealt with the source of the problem instead of with the symptom. I recommend you talk with TAC and get the process to discover whether you have problematic snmp sources hitting your 6500's and correct them / eliminate them, and educate those who set them up to do inappropriate polling. Explain how their actions tie up resources on the 6500's and cause problems for network management.

Eventually I retired the 6500's and put in bigger hardware, then contacted the snmp polling teams and asked them to test by once-again configuring their polling engines to do inappropriate polling. The new hardware handled the load much better than the old 6500's.

Finally, I had them remove the inappropriate polling again, and now I alert on inappropriate polling to help discover and prevent problems caused by ignorance. And I have hardware in place that can tolerate the "bad" traffic easily without causing me any other issues (like losing info from Switch Port Mapper).