cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
579
Views
0
Helpful
5
Replies
Highlighted

SNMP Trap Config

Dear Community,

 

I have inhereted Cisco Catalyst 2960 access switches for a previous network engineer with an SNMP configuration that I would like to change. I receive the below traps from all switches around 2 am in the morning, which is no use for me. Could you help me to find out what these traps are? Unfortunately I was unable to find anything in the OID search. My final goal would be to remove this trap generation from the switch config.

 

Many thanks.

 

8/9/2020 2:04:08 AM

10.175.133.34

  

SNMPv2-MIB::snmpTrapOID.0 = CISCO-SMI::ciscoMgmt.43.2.0.1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.3.90 = 1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.4.90 = 4
CISCO-SMI::ciscoMgmt.43.1.1.6.1.5.90 = 2

8/9/2020 2:03:36 AM

10.175.133.34

  

SNMPv2-MIB::snmpTrapOID.0 = CISCO-SMI::ciscoMgmt.43.2.0.1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.3.89 = 1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.4.89 = 3
CISCO-SMI::ciscoMgmt.43.1.1.6.1.5.89 = 2

 

5 REPLIES 5
Highlighted
Beginner

Hey,

looked it up in the SNMP Object Navigator:
They are Cisco Configuration management event notifications..

ciscoMgmt.43.2.0.1ciscoConfigManEvent 
ciscoMgmt.43.1.1.6.1.3ccmHistoryEventCommandSource1 : commandLine
2 : snmp
ciscoMgmt.43.1.1.6.1.4ccmHistoryEventConfigSource1:erase
2:commandSource
3:running
4:startup
5:local
6:networkTftp
7:networkRcp
8:networkFtp
9:networkScp
ciscoMgmt.43.1.1.6.1.5ccmHistoryEventConfigDestination1:erase
2:commandSource
3:running
4:startup
5:local
6:networkTftp
7:networkRcp
8:networkFtp
9:networkScp

 

Let me know if that helps.

Best regards
Juls

Highlighted

Hi Juls,

 

Many thanks, I think it does, yes.

 

Assume this is the command line I need to remove then?

 

snmp-server enable traps event-manager

 

Regards,

 

Zoltan

Highlighted

Hi Zoltan,

yes removing that line should to the trick.
Do you have other SNMP traps enabled?

 

BR
Juls

 

Don't forget to rate helpful posts and mark solutions :)

Highlighted

Hi Juls,

 

I have removed that line, however I still receive traps around the same time with similar content, see below.

 

SNMPv2-MIB::snmpTrapOID.0 = CISCO-SMI::ciscoMgmt.43.2.0.1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.3.309 = 1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.4.309 = 3
CISCO-SMI::ciscoMgmt.43.1.1.6.1.5.309 = 2

CISCO-SMI::ciscoMgmt.43.1.1.6.1.3.309 = 1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.4.309 = 3
CISCO-SMI::ciscoMgmt.43.1.1.6.1.5.309 = 2

SNMPv2-MIB::snmpTrapOID.0 = CISCO-SMI::ciscoMgmt.43.2.0.1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.3.309 = 1
CISCO-SMI::ciscoMgmt.43.1.1.6.1.4.309 = 3
CISCO-SMI::ciscoMgmt.43.1.1.6.1.5.309 = 2

 

I have the below SNMP command lines configured:

 

snmp-server community public RO
snmp-server community ********* RO
snmp-server trap link ietf
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps transceiver all
snmp-server enable traps license
snmp-server enable traps auth-framework sec-violation
snmp-server enable traps cluster
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps config-ctid
snmp-server enable traps trustsec-sxp conn-srcaddr-err msg-parse-err conn-config-err binding-err conn-up conn-down binding-expn-fail oper-nodeid-change binding-conflict
snmp-server enable traps energywise
snmp-server enable traps fru-ctrl
snmp-server enable traps entity
snmp-server enable traps event-manager - this line has been removed yesterday
snmp-server enable traps ike policy add
snmp-server enable traps ike policy delete
snmp-server enable traps ike tunnel start
snmp-server enable traps ike tunnel stop
snmp-server enable traps ipsec cryptomap add
snmp-server enable traps ipsec cryptomap delete
snmp-server enable traps ipsec cryptomap attach
snmp-server enable traps ipsec cryptomap detach
snmp-server enable traps ipsec tunnel start
snmp-server enable traps ipsec tunnel stop
snmp-server enable traps ipsec too-many-sas
snmp-server enable traps power-ethernet group 1
snmp-server enable traps power-ethernet police
snmp-server enable traps cpu threshold
snmp-server enable traps vstack
snmp-server enable traps bridge newroot topologychange
snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
snmp-server enable traps syslog
snmp-server enable traps vtp
snmp-server enable traps vlancreate
snmp-server enable traps vlandelete
snmp-server enable traps flash insertion removal
snmp-server enable traps port-security
snmp-server enable traps envmon fan shutdown supply temperature status
snmp-server enable traps stackwise
snmp-server enable traps bulkstat collection transfer
snmp-server enable traps errdisable
snmp-server enable traps mac-notification change move threshold
snmp-server enable traps vlan-membership
snmp-server host 10.166.7.93 version 2c
snmp-server host 10.166.7.93
snmp-server host 10.166.7.93 version 2c
snmp-server host 10.255.17.130 version 2c

 

 

Many thanks for your help.

Highlighted

Hey!

Ah I see - the following line also makes the device send traps every time the configuration is changed:

snmp-server enable traps config

Best regards
Juls

 

Content for Community-Ad