Double monitoring.

[Steve Shipway]

> I'm admin of network with nagios, the network has like 30 servers, and
im
> trying to do a double monitoring.ie:

Sounds like what you want is either High Availaibility or Standy Nagios.

We use both.

For our 'live' Nagios, we have two servers running Linux-HA which are
both connected to the same external SCSI disk unit via an Adaptec
ServeRAID card.  Linux-HA takes care of failing over the control of the
disk unit, and the virtual IP, apache, and Nagios services.  This way,
we can shut down server A and server B will take over everything within
a few seconds.  So, we get 100% uptime, provided our main datacentre is
online.

However, for DR, we have another Nagios server at a remote site.  This
server has a mirror of the configuration files but Nagios is normally
down.  A regular cron job attempts to check Nagios on the live server
(via NRPE and check_nagios) and if Nagios is down on the live server,
then the DR Nagios is started up.  We could do this alternatively by
having Nagios always running, but with service checks and notifications
disabled.  Then, when the check fails, use the command pipe to send in
the enable commands (and disable commands when it comes back).  In this
case, you could even use a custom host check and event handler to take
care of it all internally to Nagios, although this would prevent you
from simply using a straight copy of the live configuration files.

I think there is some documentation on this at the Nagios web site.

Steve

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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