<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Well my problem isn't that easy. I agree that Acking the Root problem should be simple and a single click away. However, (from a previous posting)... Well I would agree, however I have also posted a question in this list about Sounds. Nagios does see only one Host as being down, while 99 are Unreachable. The problem I'm trying to avoid is when the cgi.cfg has Host, Critical, and Warning sounds turned on, the Nagios webpages keep sending out the Critical Alarm, even though the Host that is Down has been Acked, and we don't get the HostDown Alarm anymore, we only get the Critical Alarm. The real interesting part is that we only get One Notifiication email, showing the Host being down, nothing for the Critical Services, which is the way we want it configured. If the Hosts are Down, why would you still want to know that the Services are critical? Here's from my first posting. 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? Tedman Eng wrote: <blockquote cite="mid37ED92F9890FAF4BB947613C66FF8B1A08BB2C6C@dw-mail.dataway.com" type="cite"> <pre wrap="">You could add a parent to those hosts in order to group them. Then the 100 powered-off hosts would be marked unreachable and you'd only have to acknowledge that one parent host. The 'parent' host does not have to be the real network-parent. Just some reliable host that will help indicate the power status of the building. (an access point, one of the switches, etc.) We use the same concept to isolate large groups of devices that we need to 'toggle off' for one reason or another. </pre> <blockquote type="cite"> <pre wrap="">-----Original Message----- From: Scott Smith [<a class="moz-txt-link-freetext" href="mailto:ssmith@siu.edu">mailto:ssmith@siu.edu</a>] Sent: Thursday, December 08, 2005 12:00 PM To: <a class="moz-txt-link-abbreviated" href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a> Subject: [Nagios-users] Acknowledge Scripts I was wondering if anyone would have a script they wrote, or copied from somewhere, to acknowledge multiple Devices/Hosts that are down at one time instead of having to goto each individual Host and Ack. I.e., one building is down without power, and we have 100 Switches/Routers in this building. Instead of our NOC Acking 100 times, it would be nice if they could Ack the Root (Parent) problem and it would Automatically Ack all the Children. Any ideas on this one? If I need to post this in a different List, please advise which one and I'll post it there. Thanks in advance. -- Scott Smith Network Engineering Services Southern Illinois University Carbondale <a class="moz-txt-link-abbreviated" href="mailto:ssmith@siu.edu">ssmith@siu.edu</a> ------------------------------------------------------- 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! <a class="moz-txt-link-freetext" href="http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click">http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click</a> _______________________________________________ Nagios-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </pre> </blockquote> <pre wrap=""> </pre> </blockquote> <div class="moz-signature">-- Scott Smith Network Engineering Services Southern Illinois University Carbondale <a class="moz-txt-link-abbreviated" href="mailto:ssmith@siu.edu">ssmith@siu.edu</a> </div> </body> </html> ------------------------------------------------------- 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@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