Critical Audible Alarms with Unreachable Hosts

[Scott Smith]

I have been using Nagios for a while (several years, and even when it 
was NetSaint).  Just recently we had our NOC switchover from HP OpenView 
to Nagios.  In doing so we updated all the Hosts from our network into 
the Nagios config, some 990 plus Hosts, and now over 1000 services.

Here is my issue.  When we have a building go down, say 5 Switches 
(Hosts), and we have the Parents Relationship setup properly we see 1 
Host Down, and 4 Hosts Unreachable.  We only get one Email Notification 
about the single Host being down, which is what we want.  However, the 
NOC has recently asked use to enable the Sound for Nagios, which we did 
with the cgi.cfg file.  The problem is that when the NOC Acknowledges 
the root problem, and services from the 1 Host that is down, we keep 
getting the Critical.wav alert on our webpages.  They have to goto ALL 
the Unreachable devices services, and Acknowledge them as well. 

In this example isn't to bad, however some of our buildings have over 
100 Hosts, and if the main router goes down for that building our NOC 
would have a nightmare trying to Ack each Host.  Ultimately I would 
think that they should just Ack the Root problem, and then the 
Unreachable Children (so to speak) would not need Acking.  The more 
interesting part is that Nagios seems to understand this by only sending 
one Email, but the webpages don't.

Any ideas on this one?
-- 
Scott Smith
Network Engineering Services
Southern Illinois University Carbondale
ssmith at siu.edu


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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