Need some help with an Snmp Entry.

[skyerjoe]

Hello tgriep

Yes the basic snmptt definition will triggered the submit checkresult correctly .. so no problem with the basic trap definition

Btw. I have to restart snmpd also

But the ent value definition is the problem.

Here is the output from trapd in syslog with the trap with the additional value :

Code: Select all

 2016-04-08 11:39:53 UDP: [xxx.16.9.138]:53831->[xxx.16.9.61]:162 [UDP: [xxx.16.9.138]:53831->[xxx.16.9.61]:162]:#012.1.3.6.1.2.1.1.3.0 = Timeticks: (0) 0:00:00.00#011.1.3.6.1.6.3.1.1.4.1.0 = OID: .1.3.6.1.4.1.31440.0.6#011.1.3.6.1.4.1.31440.2.2.1.1.5 = STRING: "2"

And the trap is no more showing in the snmptt unknown log i guess due to the main oid matching

best regards

[tgriep]

If the MATCH didn't match the data received exactly as it is specified, it will show up in the unknown log file.
Try editing the MATCH for that OID like below and see if it works for you.

Code: Select all

MATCH $1:.1.3.6.1.4.1.31440.2.2.1.1.5:2

or

Code: Select all

MATCH $1:.1.3.6.1.4.1.31440.2.2.1.1.5=2

[skyerjoe]

Hey Guys again

So i tried to find out the right Value but it won't be fit at all

I tried some several definitions:

MATCH $+1:.1.3.6.1.4.1.31440.2.2.1.1.5=1

MATCH $1:.1.3.6.1.4.1.31440.2.2.1.1.5=1

MATCH $1:.1.3.6.1.4.1.31440.2.2.1.1.5:1

MATCH $+1:.1.3.6.1.4.1.31440.2.2.1.1.5:1

I'm not really sure i this the right way for the adiitional value definition

See my defintions before and these ones are worked a long time till i had update to our ubuntu server.


Furthermore these are the Ent Values which comes from the ow-server to the smptt unkonwn log if i trigger our water altert components manually:

Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=2 water sensor 1
Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=1 water sensor 1


Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.5=2 water sensor 2
Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.5=1water sensor 2

regards john

[Box293]

Try:

Code: Select all

MATCH $1: 2

[skyerjoe]

Try:

MATCH $1: 2

Hello Box293

thanks for helping

This one seems to work a litte bit bettter some triggered snmp traps will be processed.

But this match is not exactly enough.

The OID .1.3.6.1.4.1.31440.2.2.1.1.4 with the Value '2'

will be processed also

any more suggestions so far ?

regards john

[ssax]

Try this:

Code: Select all

MATCH $+1:(31440.2.2.1.1.5:2)

Or this:

Code: Select all

MATCH $+1:(.1.3.6.1.4.1.31440.2.2.1.1.5:2)

[skyerjoe]

Hello Again

Again thanks for help

I Tired several traps Matches with these Defintion ( incl. all commented out matches which are listed below )

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:.1.3.6.1.4.1.31440.2.2.1.1.5:2
#MATCH $+1:(31440.2.2.1.1.5:2)
# works :MATCH $1: 2
#MATCH $+1:(31440.2.2.1.1.5:2)
MATCH $+1:(.1.3.6.1.4.1.31440.2.2.1.1.5:2)
SDESC
ow-server alert
EDESC

The only one which works is the

Code: Select all

MATCH $1: 2    

Variable but these one is as i mentioned already too common and too much matches fits for the matching condition .


regards john

[ssax]

Looks like this is what works:

Code: Select all

MATCH $+1:(enterprises.31440.2.2.1.1.5:2)

It's translating the OID.

[skyerjoe]

Hello ssax

Unfortunately these Match leads also to an unknown trap

im not really sure . may i have to translate some oids or sth like that to reach the finish line

regards john

[ssax]

Hmm, it works perfectly on mine.. please zip up and attach your /usr/share/snmp/mibs directory so I can lab this up.

Thank you