Distributed Toplogy - check-host-live doubt - Please help needed!

[Arno Lehmann]

Hi.

I start to understand...

Artur D'Assumpção wrote:

  > My doubt is really simple. I've got a monitoring distributed/recursive
> topology like it i've already explained in a previous thread:
> 
> ---
> - root A (this will receive and web publish all the incoming passive 
> submits. NSCA)
> -- root B (this will receive, web publish his results and re-submit them 
> no root A. NSCA / OSCP)
> --- clientB:x (this is a standar client submiting to root B, OSCP with 
> send_nsca)
> -- root C (analogous to root B)
> --- client C:x (analogous to client B:x)
> ----
> 
> So the problem is, for example:
> 
> Since root A can't reach clientB:x, i'm dependent from root B to obsess 
> the passive checks submited by client B:x directly to root A. So far so 
> good, and I confirm this topology works in pefection. But i've got one 
> problem in root A, since the checks for client B:x are received 
> passively trough root B and this client is unreachable from root A's 
> network, I had to redefine the check_command to a "dummy OK" check that 
> enables the client's services to be checked, otherwise the host would 
> get stated has DOWN and service checks disabled. But what I really 
> needed and is exacly the problem I am having, is that root B, that 
> actually can reach and check actively (with check_command) the clientB:x 
> status, also notified root A for this status.


I think you need the passive hosts check feature from nagios version 2.

> If this is possible, root A, like the service checks, will be also 
> capable to determine the clientB:x status trough the root B submits.
> 
> My english is not very well, but I hope I was clear, please ask me to 
> try to explain better if it wasn't so clear.

I think it's becoming clear now.

> Hope anyone could lead me here please.
> 
> Tnks,
> 
> Artur D'Assumpção


Arno
> Marc Powell wrote:
> 
>>> -----Original Message-----
>>> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
>>> admin at lists.sourceforge.net] On Behalf Of Artur D'Assumpção
>>> Sent: Thursday, April 07, 2005 4:51 PM
>>> To: nagios-users at lists.sourceforge.net
>>> Subject: Re: [Nagios-users] Distributed Toplogy - check-host-live 
>>> doubt -
>>> Please help needed!
>>>
>>> I still can't solve this issue, can any one help me here please? I would
>>> be gratefull.
>>>
>>>
>>> Artur D'Assumpção wrote:
>>>
>>>   
>>>
>>>> I'm sorry to insist in this subject, but i'm really running on a
>>>> schedulle here. Can any one help me out?
>>>>
>>>> Artur D'Assumpção
>>>>
>>>> Artur D'Assumpção wrote:
>>>>
>>>>     
>>>>
>>>>> Hi ppl,
>>>>>
>>>>> Here I am again with a distributed topology doubt. In my present
>>>>> configuration I have Parents that depends from other lower Parents to
>>>>> detected some unreachable client status. In this topology I had to
>>>>> create a check-unreachable-host-live command that returns a dummy OK
>>>>> status, so the top parent could process the host's passive checks. So
>>>>> far so good, but I have one litle problem, I wish that the beneath
>>>>> parent, that is actually able to reach this specific client, could
>>>>> also send the reachability status of this host to its direct parent.
>>>>> If this check was a service, then there was no problem, but since
>>>>> this is a host specific directive(check_command), how can I acomplish
>>>>> this, or get around it?
>>>>>       
>>
>>
>> Resending the same thing over and over again isn't going to help. 
>> Perhaps no one has done what you are trying, you haven't supplied 
>> enough information to answer or, more likely, what you're trying to 
>> accomplish isn't clear at all. I for one have no idea what your 
>> desired end-result is from the information above or how it differs 
>> from the documented parenting/network reachability logic that is 
>> already incorporated into Nagios.
>>
>> Perhaps you should read 
>> http://nagios.sourceforge.net/docs/1_0/networkreachability.html and 
>> http://nagios.sourceforge.net/docs/1_0/networkoutages.html and then 
>> tell us how what you want is different and/or state your problem more 
>> simply, using examples.
>>
>> -- 
>> Marc
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_ide95&alloc_id396&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
>>  
>>
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
> 

-- 
IT-Service Lehmann                    al at its-lehmann.de
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&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