Organization and host checks

[Andrew Tjang]

Hello all,
 
I have a couple of questions about how nagios functions.
 
How does nagios determine the host status? It seems that without any
user intervention, host status changes from pending to "Up". 
I have no is_alive checks set. So shouldn't the host status remain
pending until it receives information to the contrary? (I have passive
checks set up, and another script generates the host state information).

 
The only thing I can think of is that I've set all the host addresses to
127.0.0.1 (b/c i'm using passive checks, and not all hosts have a real
IP anyway), and somehow nagios is sensing that localhost is up, and thus
is setting the host status to Up. If this is the case, how do i disable
this behavior?
 
 
The second question I have is how to further organize hostgroups. I
would like to use one nagios installation to monitor 2 sets of machines
(each with their own list of hostgroups that might share the same
namespace). What is the easiest way to segregate these sets of machines
- perhaps on 2 hostgroup summary pages?
 
Thanks in advance for your help!
-Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20061109/13c725f3/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- 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