First, the quickie background. We're in the process of setting up nagios to
monitor our network - not the hosts on it, but our collection of routers and
switches. This means that a few of the host based assumptions that nagios
makes kinda break, but the biggest one right now is the fact that a single host
can have multiple IPs associated with it.
Now the easiest way I can think of to monitor multiple IPs on a single host
while still keeping a single host definition is to define a service for each IP
beyond the primary management one. The problem this brings in is dependancies.
Any nodes downstream aren't dependant not only upon the router as a whole being
operational, but also its particular interface.
So what I would love to see is the ability to define the parent of a given host
to be not just another host, but a list of services on another host.
For example, take a router with two interfaces, ifA is closest to the nagios
box, and ifB is a seperate interface defined as a service. So it would look
something like
+--------+
nagios ------- ifA | router | ifB ------- other host
+--------+
So at first glance, router should be the parent of other host. However, if
ifB goes down but ifA stays up, then other host will be incorrectly flagged
as down rather than unreachable. If nagios could be told that the parent is
not just router, but service ifB on router, with a syntax like
parent router!ifB
then nagios could do The Right Thing.
I've identified at least some of the code points that would have to be
modified (in the template config stuff only), and am willing to take a crack
at it if no one else will.
So would such a feature be considered for inclusion?
--
Frank Sweetser fs at wpi.edu
WPI Network Engineer
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]