<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2716.2200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi List,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Well, after settingup Nagios... (Works a
treat by the way!!!) I have found a small issue which (knowing my luck has been
covered in the past) causes dependancies to fail given a particular
scenerio.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Here is the example</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Nagios proposes that it is the head of the network
(fine), now to get any further around the network nagios links into a switch
which in turns connects into a core router. This seems logical at first except
for this little problem. Suppose you have other hosts on the switch and they are
all talking on different VLans which are defined by this so called core router..
if the core router dies then the remainder of all of my network dies.. the way
to get around this seems to be to assign the parent of the core router directly
to the nagios server which works, although upon the switch then dying would
cause that instance to fail..</FONT></DIV>
<DIV><FONT face=Arial size=2>Does anybody see the problem here or is it just me
and if they do, is there a solution to this little problem?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Hoping that I am not waffling....</FONT></DIV>
<DIV><FONT face=Arial size=2>Scott</FONT></DIV></BODY></HTML>