2 Nagios boxes running together in different locations

[Allan Clark]

On Wed, May 9, 2012 at 5:57 AM, Jeffrey Watts <jeffrey.w.watts at gmail.com>wrote:

> On Wednesday, May 9, 2012, C. Bensend wrote:
>>
>>
>> I've dealt with this situation before, and I've ended up
>> implementing two mostly standalone Nagios systems.  They each
>> check their own site, so if their external network goes away they
>> are still able to monitor and alert for the things they're
>> responsible for (you have to use out-of-band notifications of
>> course).  They also each check each other's *site*, ala the other
>> site's firewall, so the Nagios server at site A can alert and let
>> you know if site B goes away, but it *doesn't* try to alert you
>> for all of the hosts and services at site B.
>>
>
> This is exactly how I do things, except I have three sites.
>
> Jeffrey
>
>
I did the same for a company I was at; the configuration load was why i
moved things to LDAP-based config, so that adding LDAP objects for a server
defined the IP and a basic monitoring config, and a note of which Nagios
monitors it.

Allan
-- 
allanc at chickenandporn.com  "金鱼" http://linkedin.com/in/goldfish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120511/36b4ad00/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
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