Hello and thank you for coming: I could use your help!
I am running a new LAN with quite a few Cisco3560 switches (12.2(20)SE4 variety) and I am using Network Instruments Observer for SNMP monitoring of the switches.
I initially configured the Cisco's to use the Observer station to send traps to and enabled all traps on all switches, figuring I could disable the trap types I didn't want to see as became familiar with the 3560's.
When I fired up Observer on the new LAN, I noticed I was getting tons and gallons of traps. Initially using the CMS web interface, I tried turning off various traps, and finally disabling traps altogether. The traps kept coming and I decided the trap portion of the web interface doesn't work well (I had problems with the time-server section as well). So I switched to the CLI interface and did an no snmp-serv enable trap xyz and disabled all of the trap types for the switches, as well as just executing no snmp-serv enable traps. Finally I tried a no logging trap.
After all of this the traps are still coming. I can get a run of 20 in 10 seconds from a single switch. They are always the same 1.3.6.1.4.1.9.1 with no other information or specifiers even after loading all of the MIBs as instructed on cisco's web site for getting their traps to make sense.
Does anyone have any ideas as to where the flood is coming from, how to turn it off, and how to restore normal trap operation for the truely important traps?
Thanks for your help,
Feeling Trapped
I am running a new LAN with quite a few Cisco3560 switches (12.2(20)SE4 variety) and I am using Network Instruments Observer for SNMP monitoring of the switches.
I initially configured the Cisco's to use the Observer station to send traps to and enabled all traps on all switches, figuring I could disable the trap types I didn't want to see as became familiar with the 3560's.
When I fired up Observer on the new LAN, I noticed I was getting tons and gallons of traps. Initially using the CMS web interface, I tried turning off various traps, and finally disabling traps altogether. The traps kept coming and I decided the trap portion of the web interface doesn't work well (I had problems with the time-server section as well). So I switched to the CLI interface and did an no snmp-serv enable trap xyz and disabled all of the trap types for the switches, as well as just executing no snmp-serv enable traps. Finally I tried a no logging trap.
After all of this the traps are still coming. I can get a run of 20 in 10 seconds from a single switch. They are always the same 1.3.6.1.4.1.9.1 with no other information or specifiers even after loading all of the MIBs as instructed on cisco's web site for getting their traps to make sense.
Does anyone have any ideas as to where the flood is coming from, how to turn it off, and how to restore normal trap operation for the truely important traps?
Thanks for your help,
Feeling Trapped