Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
I don't have a copy of the CISCO-SYSLOG-MIB file, can you post it?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
Try replacing your current OID setting with the following.
Take a look at the MATCH settings and if it still fails, you may have to adjust the value on the Warning OID if the device does not send a 1 as the warning severity level.
Code: Select all
EVENT clogMessageGenerated .1.3.6.1.4.1.9.9.41.2.0.1 "Status Events" Normal
FORMAT When a syslog message is generated by the device a $*
MATCH $1: 0
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "When a syslog message is generated by the device a $*"
SDESC
When a syslog message is generated by the device a
clogMessageGenerated notification is sent. The
sending of these notifications can be enabled/disabled
via the clogNotificationsEnabled object.
Variables:
1: clogHistFacility
2: clogHistSeverity
3: clogHistMsgName
4: clogHistMsgText
5: clogHistTimestamp
EDESC
EVENT clogMessageGenerated .1.3.6.1.4.1.9.9.41.2.0.1 "Status Events" Warning
FORMAT When a syslog message is generated by the device a $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "When a syslog message is generated by the device a $*"
MATCH $1: 1
SDESC
When a syslog message is generated by the device a
clogMessageGenerated notification is sent. The
sending of these notifications can be enabled/disabled
via the clogNotificationsEnabled object.
Variables:
1: clogHistFacility
2: clogHistSeverity
3: clogHistMsgName
4: clogHistMsgText
5: clogHistTimestamp
EDESC
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
It still fails to register....tgriep wrote: Take a look at the MATCH settings and if it still fails, you may have to adjust the value on the Warning OID if the device does not send a 1 as the warning severity level.
This is what was in the snmptt.log file today but no SNMP notification evenn after the suggested change:
Code: Select all
Fri Jan 19 07:26:46 2018 .1.3.6.1.4.1.9.9.41.2.0.1 Normal "Status Events" SomSW02 - When a syslog message is generated by the device a RTT 5 OPER_TIMEOUT condition occurred, entry number = 1 34:1:07:33.84
Code: Select all
EVENT clogMessageGenerated .1.3.6.1.4.1.9.9.41.2.0.1 "Status Events" Normal
FORMAT When a syslog message is generated by the device a $*
EXEC /usr/local/bin/snmptraphandling.py "$r" "SNMP Traps" "$s" "$@" "$-*" "When a syslog message is generated by the device a $*"
MATCH $1: 0
SDESC
When a syslog message is generated by the device a
clogMessageGenerated notification is sent. The
sending of these notifications can be enabled/disabled
via the clogNotificationsEnabled object.
Variables:
1: clogHistFacility
2: clogHistSeverity
3: clogHistMsgName
4: clogHistMsgText
5: clogHistTimestamp
EDESC
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
Do you see that OID in the snmpttunknown.log file?
If so, post it here.
If so, post it here.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
There is nothing in the SNMPTTUnknown log file whatsoever for today.tgriep wrote:Do you see that OID in the snmpttunknown.log file?
If so, post it here.
I would not have expected anything in the SNMPTTUnknown log as the OID .1.3.6.1.4.1.9.9.41.2.0.1 exists in the SNMPTT.conf file, but it is not triggering a response in to the GUI.....am I correct on that assumption ?
Re: Cisco RTT / IPSLA showing SNMP Traps in hex on Nagios
Here is what I would do, remove both of the entries from the snmptt.conf file and restart snmptt
Then force a good trap from the device and a bad trap.
Because the OID it removed, they should show up in the snmpttunknown.log file. Post those entries here.
Then force a good trap from the device and a bad trap.
Because the OID it removed, they should show up in the snmpttunknown.log file. Post those entries here.
Be sure to check out our Knowledgebase for helpful articles and solutions!