Multiple interfaces

[PGuth at corp.terralycos.com]

I guess it depends on what you're trying to do.  If you just want to make 
sure you're hitting the interface that's closest to the nagios server, 
then why not simply use *that* interface as the one defined in the host 
object?  And ignore the rest?

If you actually need to monitor each interface (or services on each 
interface) separately I don't see how to avoid the work of defining 
multiple "things" even if you could find a way to do it without multiple 
host definitions.  You can make the multiple definitions easier with 
hostgroups/templating etc so that you only define a service once, assign a 
hostgroup to it, and put all your hosts (and their interfaces) in that 
hostgroup.





Phil Dibowitz <phil at usc.edu>
07/30/2004 03:35 PM
 
        To:     PGuth at corp.terralycos.com
        cc:     nagios-users at lists.sourceforge.net
        Subject:        Re: [Nagios-users] Multiple interfaces


I'm brining this back on-list, because I think that the reasoning is 
important
to my question... hope you don't mind.

On Fri, Jul 30, 2004 at 03:22:47PM -0700, PGuth at corp.terralycos.com wrote:
> We just define multiple hosts, one for each interface.  Generally they 
> have the same hostname with a letter appended to signify what network, 
so 
> if your host is named host22 you could define host22pub and host22priv, 
> for instance. 

See. But we have lik 8 interfaces that are all reachable from any one 
place,
but depending on where you are on the network one is closer to you --
different subnets. And hosta - hostg is kind of annoying. Especially 
because
someones we'll name one interface seperately so we get:

almaakA
almaakB
almaakC
almaakD
almaakE
almaak-qfe0A
almaak-qfe0B
almaak-eri0A
almaak-eri0B

And that's kinda hard to manage --- have to have service entires for all 
of
the, etc., etc...


-- 
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427


-------------- next part --------------
A non-text attachment was scrubbed...
Name: attyd4il.dat
Type: application/octet-stream
Size: 196 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040730/232df288/attachment.obj>