Dependencies not working properly

[petr5250]

Hello,
I'm trying to setup Zabbix to monitor our wireless network. The network elements are connected in series, so when something happens (power failure, failure of some element etc.), there are lot of warning emails/events generated.

To minimize number of events generated, I'm trying to configure dependency chain between elements using icmpping item/trigger, so when ICMP ping fails for 2 consequent tests, the trigger is fired and warning email is generated.

Example:
Zabbix server ----- A ----- B ----- C ----- D

Trigger "A - Host unreachable" depends on nothing,
Trigger "B - Host unreachable" depends on "A - Host unreachable",
Trigger "C - Host unreachable" depends on "B - Host unreachable",
Trigger "D - Host unreachable" depends on "C - Host unreachable".

My problem is, that when I have multiple hosts/triggers in dependency chain, some of the warning which should be masked by the predecessor in dependency chain are fired as well. In the example above it means, that there are warnings for unavailability of elements A and D when element A fails.
When I look on dashboard, I can see following:
System status - Some problem with element A
Host status - Some problems with elements A and D

My question is, how I can prevent such behaviour and get warning only for unavailability of element A?

There can be as much as 30 elements/triggers in dependency chain. I'm using Zabbix 1.8.2.

Petr

[Rudd]

The manual confirms your configuration up to the third level, but does not specify how many levels of nested dependencies are checked. When reading it I would also have expected this to work. Your findings seem to imply otherwise.

You could try adding a second dependency to D host to bridge the gap:

Trigger "A - Host unreachable" depends on nothing,
Trigger "B - Host unreachable" depends on "A - Host unreachable",
Trigger "C - Host unreachable" depends on "B - Host unreachable",
Trigger "D - Host unreachable" depends on "C - Host unreachable" or "A - Host unreachable".