bind nagios server to a certain IP

Greg Cope greg.cope at e-dba.net
Mon Jul 17 17:40:02 CEST 2006


On Mon, 2006-07-17 at 17:18 +0200, Giles Coochey wrote:
> 
> >The host already has a default route.
> 
> Hi Greg,
> 
> What I mean to say is if you have one IP for cluster communications
> (without a default route) and another IP (your roaming IP for nagios
> which has the default route). You can implement this with a second
> interface card or subinterface and existing interface using dot1q
> encapsulation, if your switch infrastructure supports it, for which you
> do not assign a default route. You do this on both servers for the
> specific reason of checking that nagios is running on both hosts. It's
> simply a management interface.
> 
> If your passive system(s) detect that the active nagios host is
> experiencing problems (which you can do in a number of ways with both
> local and remote checks on the secondary IP address) it can take on the
> role of the active by reconfiguring the primary interface card with the
> IP of the failed device.
> 
> Thanks
> 
> Giles

Thanks Giles.

The host already runs linux heartbeat, and is in an active-passive ha
cluster running bind, ldap and dhcpd.  I wanted to add nagios to the
mix.  When setting this up it is usual to give each app a VIP address,
and configure that on the active host.

As I have configured nrpe clients to only allow checks from one IP - the
nrpe checks needs to come from that IP address.

Greg



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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





More information about the Users mailing list