Parent and Child Relationships

[Jim McNamara]

I'm having an issue figuring out the parents remote routers that are
connected over radio links to my main router. In one of my installations
I have remote hosts (D) behind a remote router (C)  that is connected to
my "main" network via two radio connections (B1,B2). The "main" router
(A) is needed to communicate with all of the remote hosts (C,D) because
of the necessary routing and natting. 

I've used the two radios (B1,B2) plugged into the remote routers (C) as
the parents for the router (C), and discovered that with two parents,
nagios uses an OR style to determine the child host state. In this case,
if either B1 or B2 is up, the child C should be up. This is accurate to
a point in my case, but for the complete picture I need to introduce
something like an AND to this. Specifically, to reach host C, A must be
up, and either B1 or B2.  

I had though to make A the parent of B1 and B2, but it simply isn't. B1
and B2 can be reached with A down. 

Is there a way to specify parent/child relationships where there are
three parents, but one specific parent must be up and at least one of
the other two?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120425/2e27f330/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null