Dependencies for multiple locations

[thebigj]

I am new to zabbix (using the latest build 2.0.3) and trying to setup multiple locations with devices behind the routers.

Like:

Site1 : Router -> Switch1
--------------> Switch2
--------------> Switch3
Site2 : Router -> Switch1
--------------> Switch2
--------------> Switch3

I setup a template called routers and added all routers to it. Then a group called switches and added the switches to it.

Now I liked to setup a dependency for the switches to point back to the router template in the template switches, but I get an error that the switch is not in the router template.

Am I doing something wrong, or is there a better way for this setup? I would just like to not get an email for every device at a site when the router goes offline.

Thanks for your time.

[Mizukusai]

I don't think zabbix has this kind of features.

Nagios and other monitoring solutions do.
Cacti and metrology solutions don't.

[m_gularte]

Yep, it's possible:

http://www.zabbix.com/documentation/...s/dependencies

[Mizukusai]

ok, possible, yes.
Don't you think it's too complicted when you have lots of hosts ?
Ok, I shouldn't be saying that on a zabbix forum, moreover on THE zabbix forum but no matter what you think of Nagios, centreon or shinken, host relationships are easier to setup on them than on zabbix. Zabbix have a lot of qualities they will certainly never have, but this is definitely not its best suit.

Now you can bash me.

[heaje]

@Mizukusai - No bashing needed . Each system definitely has its strong suit and I definitely agree that dependencies are sometimes overly complex in Zabbix.

@thebigj - You're getting that error because the switches have not inherited the router template (as the error says). With a dependency between templates like you've done, the switch trigger dependencies get resolved down to the router template, NOT the hosts that inherit the router template. In essence, you've tried to set up a dependency to something that doesn't exist. When you set up a dependency on a host (whether through inheriting a template or on the host directly), it has to refer to a host in some way (not a template).

The method to do this that I know of (which would get old very fast) is to to set up the dependency on each switch individually to each host.

Another thought (not 100% sure this would work, but I don't see why it wouldn't) is to setup the dependencies on the switch template directly to the router hosts (and NOT the router template).

[thebigj]

Thanks everyone for looking over my question.

I found that I can manually go into each device and setup the dependency on the template trigger and it works correctly.

Now if I could figure out a way to make this change in a script or a mass import/update I would be happy. Does anyone else have an idea?

Thanks.