Ach. forgot to CC the list. My apologies
-------- Original Message --------
From: - Tue Dec 11 15:33:11 2007
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 11 Dec 2007 15:32:52 +0100
From: Andreas Ericsson <[EMAIL PROTECTED]>
To: Andrei-Florian Staicu <[EMAIL PROTECTED]>
Subject: Re: [Nagios-users] Define multiple serves per host(s)
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Andrei-Florian Staicu wrote:
> Andreas Ericsson wrote:
>> Make a hostgroup of all your switches and define your service like this:
>>
>> define service{
>> service_description yada yada
>> hostgroup_name all-the-routers
>> check_command more yada yada
>> yada and more yada
>> }
>>
> Yes, but each switch has 24 ports. Since the check_command is different
> for each port (different oid's), shouldn't there be a service for each
> port? Or can I avoid this?
>
You can't avoid that then. What you're asking now doesn't match what you
wanted at first though:
> The actual case here is to monitor the link status on all ports on
> several identical switches.
> I hope to bypass creating a huge config file from the command prompt.
To monitor the link status of ALL ports wouldn't be terribly difficult.
Just make a script to check all ports on one switch and use that in
your check command definition.
--
Andreas Ericsson [EMAIL PROTECTED]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
--
Andreas Ericsson [EMAIL PROTECTED]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users@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
