snmp trigger

[cptnzod]

I have 2 items on a map and want to connect them together. One is a host and the other is a cisco firewall. In order to connect them I have to enter something for the link status indicator. There are no triggers now. So I guess I have to create triggers. I try the following expression for the firewall:

{champ:ifOperStatus.1.last(0)}=1

I get:

No such host (champ) or monitored parameter (ifOperStatus.1)

There is a host defined, and there is also an item for ifOperStatus.1 which is Active.

What do I need to enter for the expression? Am I on the right track?

[Alexei]

You must have:

1. Host 'champ' defined
2. Item with key 'ifOperStatus.1' defined for host 'champ'

[cptnzod]

They are both defined. If you dont believe me I am submitting pictures:

[Alexei]

Come on! I see 'Up Interface' instead of 'ifOperStatus.1' there!

[cptnzod]

Are you saying that the description is what is used here?
Okay I am gonna change it. But the description usually just means that!

[cptnzod]

Oh I got it. You meant the key! I had read in one post that the key was not important and just had to be unique. I changed the key to the snmp ifOperStatus.1 and all looks good now.
zabbix rocks.

[Alexei]

Yes, it is not important as you may call it "ifOperStatus.1", "key123", whetever, but still the key is user by triggers as an unique reference.

[szettervall]

Don't overlook the bug here...

I ran into the error similar to "No such host (champ) or monitored parameter (ifOperStatus.1)".

The key was not valid, but the host was, thus the message "No such host" shouldn't of been part of the the error message.

I verified this behavior which appears to be incorrect on 1.1.7

[Alexei]

The key was not valid, but the host was, thus the message "No such host" shouldn't of been part of the the error message.

The error reporting was improved in the latest 1.3.x code. Now we have two messages instead of one.