01-17-2021 02:32 AM - edited 01-17-2021 02:33 AM
I have configured and working deployment - catalyst 3750 sending traps to zabbix, which are received and processed correctly.
Configured to send CPU notification via:
snmp-server enable traps cpu threshold
Q: Do i also have to configure threshold values and statistic as stated in examples from link below or that is not necesarry?:
process cpu statistics limit entry-percentage 40 size 300 process cpu threshold type total rising 80 interval 5 falling 20 interval 5
Asking if there is any default value already configured, or traps are not sent until i configure specific values. I found for ASA there is 95% for critical threshold, but found no such information for Catalyst or Nexus switches.
01-17-2021 05:13 AM
- There will certainly be default values. Perhaps they could be revealed by running command completion with question marks when entering one of the commands. A ? at a certain point may provide short documentation of the intended command with defaults being listed (not sure though). Another source maybe the MIB for the relevant (trap-)OID's for the switch-model were defaults might be documented too. Or perhaps in show running-config all.
M.
01-19-2021 12:01 PM - edited 01-19-2021 12:02 PM
Well, in both cases, i found no default value. In "show running-config all", command for threshold was not mentioned also. I changed it to 30% to generate example trap and then unconfigured with
no process cpu threshold type total
any idea if default value is taken back for being used or i unconfigured it completely? I still can not confirm it was set by default.
Also posting SNMPv3 trap i recieved, might be useful for someone.
Provided by "snmp-server enable trap cpu threshold" and "process cpu threshold type total rising 30 interval <number>":
DISMAN-EXPRESSION-MIB::sysUpTimeInstance type=67 value=Timeticks: (1216327920) 140 days, 18:41:19.20 SNMPv2-MIB::snmpTrapOID.0 type=6 value=OID: CISCO-PROCESS-MIB::cpmCPURisingThreshold CISCO-PROCESS-MIB::cpmCPURisingThresholdValue.1.total type=2 value=INTEGER: 30 CISCO-PROCESS-MIB::cpmCPUTotalMonIntervalValue.1 type=2 value=INTEGER: 32 CISCO-PROCESS-MIB::cpmCPUInterruptMonIntervalValue.1 type=2 value=INTEGER: 1 CISCO-PROCESS-MIB::cpmProcExtUtil5SecRev.1.174 type=2 value=INTEGER: 19 CISCO-PROCESS-MIB::cpmProcessTimeCreated.1.174 type=67 value=Timeticks: (357334455) 41 days, 8:35:44.55 CISCO-PROCESS-MIB::cpmProcExtUtil5SecRev.1.86 type=2 value=INTEGER: 2 CISCO-PROCESS-MIB::cpmProcessTimeCreated.1.86 type=67 value=Timeticks: (357334457) 41 days, 8:35:44.57 CISCO-PROCESS-MIB::cpmProcExtUtil5SecRev.1.129 type=2 value=INTEGER: 1 CISCO-PROCESS-MIB::cpmProcessTimeCreated.1.129 type=67 value=Timeticks: (357334362) 41 days, 8:35:43.62
Provided by "snmp-server enable traps syslog" (i guess)
DISMAN-EXPRESSION-MIB::sysUpTimeInstance type=67 value=Timeticks: (1216247919) 140 days, 18:27:59.19 SNMPv2-MIB::snmpTrapOID.0 type=6 value=OID: CISCO-SYSLOG-MIB::clogMessageGenerated CISCO-SYSLOG-MIB::clogHistFacility.18498 type=4 value=STRING: "SYS" CISCO-SYSLOG-MIB::clogHistSeverity.18498 type=2 value=INTEGER: 2 CISCO-SYSLOG-MIB::clogHistMsgName.18498 type=4 value=STRING: "CPURISINGTHRESHOLD" CISCO-SYSLOG-MIB::clogHistMsgText.18498 type=4 value=STRING: "Threshold: Total CPU Utilization(Total/Intr): 31%/0%, Top 3 processes(Pid/Util): 174/20%, 86/3%, 129/1%" CISCO-SYSLOG-MIB::clogHistTimestamp.18498 type=67 value=Timeticks: (1216247917) 140 days, 18:27:59.17
on:
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.0(1)SE, RELEASE SOFTWARE (fc1)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide