On Wed, Jan 13, 2016 at 03:54:29PM +0000, Michael Friedrich wrote: > > Icinga 2 supports that, but I’m curious how your configuration looks in > detail. >
Extended the exporter today with the first step. Making a bridge domain depend
not only on the switch it runs on but also on the firewall beeing the upstream.
A simple host<>host dependency wont do it as the management of the switch is
not via this firewall so the switch wont be DOWN if this firewall fails.
The VLAN/Bridge Domain is not down when the firewall fails but i want
it to go down as its a useless bridge domain without upstream
object Host "firewall-host-A" {
import "generic-host"
address = "10.1.2.3"
}
object Host "switch-host-B" {
import "generic-host"
address = "172.16.1.2"
vars.snmprocommunity = "stripped"
}
object Service "BRIDGE VLAN336" {
import "generic-service"
host_name = "switch-host-B"
check_command = "bridge"
vars.bridgeid="VLAN336"
}
object Dependency
"cb7aee14377f35ccb58d46d9c30ac3c4-cb7aee14377f35ccb58d46d9c30c8aa8-BRIDGE-VLAN336"
{
parent_host_name = "firewall-host-A"
child_host_name = "switch-host-B"
child_service_name = "BRIDGE VLAN336"
}
It does not complain loading this configuration but it wont show up
and it wont work.
Flo
--
Florian Lohoff f...@zz.de
We need to self-defend - GnuPG/PGP enable your email today!
signature.asc
Description: Digital signature
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
