I have a custom device Trap defined as following in the Mib already imported in PRTG.
I'm able to receive traps bat I'm not able to manage the SEVERITY and the Summary information.
radiostatusBiteTrap TRAP-TYPE
ENTERPRISE elman
VARIABLES { radiostatusResourceName, radiostatusBiteCode, radiostatusBiteMsg }
DESCRIPTION "Remote radio device in ERROR status."
SUMMARY "Remote radio device %s in ERROR status: code %d - %s"
ARGUMENTS {0, 1, 2}
SEVERITY CRITICAL
STATE NONOPERATIONAL
::= 101
This is what I can see on the Trap Receiver sensor Bindins fields, but I cannot see the "SUMMARY" and SEVERITY fieds:
SNMPv2-SMI-v1::enterprises.33205.100.100.0=ELM475
SNMPv2-SMI-v1::enterprises.33205.100.104.0=52
SNMPv2-SMI-v1::enterprises.33205.100.105.0=AIS: internal GNSS failure - Antenna connector is open
Article Comments
Trap contains that information (i.e. checked with Wireshark and other SNMP Manager) but these infos aren't in a "human" readable format: these infos are encoded in the MIB format (i.e. see original post). What I'm missing is how to set in the SNMP Trap receiver the TRAP MIB that contains "TRAP-TYPE" information.
Feb, 2014 - Permalink
Just to check, how exactly did you "import" the MIB? Please be aware that, for the SNMP Trap Receiver Sensor, the MIB needs to be in the "\Mib"-subfolder of PRTGs program files directory, as MIB-File (not OIDLib-File).
Feb, 2014 - Permalink
It seems to work better,
now Bindings field is more clear:
ELMAN-MIB::radiostatusResourceName.0=ELM198 ELMAN-MIB::radiostatusAlarmCode.0=52 ELMAN-MIB::radiostatusAlarmMsg.0=AIS: internal GNSS failure - Antenna connector is open
However it isn't enough for my purposes, because, in order to manage a kind of "Severity", it is useful to have also other information (e.g. as described here ).
Feb, 2014 - Permalink
I'm afraid PRTG cannot have the Trap Sensor change into Error state with a certain trap being received, and only go into green UP state again, if a certain different trap was received. The suggestion is to work with according filters here, where the sensor will open a Ticket-Notification then, which has to be closed by a user then.
Feb, 2014 - Permalink
Hello,
thank you very much for your KB-Post. The "bindings"-column should show all contents of a trap (except the standard fields like source ip, etc.). Did you check with Wireshark if the trap does contain a 'Severity' field indeed?
best regards.
Feb, 2014 - Permalink