hysteresis/nodata problem snmp

[lalo]

hi folks, i have this trigger

({TRIGGER.VALUE}=0 | {TRIGGER.VALUE}=1) & {acc55:P_41.avg(#4)}=2


for operstatus but this trigger change to UNKNOW-OK-PROBLEM`s cycle, but this port ALWAYS is down (2).

I have large periods with not data. how i stop hysteresis?

[Heilig]

What you have described is not a hysteresis (you can see example here).
Why you do not use expression like "{acc55:P_41.avg(#4)}=2"?
Please describe the conditions under which the trigger should fire.

[lalo]

with this trigger

{acc55:P_41.avg(#4)}=2 & {acc55:P_41.nodata(1200)}=0

obtain

23 May 2013 09:44:04	P_41	PROBLEM	Warning	58m 41s	No	
23 May 2013 09:39:42	P_41	UNKNOWN	Warning	4m	No	
23 May 2013 09:36:42	P_41	UNKNOWN	Warning	2m	No	
23 May 2013 06:44:02	P_41	PROBLEM	Warning	2h 59m 40s	No	
23 May 2013 06:42:00	P_41	UNKNOWN	Warning	1m 42s	No	
23 May 2013 06:01:02	P_41	PROBLEM	Warning	42m 40s	No

with this trigger

({TRIGGER.VALUE}=0 | {TRIGGER.VALUE}=1) & {acc55:P_41.avg(#4)}=2 & {acc55:P_41.nodata(1200)}=0

obtain

23 May 2013 09:43:42	P_41	OK	                Warning	22s	No	
23 May 2013 09:39:42	P_41	UNKNOWN	Warning	4m	No	
23 May 2013 06:44:02	P_41	PROBLEM	Warning	2h 59m 40s	No	
23 May 2013 06:43:42	P_41	OK	                Warning	20s	No	
23 May 2013 06:42:00	P_41	UNKNOWN	Warning	1m 42s	No	
23 May 2013 06:01:02	P_41	PROBLEM	Warning	42m 40s	No	
23 May 2013 06:00:47	P_41	OK	                Warning	15s	No

this link ALWAYS is down (operstatus = 2) but I see event = UNKNOW with value = 0 in db, this is weird

SELECT t.value 
FROM triggers t, functions f, items i 
WHERE t.triggerid = $triggerid AND t.triggerid = f.triggerid AND f.itemid = i.itemid AND i.status = 0

item info: ifOperStatus["index","ifName","Gi1/41"]


thax for the reply

[Heilig]

Try this expression:
{acc55:P_41.avg(#4)}=2|{acc55:P_41.nodata(1200)}=1

But in this situation, it would be more appropriate to use a trigger:
{acc55:P_41.avg(#4)}=2
and create additional trigger "SNMP agent is Down" (by checking the availability of port 161).
In this case, you immediately clear with what the problem is, with the interface or with the snmp agent on the device.