> On Monday October 20 2008 11:38:04 am Paul Weaver wrote: > > How about a new command called "fakecheck", and apply to a > > "dumbswitch" host with a 127.0.0.1 address. It would take a list of > > machines, and check them all. If any of them are up, then the > > fakecheck would return OK, otherwise it would return an error state. > Just for understanding, you would check if the hosts which > are connected to > this dumbswitch are up? > > But they are tested anyhow..
If you have 10 devices on the unmanaged switch, and all 10 are off, it's likely the switch is broken -- so set the switch to off, and the devices to unreachable If 9 are off, and one is on, the switch *can't* be broken You could check the current state of each device (check_cluster), but 1) All devices go off, check_cluster goes bad 2) All devices then go unreachable 3) Check_cluster stays bad for ever (won't go good until a device goes good, which won't happen if they are unreachable and aren't checked), or it goes unreachable (inheriting the state of the devices), or goes good (if it treats unreachable as "OK"). None of those is the correct action. Pings are cheap. ------------------------------------------------------------------------- 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
