Service and host dependencies

Anthony Brock Anthony_Brock at ous.edu
Mon Jun 9 22:51:06 CEST 2003


I am having problems identifying how to define a specific dependency situation. Assuming I have 3 hosts (R1, R2, and R2) located behind a transparent firewall. The transparent firewall (FW1) serves as a bridge (using interface 'br0') from the internal network (N1) and the Internet.

However, the transparent firewall does NOT have logical connectivity to either network (it does not have an IP address or route to either network). On the other hand, the firewall DOES have a direct network connection to the management network (N2) that nagios is running on. How would I define this dependency?

Put simply, I believe I want to define a dependency for each host located behind the transparent FW1. This dependency need to be against the SERVICE of 'br0'. This may seem a little complicated, but it become important when you have more than one bridged interface on a transparent firewall (say, 4 or 5). It is quite possible for one of the bridged interfaces to go down while the other interfaces remain functional. This makes a host/host dependency too broad.

Ideas? I keep telling myself it is possible, but I've only found instructions for service/service and host/host dependencies, not for service/host dependencies. Or does someone have a better way to do this?

Tony


Anthony Brock
Unix Administrator/Network Engineer
Oregon University System
Chancellor's Office

(541) 737-9607
Anthony_Brock at ous.edu



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
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





More information about the Users mailing list