Monitoring multi-homed boxen

[Karl DeBisschop]

On Wed, 2003-09-17 at 11:43, Damian Gerow wrote:
> Thus spake Tedman Eng (teng at dataway.com) [16/09/03 22:53]:
> > It sort of depends on how the services are set up on the multi-homed host.
> > 
> > Do the different interfaces have services specific to each interface?  (For
> > example, DHCP in one side, DNS on the other side).  If so I'd monitor each
> > interface as a separate host.
> > 
> > Do you have to go through one interface to get to the other? (For example, a
> > box set up as a gateway, which Nagios is allowed to route through).  If so,
> > I'd set up the near interface as parent, and the far side interface as a
> > child.  This would mark the far side interface 'unreachable' if the near
> > interface goes down.
> 
> For the most part, I'm talking about routers here.  Some of them are
> internal to our network, some of them have an interface on an external
> network.  The services they run will (for the most part) be the same on
> every interface -- a remote connection daemon (telnet, ssh), and a routing
> daemon.
> 
> So it /is/ important to monitor every daemon on every interface (we need to
> know if peering with Company X goes down, but the rest of the box is up).
> 
> I suppose to clarify, what I was trying to avoid is, with ten routers, three
> interfaces per router, that's thirty host objects.  There's no way to
> specify multiple IP addresses in a host object, is there?  Because
> technically they /are/ all the same machine; every interface runs the same
> service.  The only thing that's changed is the IP address of the interface.
> Having multiple IP's per host object would really un-clutter the visual
> display, but would probably be a PITA to get working properly, especially
> with dependancies.

define host{
        name                          generic-host
        notifications_enabled         1
        event_handler_enabled         1
        flap_detection_enabled        1
        process_perf_data             1
        retain_status_information     1
        retain_nonstatus_information  1
        check_command                 check-host-alive
        max_check_attempts            10
        notification_interval         120
        notification_period           24x7
        notification_options          d,r
        register                      0
        }


define host{
        use        generic-host
        host_name  lin04
        alias      lin04
        address    10.160.3.169,165.193.123.156,165.193.123.157
        }
 
define command{
        command_name    check-host-alive
        command_line    /usr/lib/nagios/plugins/check_ping -H
$HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 1
        }

But you have to use the plugins from CVS HEAD.

--
Karl



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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