We have about 150 client sites that we would like to be able to monitor
via SNMP. The client sites have multiple WAN interfaces on a router
(2-6) for bandwidth and redundancy. The SNMP interface of the device
allows checking of statistics on each interface (about 12-18 items per
interface).
* What we would like to do is setup each site as its own host and
then monitor:
* Ping for each interface (already working in nagios)
* Each interfaces set of snmp information (working but cumbersome)
* Mrtg -- (that will come next)
Currently, I have defined each snmp service separately as a template
(register 0) and then as I define each host, I have to copy/paste each
group of snmp checks for as many interfaces as there are to be monitored.
My question is -- is there a way to enumerate the interfaces either
through SNMP (there is an OID that tells how many interfaces are defined
on the router) or through a script? (like snmpwalk?) Ultimately, it
would be easier if nagios could determine the number of defined
interfaces and enumerate the OIDs that we have defined and want to
monitor. If not -- if there was a way to define interfaces in groups
that allowed the interfaces to be quickly defined for each host.
I have tried the nagios documentation on service groups/host groups/etc
but it is still cumbersome. It also doesn't let me see each host and
its associated interfaces as a single group unless I define each/every
one for that host.
Anyone run into this and/or can lend some friendly advice -- It would
be greatly appreciated.
*Will Howard*
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
