Issues with simple trigger conditions

[JoePhillips]

Hi All,

Wondering whether somebody can help me... I have a SNMP check that returns a text value of "00 00 00 00" when it's status is OK. If any values change in "00 00 00 00" there is a problem and I would like a trigger to occur so I am notified.

I have configured the following problem condition where if the string value does not equal "00 00 00 00"

last(/Alcatel SNMP Virtual-Chassis by Joe Phillips/vcmissing2.slot)<>"00 00 00 00"

Along with the following recovery condition where the string value does equal "00 00 00 00"

last(/Alcatel SNMP Virtual-Chassis by Joe Phillips/vcmissing2.slot)="00 00 00 00"

However the a problem is being triggered constantly even though its reporting back with a string value of "00 00 00 00". Any help would be greatly appreciated!

[cyber]

last()<>"string"...
If we look on trigger expressions...

<>	Not equal. The operator is defined as: A<>B ⇔ (A<B-0.000001) or (A>B+0.000001)

Doesn't fit ,right?

use

find(/host/item,,"like","00 00 00 00"))<>1

and you do not need recovery expression there, as it is exatly same as main expression being false, which anyway turns your trigger to OK already...

[JoePhillips]

Hi Cyber,

Thanks for taking the time to reply. I’ll give your suggestion a try tomorrow

[JoePhillips]

Hi Cyber,

Just to update you, your suggestion worked a treat (minus one bracket)! Thanks very much, really appreciated the help there.