Nagios Support Forum

Hello Tgriep,

Sorry, couldn't come back to from last few days.

I was able to complete the MIB upload process after following your instruction and was able to receive the trap after disabling the firewall on the server. Turning off the firewall is a recommended option.

Also the trap recieved on the nagios doesnt match the trap recieved on the remote machine so we are trying to workout with IPC vendor to through some light on that. I am attaching the trap which was record on the event log.

The traps are coming as Info and we set notification generation for critical alerts only.. How do change this alert from Info to critical so that we receive notificaiton each time the trap is received.

Thank you..

To get a Critical Status when a Trap is received, a custom event entry has to be added in the /etc/snmp/snmptt.conf file.
In the following Trap Tutorial article.
https://support.nagios.com/kb/article/n ... al-77.html

Search for a section called "Create Custom Events In SNMPTT". It has the steps needed to create a custom event.

Thank you for the document I had followed the steps mentioned in the document but still the same issue. I see few traps coming as Info only.

Also for one of the test, the trap sent by the server is not captured by the Nagios it is showing non relevant information. I am attaching the information sent by the remote machine as against the trap shown on the nagios side. can you help in identifying the issue here.

I am attaching both the document with the appropriate file name

The trap that shows in the nagios UI is just the latest trap received.

We tried to replicate the same but the Nagios doesn't give us the full details. The information that we were looking for was a cold start of the device being rebooted.

Also even after making the changes in the snmp.conf the data is still coming as Info and not changing to critical.

Regards..

naranant wrote:Also even after making the changes in the snmp.conf the data is still coming as Info and not changing to critical.

the changes should be in /etc/snmp/snmptt.conf
If that is what you changed can you share them because it is the status in that file mapped to the MIB/OID that determines if it is a critical state or not.

Hello Scott,

Please find the snmptt.conf attached. Do let me know..

Regards

naranant wrote:Also even after making the changes in the snmp.conf the data is still coming as Info and not changing to critical.

I don't know what you changed in that file...

Also, I don't fint any OID's in the file that start with .1.3.6.1.4.1.1453.4.9.1.5.x.x.x like you show in the IP Capture

Hello Scott,

The MIB's were uploaded and the commands were executed as given in the earlier thread. So I am not sure why the OID's are not reflecting the snmptt.conf.

So can you confirm if the OID should get loaded as part of the MIB uploading or do I need to manually define the OID in the configuration file?

I am setting this for the first time. So highly appreciate if I get the step by step instruction in making this work.

Regards..

I'm not familiar with this hardware and MIBS but if you ran the addmib command and they didn't get added, I would suspect that the OID's were not part of the MIB's you uploaded.

naranant wrote:So can you confirm if the OID should get loaded as part of the MIB uploading or do I need to manually define the OID in the configuration file?

You may be able to create them yourself however I can't give much guidance as I will not know what should be normal, critical etc.