Cisco SNMP (templatesport down trigger resetted with port still down

[Pigi_102]

Hello all.
Yesterday I had a very strange situation: One port of a cisco NX7000 switch went down ( as the object at the other end of the cable broke ) and correctly the trigger that inform me that the port went unexpectedly down triggered. Being this port part of a port channel, also the trigger of the port channel triggered.
So far so good, this is the expected behavior.
After 6 hours however without any intervention at all, I received the "RESOLVED" message for both the port and the portchannel, but it says :



As you can see, the Current State is down so I didn't expected for the alarm to resolv
Also the port-channel resolved:



No one has manually closed the problem, nor acknowledged them.

Any idea on what I can check ?


Thanks in advance.

Pigi_102

[markfree]

I don't think the event message shows the hole picture. If the port is still down but the event has been resolved, it seems the trigger expression has somehow became false. You should check the trigger as well as the item history.

[Pigi_102]

Hello, and thanks for your reply.
The trigger is this one:
"{$IFCONTROL:"Ethernet4/32"}=1 and last(/10.10.1.20/net.if.status[437907456])=2 and change(/10.10.1.20/net.if.status[437907456])"



I cannot see nothing strange here.
The item history don't look strange too:

It clearly shows that there has been a change and nothing more.
On the event, in the problem history, I don't see any aknowledge icon or whatever.

Any idea on what other I can look into ?
Any file, or database table, to investigated what's happening ?

Thanks again
Pigi_102

[markfree]

Note that the trigger uses only "and" operations.
It will only become true (create an event) if there is a change on the interface (oper) status going from something to down (2), also the control macro must be 1.
On your second picture, the partial graph, I can't see the actual values, so I assume the interface current status is not 2. It looks more like 3, which resolves the event.

[Pigi_102]

Unfortunally not, the link state is 2 ( down ).... that's why I was asking....