Need some help with an Snmp Entry.
Need some help with an Snmp Entry.
Hello Guys,
I need some help with an trap value.
We use an snmp trap from an ow-server to give alarm when our air condense water reach a limit.
it looks like this:
EVENT wateralertOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" Testing
FORMAT Water Status $+1
EXEC /usr/local/nagios/libexec/submit_check_result ow-server "Water Alert level 1" 0 "Water status is ok"
MATCH $+1:(31440.2.2.1.1.4:1)
SDESC
ow-server alert
EDESC
The entry was created a long time ago and i cannot verify exactly what these line do:
MATCH $+1:(31440.2.2.1.1.4:1)
I even tried to resaerch the value on the snmptt Homepage. But i haven't found an value which belongs to the Match Variable §+1
Does anybody know which effect these line of code has ?
Thanks in advance for help
regards skyerjoe
I need some help with an trap value.
We use an snmp trap from an ow-server to give alarm when our air condense water reach a limit.
it looks like this:
EVENT wateralertOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" Testing
FORMAT Water Status $+1
EXEC /usr/local/nagios/libexec/submit_check_result ow-server "Water Alert level 1" 0 "Water status is ok"
MATCH $+1:(31440.2.2.1.1.4:1)
SDESC
ow-server alert
EDESC
The entry was created a long time ago and i cannot verify exactly what these line do:
MATCH $+1:(31440.2.2.1.1.4:1)
I even tried to resaerch the value on the snmptt Homepage. But i haven't found an value which belongs to the Match Variable §+1
Does anybody know which effect these line of code has ?
Thanks in advance for help
regards skyerjoe
Nagios Core 3.5.1
Checkmk 1.2.4p5
Checkmk 1.2.4p5
Re: Need some help with an Snmp Entry.
It does variable substitution:
http://snmptt.sourceforge.net/docs/snmptt.shtml
$+n - Expand variable-binding n (1-n) in the format of variable name:value (see Note 2,3,5)
variable substitutions: $vn (variable name), $+n(variable name:value), $-n (variable name (type):value), $+* (same as $+n but wildcard), and $-* (same as $-n but wildcard). Translation of the variable name using the MIB requires the UCD-SNMP / Net-SNMP Perl module.
Taken from here:Note (2):
If translate_integers is enabled in the snmptt.ini file, SNMPTT will attempt to convert integer values received in traps into text by performing a lookup in the MIB file.
You must have the UCD-SNMP / Net-SNMP Perl module installed for this to work and you must enable support for it by enabling net_snmp_perl_enable in the snmptt.ini file.
For this feature to work, you must ensure UCD-SNMP / Net-SNMP is configured correctly with all the required MIBS. If the option is enabled, but the value can not be found, the integer value will be used. If the MIB files are present, but translations do not occur, ensure UCD-SNMP / Net-SNMP is correctly configured to process all the required mibs. This is configured in the UCD-SNMP / Net-SNMP snmp.conf file. Alternatively, you can try setting the mibs_enviroment variable in snmptt.ini to ALL (no quotes) to force all MIBS to be initialized at SNMPTT startup.
If translate_integers is enabled while using stand-alone mode, it may take longer to process each trap due to the initialization of the MIB files.
Note (3):
$vn, $+n and $-n variable names and variable type are translated into the text name by performing a lookup in the MIB file. You must have the UCD-SNMP / Net-SNMP Perl module installed for this to work and you must enable support for it by enabling net_snmp_perl_enable in the snmptt.ini file. If net_snmp_perl_enable is not enabled, the $vn variable will be replaced with the text 'variablen' where n is the variable number (1+).
For the name translation to work, you must ensure UCD-SNMP / Net-SNMP is configured correctly with all the required MIBS. If the option is enabled and the correct name is not returned, ensure UCD-SNMP / Net-SNMP is correctly configured to process all the required mibs. This is configured in the UCD-SNMP / Net-SNMP snmp.conf file. Alternatively, you can try setting the mibs_enviroment variable in snmptt.ini to ALL (no quotes) to force all MIBS to be initialized at SNMPTT startup.
Note (5):
If translate_oids is enabled in the snmptt.ini file, SNMPTT will attempt to convert any numeric OIDs found inside the variables passed inside the trap to symbolic form. You must have the UCD-SNMP / Net-SNMP Perl module installed for this to work and you must enable support for it by enabling net_snmp_perl_enable in the snmptt.ini file. If net_snmp_perl_enable is not enabled, it will default to using the numeric OID.
Net-SNMP 5.0.9 and earlier does not support including the module name (eg: IF-MIB::) when translating an OID and most of the 5.0.x versions do not properly tranlsate numeric OIDs to long symbolic names. A patch is available for 5.0.8+ that is inlcuded in Net-SNMP 5.1.1 and higher. The patch is available from the Net-SNMP patch page.
http://snmptt.sourceforge.net/docs/snmptt.shtml
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Need some help with an Snmp Entry.
To expand on what @ssax has said ...
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH
This EVENT string defines is the OID that triggers SNMPTT to action this trap and execute the EXEC line.
However the MATCH statement is additional criteria that MUST be met before the EXEC line is executed.
There are two values separated by a :
$+1 will be the name and value of the variable that has come in the trap.
The number in the brackets ... the brackets represent a regular expression.
So if $+1 = 31440.2.2.1.1.4:6 then the trap wouldn't match because it doesn't match 31440.2.2.1.1.4:1 and hence the EXEC would not be executed and Nagios would not be notified.
SNMPTT is extremely powerful
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH
Code: Select all
EVENT wateralertOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" Testing
However the MATCH statement is additional criteria that MUST be met before the EXEC line is executed.
$+* - Expand all variable-bindings in the format of variable name:value (see Note 2,3,5)
$+n(variable name:value)
Code: Select all
MATCH $+1:(31440.2.2.1.1.4:1)
Code: Select all
$+1
(31440.2.2.1.1.4:1)
The number in the brackets ... the brackets represent a regular expression.
So if $+1 = 31440.2.2.1.1.4:6 then the trap wouldn't match because it doesn't match 31440.2.2.1.1.4:1 and hence the EXEC would not be executed and Nagios would not be notified.
SNMPTT is extremely powerful
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Need some help with an Snmp Entry.
Hey guys,
Thanks for helping
Really helpful explanations
One more questions i have to ask
I just want to test some snmptt entries against ...
So I use the ireasoninig browser for it but i'm not sure in which way i have to set the values in the interface for an proper test.
Here is an picture from it:
Is this correct or does it not fit the Trap definition which i've described before.
regards skyerjoe
Thanks for helping
Really helpful explanations
One more questions i have to ask
I just want to test some snmptt entries against ...
So I use the ireasoninig browser for it but i'm not sure in which way i have to set the values in the interface for an proper test.
Here is an picture from it:
Is this correct or does it not fit the Trap definition which i've described before.
regards skyerjoe
Nagios Core 3.5.1
Checkmk 1.2.4p5
Checkmk 1.2.4p5
Re: Need some help with an Snmp Entry.
Take a look in the /var/log/snmptt/snmpttunknown.log file to see if the OID that you sent earlier is in there.
Try sending this OID to see if the Nagios system receives the trap.
Try sending this OID to see if the Nagios system receives the trap.
Code: Select all
.1.3.6.1.4.1.31440.2.2.1.1.4
Be sure to check out our Knowledgebase for helpful articles and solutions!
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Need some help with an Snmp Entry.
Your screenshot shows SNMPv1 traps.
Try sending v2c traps, it's a little less complicated.
Try sending v2c traps, it's a little less complicated.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Need some help with an Snmp Entry.
Thanks Guys
I'll try
regards john
I'll try
regards john
Nagios Core 3.5.1
Checkmk 1.2.4p5
Checkmk 1.2.4p5
Re: Need some help with an Snmp Entry.
Sounds good, let us know if you need any further assistance.skyerjoe wrote:Thanks Guys
I'll try
regards john
Former Nagios Employee
Re: Need some help with an Snmp Entry.
Hello again
I tried to reproduce an trap from my ow-server but i cannot reach the finish line atm I'm struggle with the definition and the trap ...
I use the advise to explore the logs from snmptt:
Here is my log which our ow server produce:
Here is my trap which should reproduced the original one:
And this is the Trap Definition which i want to trigger
I'm not sure which i have to reproduce it
May trap sender looks like this:
regards skyerjoe
I tried to reproduce an trap from my ow-server but i cannot reach the finish line atm I'm struggle with the definition and the trap ...
I use the advise to explore the logs from snmptt:
Here is my log which our ow server produce:
Code: Select all
Wed Apr 6 14:24:53 2016: Unknown trap (.1.3.6.1.4.1.31440.0.6) received from xxx.16.9.117 at:
Value 0: xxx.16.9.117
Value 1: xxx.16.9.117
Value 2: 458:20:54:30.15
Value 3: .1.3.6.1.4.1.31440.0.6
Value 4: xxx.16.9.117
Value 5: public
Value 6: .1.3.6.1.4.1.31440
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.5=2
Code: Select all
Wed Apr 6 16:22:42 2016: Unknown trap (.1.3.6.1.4.1.31440.0.6) received from test-pc.local.1 at:
Value 0: test-pc.local.1
Value 1: xxx.16.9.138
Value 2: 0:0:00:00.00
Value 3: .1.3.6.1.4.1.31440.0.6
Value 4: xxx.16.9.138
Value 5:
Value 6:
Value 7:
Value 8:
Value 9:
Value 10:
Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.5=2
Code: Select all
EVENT wateralertOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" Testing
FORMAT Water Status $+1
EXEC /usr/local/nagios/libexec/submit_check_result ow-server "Water Alert level 2" 2 "Water status is critical"
#MATCH $+1:(31440.2.2.1.1.5:2)
MATCH $x:.1.3.6.1.4.1.31440.2.2.1.1.5:2
SDESC
ow-server alert
EDESC
May trap sender looks like this:
regards skyerjoe
Nagios Core 3.5.1
Checkmk 1.2.4p5
Checkmk 1.2.4p5
Re: Need some help with an Snmp Entry.
When you edited the snmptt.conf file, did you restart the snmptt daemon?
You need to do that every time you do any changes to that file.
How about you start out simple and comment out the MATCH for that OID and see if the system receives the trap.
You need to do that every time you do any changes to that file.
How about you start out simple and comment out the MATCH for that OID and see if the system receives the trap.
Be sure to check out our Knowledgebase for helpful articles and solutions!