You are here

Manage trap rules

5 posts / 0 new
Last post
kappakappa
kappakappa's picture
Manage trap rules

Hi all,

i've a Opsview 3.11.3 Community installed on a Solaris 10. I've wrote some rules for snmp trap, like this:

detach check

DETACH_server_inst_0_critical "${V6}" eq "2" && "${V7}" eq "critical" && "${V8}" =~ /-i\s+0/ CRITICAL DETACH_server_inst_0_clear "${V6}" eq "2" && "${V7}" eq "clear" && "${V8}" =~ /-i\s+0/ || "${V6}" eq "2" && "${V7}" eq "clear" && "${V8}" =~ /instance:\s+0/ OK

 

loss of frame check

LOF_server_inst_0_int_0_critical "${V6}" eq "8" && "${V7}" eq "warning" && "${V8}" =~ /instance:\s+0/ && "${V8}" =~ /interface:\s+0/ CRITICAL LOF_server_inst_0_int_0_clear "${V6}" eq "8" && "${V7}" eq "clear" && "${V8}" =~ /instance:\s+0/ && "${V8}" =~ /interface:\s+0/ OK

 

loss of signal

LOS_server_inst_0_int_0_critical "${V6}" eq "7" && "${V7}" eq "warning" && "${V8}" =~ /instance:\s+0/ && "${V8}" =~ /interface:\s+0/ CRITICAL LOS_server_inst_0_int_0_clear "${V6}" eq "7" && "${V7}" eq "clear" && "${V8}" =~ /instance:\s+0/ && "${V8}" =~ /interface:\s+0/ OK

The traps are received from Opsview and the alarm/clear are working correctly, but the trap are also inserted in the exceptions.

Below an example of trap that is working, but it is also in the exceptions:

192.168.1.192
192.168.1.192
DISMAN-EVENT-MIB::sysUpTimeInstance 1:0:03:04.78
SNMPv2-MIB::snmpTrapOID.0 MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjlAlarm
MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjAlarmIpAddr 192.168.1.192
MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjAlarmId 2
MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjAlarmSeverity clear
MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjAlarmDescr The plug-in for site server: 127.0.0.0, probe type: P12K IP-OC12 with instance: 0 does not work properly
MYTEST-MONITOR-TRAP-MIB::cpMonitorPrjAlarmOccuredTime 159:22:38:07.01

In the exceptions the reason is "At least 1 servicecheck failed to match a rule 1 2", but the linked rules have no sense. How can i fix this?

Thanks.

 

smarsh
smarsh's picture
Re: Manage trap rules

Hello,

Im afraid that I cant really advise - as this is a VERY old version, of an now end-of-life product, on Solaris which is also EOL'd by Opsview  - so it doesnt look good i'm afraid. Best of luck however!

Sam

kappakappa
kappakappa's picture
Re: Manage trap rules

Hi,

thanks for your reply.

I've installed on Debian 6.0.7, Opsview 4.4.1 (Pro trial version) to test the behaviour, but i receive this error in the snmp trap exceptions:

 

192.168.1.198 Error No trapname 192.168.1.198
UDP: [192.168.1.198]:47216->[10.2.0.132]
iso.3.6.1.2.1.1.3.0 21:1:19:09.37
iso.3.6.1.6.3.1.1.4.1.0 iso.3.6.1.4.1.26855.666.2
iso.3.6.1.4.1.26855.666.1.1 192.168.1.198
iso.3.6.1.4.1.26855.666.1.2 9
iso.3.6.1.4.1.26855.666.1.3 3
iso.3.6.1.4.1.26855.666.1.5 "Site server: 127.0.0.0, probe type: P12K IP-OC12, instance: 0, interface: 3"
iso.3.6.1.4.1.26855.666.1.4 159:22:39:43.02

The trap (and MIB) are the same that i use with the old Opsview version. If the new version can solve the issue, i could use this version.

Can you help me?

 

Thanks.

 

 

smarsh
smarsh's picture
Re: Manage trap rules

I'd recommend following the guide here as a start - http://docs.opsview.com/doku.php?id=opsview4.4:snmptrapsetup - it sounds like you just need to setup and configure the traps now on the Opsview system.

Sam.

kappakappa
kappakappa's picture
Re: Manage trap rules

I've follow that guide, but it doesn't work. Have you some ideas?

Thanks.