Nagios Support Forum

Ok I was able to fix that. Apparently it wasn't saving the line and I had to be modified. Right now receiving critical alerts from the application do get interpreted by Nagios and that is working great. At this time it is just a matter of getting a reset which apparently the application doesn't send. Is there a way for nagios to reset the alert to an ok state after a specified amount of time?

To set the service to auto clear, you would enable active checks on the service with a check interval you want for the message to be cleared.
The settings are in the Check Settings TAB.
If the service is using the xiwizard_passive_service template, it will be cleared out using the check_dummy plugin with an OK state and this message "No data received yet.".
That is how you can clear out the trap after a specified time.

So in the trap definition when I state this it means match this condition.

MATCH $6 : 1


When a less than is used for matching does this one mean include 1 or only 0

MATCH $6 < 1



As another example, does this one mean it includes 2 or only items 3, 4 and 5?

MATCH $6 > 2

When you specify this That will only be true if the value is 0.

When you specify this It will be true if the value is 3, 4, 5 or greater.

For more details on the MATCH statement, see the following link.
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH

Thank you. I recently changed the check from IP address to the actual hostname and now the defined checks aren't alerting on the service check nor are they showing up in the history of the service check states. Why would that be?.....

Scratch that. I recevied the alerts in my e-mail but the history doesn't show and even though I changed the name from the IP to hostname the alerts are still coming through with IP address as the hostname. How can I change this to be hostname instead of IP?

If you look in the /etc/snmp/snmptt.ini file, the DNS option should already be enabled.

If not, set it to a 1 and restart snmptt.

Also, the Nagios server has to have access to a DNS server that can resolve the IP address to the hostname.
Or you will have to add the IP address and Hostname to the /etc/hosts file on the Nagios server.

Because you are using hostnames now, you will have to create new Host and Service checks in xi to match the hostname.
The simplest thing to do is to configure it in the Admin > Unconfigured Objects menu and that will create the objects for you and match up the names.

What do you mean match up the names?

Mon Sep 28 11:04:15 2020 .1.3.6.1.4.1.4184.2.0.2 Critical "Fatal" <server IP> - Received trap "oplGenericV2Trap" with variables "
enterprises.4184.2.1.2.1.2.23.67.101.114.110.101.114.95.79.80.69.78.76.105.110.107.95.50.52.46.49.45.48.53:Cerner OPENLink 24.1-05
enterprises.4184.2.1.2.1.5.23.67.101.114.110.101.114.95.79.80.69.78.76.105.110.107.95.50.52.46.49.45.48.53:1
enterprises.4184.2.2.2.1.1.13.73.67.79.84.50.52.49.53.72.48.65.72.70:ICOT2415H0AHF
enterprises.4184.2.5.1.0:EN92
enterprises.4184.2.5.2.0:1
enterprises.4184.2.5.3.0:RELOAD - Alert process reload by user request.
enterprises.4184.2.5.4.0:2020-09-28 11:04:15
enterprises.4184.2.5.8.0:0
enterprises.4184.2.5.9.0:0"


This snmp trap came out as critical even though it is a 1. Screenshot of my definition.

Since you are setting up traps to use host names, you have to create new Hosts that match the new names for the devices that are sending the traps now, that is what I meant by "match up the names".

What do you have setup for the MATCH in the Critical Trap definition?

Critical definition attached.