<!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 5.50.4134.100" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I have setup Nagios to monitor around 135 hosts
(only checking to see if host is up). My network topology is a MAN using
Gig Ethernet from the site where the Nagios machine is and a mix of
10/100/1000Mb/s ethernet to each site on the MAN. I am monitoring the
router connecting each site as well as 3-4 servers at each site.
One site that is connected via 100Mb/s will show the router down and/or
some of the servers down; sometimes all, sometimes different ones. Yet,
when one of these machines is shown as down, I am able to ping it from the
nagios machine and other machines. I can restart nagios and it will show
these machines as up for a while, then return to a down state. I'm also
monitoring the performance of these using MRTG which currently is
reporting one machine at this site as being up for 16 days while Nagios
reports it has been down for 3 days. I have included
the service definition below; the hosts definitions are identical to the
other hosts which are working fine. The router at this site is in a
hostgroup with all the other routers; the servers are in a hostgroup unique to
this site. </FONT></DIV>
<DIV><FONT face=Arial size=2> Also should note that this particular site
did actually go down once after I restarted nagios; nagios reported it was up,
when the site was down. </FONT></DIV>
<DIV><FONT face=Arial size=2> Any help in troubleshooting this is greatly
appreciated. </FONT></DIV>
<DIV><FONT face=Arial size=2> </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>define
service{<BR>
use generic-service ; Name of service template to
use</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>
host_name
*<BR>
service_description
PING<BR>
is_volatile
0<BR>
check_period
24x7<BR>
max_check_attempts
3<BR>
normal_check_interval
5<BR>
retry_check_interval
1<BR>
contact_groups
router-admins<BR>
notification_interval
120<BR>
notification_period
24x7<BR>
notification_options
c,r<BR>
check_command
check_ping!100.0,20%!500.0,60%<BR>
}</FONT></DIV></BODY></HTML>