The Notifications are "HOST DOWN", not unreachable. Here is an example of the configuration....<br><br>As you can see, UNREACHABLE Notifications aren't send<br><br>------------------------------------------------------------ CFG -----------------------------------------------------------------
<br>define host{<br>        name                            generic-host<br>        notifications_enabled           1<br>    active_checks_enabled            1<br>        event_handler_enabled           1<br>    flap_detection_enabled          0
<br>        process_perf_data               1<br>        retain_status_information       1<br>        retain_nonstatus_information    1<br>        check_command               check-host-alive<br>       checks_enabled             1
<br>        max_check_attempts                 1 <br>        notification_interval       0<br>        notification_period         24x7<br>        notification_options         d<br>       contact_groups            cg-ServiceDesk
<br>    check_period            24x7<br>        register                        0               ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL<br>}<br><br><br><br>define host{<br>        name                            generic-host-wans-passive
<br>        notifications_enabled           1<br>        active_checks_enabled           0<br>      passive_checks_enabled            1<br>        event_handler_enabled           1<br>        flap_detection_enabled          0
<br>        check_freshness                 1<br>        freshness_threshold             86400<br>        process_perf_data               1<br>        retain_status_information       1<br>        retain_nonstatus_information    1
<br>        check_command                   check-host-alive<br>        checks_enabled                  1<br>        max_check_attempts              1<br>        notification_interval           0<br>        notification_period             24x7
<br>        notification_options            d<br>        contact_groups                  cg-ServiceDesk<br>        register                        0                   ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL<br>}<br>
<br>define host{<br>        use                     generic-host<br>        host_name               PARENT<br>        address                 <a href="http://192.168.192.168">192.168.192.168</a><br>        }<br><br>define host{
<br>        use                     generic-host<br>        host_name           RT1<br>        address                <a href="http://192.168.192.167">192.168.192.167</a><br>        parents                PARENT<br>        }
<br><br>define host{<br>
        use                     generic-host<br>
        host_name           RT2<br>
        address                <a href="http://192.168.192.166">192.168.192.166</a><br>
        parents                PARENT<br>
        }<br><br>define host{<br>

        use                     generic-host-wans-passive<br>

        host_name           RT3<br>

        address                <a href="http://192.168.192.165">192.168.192.165</a><br>

        parents                RT1<br>

        }<br>------------------------------------------------------------ CFG
-----------------------------------------------------------------<br><br>Thx,<br>Lívio Zanol Puppim<br><br><br><div><span class="gmail_quote">2007/10/5, Marc Powell <<a href="mailto:marc@ena.com">marc@ena.com</a>>:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>> -----Original Message-----<br>> From: <a href="mailto:nagios-users-bounces@lists.sourceforge.net">
nagios-users-bounces@lists.sourceforge.net</a> [mailto:<a href="mailto:nagios-users-">nagios-users-</a><br>> <a href="mailto:bounces@lists.sourceforge.net">bounces@lists.sourceforge.net</a>] On Behalf Of Livio Zanol Puppim
<br>> Sent: Friday, October 05, 2007 9:45 AM<br>> To: <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>> Subject: [Nagios-users] NAGIOS Notifications Problems<br>><br>
> Hello,<br>><br>> I'm looking for help in notifications. If anyone could answer this i'd<br>be<br>> pleased.<br>><br>> My Nagios has some hosts configured with parents settings, so when a<br>host
<br>> is down, Nagios checks out his parent to see if it is down too.<br>> OK, I think this is working. But When the notifications comes into<br>place,<br>> I receive notifications for parents and ALSO for his children like
<br>this:<br>><br>> *PARENT*     CRITICAL - Plugin Timed out after 3 seconds<br>> *RT1*            CRITICAL - Plugin Timed out after 3 seconds<br>> *RT2*            CRITICAL - Plugin Timed out after 3 seconds<br>
> *RT3*            CRITICAL - Plugin Timed out after 3 seconds<br>><br><br>Are the RT* notifications DOWN or UNREACHABLE notifications? There is a<br>difference.<br><br>> I want to receive a notification only for the parent host. How can
<br>this be<br>> done?<br>><br>> Is there something wrong?<br><br>Sounds like it. Post a complete host definition for RT1 and PARENT so we<br>can see if there is.<br><br>--<br>Marc<br><br>-------------------------------------------------------------------------
<br>This SF.net email is sponsored by: Splunk Inc.<br>Still grepping through log files to find problems?  Stop.<br>Now Search log events and configuration files using AJAX and a browser.<br>Download your FREE copy of Splunk now >> 
<a href="http://get.splunk.com/">http://get.splunk.com/</a><br>_______________________________________________<br>Nagios-users mailing list<br><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net
</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
<br>::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br>