I currently have two hosts where one acts as a backup for the other and so
long as the first is up the second will always be down.

What I am looking to do is control the status of the second based on the
first and am wondering if this kind of configuration is possible?

I tried using a host dependency and host definitions as follows but no luck
so far

define hostdependency{
        dependent_host_name             sydisdn
        host_name                       sydgw
        execution_failure_criteria      o
        }

define host{
        use                     router
        host_name               sydgw
        alias                   sydgw
        address                 *.*.*.*
        hostgroups              router,sydney
}

define host{
        use                     router
        host_name               sydisdn
        alias                   sydISDN
        active_checks_enabled   1
        passive_checks_enabled  0
        address                *.*.*.*
        hostgroups              isdn,sydney


I would like to be able to display the status of sydisdn as downtime when
sydgw is up and running normally. When the status of sydgw is anything else
sydisdn should be monitored to check its status.

Any help would be much appreciated.

Brad



-- 
Bradley Mclain
Systems Administrator Trainee
De Bortoli Wines Pty limited
De Bortoli Rd, BILBUL NSW  2680
e:  [EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to