Design question

[Michael Weiner]

On Thu, Jul 31, 2008 at 9:50 AM, Sean McAfee
<smcafee at collaborativefusion.com> wrote:
>
> Michael Weiner wrote:
> > Just a general question to the nagios user audience out there. I have
> > a situation that dictates I run two nagios instances due to the manner
> > in which our systems are provided power. We have no true data center,
> > and as such the servers being monitored by nagios are somewhat
> > distributed throughout the campus. My design question comes from a
> > recent major power outage that not only affected a slew of servers
> > that nagios was monitoring, but nagios itself. So my thought was to
> > provide a secondary, backup, nagios server somewhere off the power
> > grid – but the issue is that I don't want duplicate notifications. I
> > would like it setup such that the second device only monitors, and
> > will only send out alerts/notifications if and only if the primary
> > nagios server is down. Has anyone designed a setup similar to this? Is
> > this thinking not logical? Is there a better mouse trap? Is there any
> > design documentation?
> >
>
> Check out the documentation on Redundant and Failover Network Monitoring
> (http://nagios.sourceforge.net/docs/3_0/redundancy.html).
>
> Both examples will do what you want, but the underlying behavior is
> drastically different between the two so make sure you read carefully.
>
Thanks i am surprised i didnt see that already!!

Thanks again
Michael

-------------------------------------------------------------------------
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
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