I am faced with the potential of having to monitor different remote
networks with primariliy custom perl based snmp checks.
The tricky part of this is that different networks may have different
SNMP community names.
While I could create different service definitions for each different
1. N3 will/does support custom macros
2. I've seen (or heard) somewhere patch to add snmp community name to host
3. Many are doing it using hostgroup names and then have a map file
with community names loaded from it (and then also not seen when
you do ps on the box!!!)
On Thu, 21 Jun
-Original Message-
From: [EMAIL PROTECTED] [mailto:nagios-users-
[EMAIL PROTECTED] On Behalf Of James Whittington
Sent: Thursday, June 21, 2007 10:06 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] snmp community option in host definition?
I am faced
Off the top of my head, maybe the scripts could be edited so that you
could pass the community string to the script from the service
definition. For example, here's one that I use:
define service{
use chkifoperstatus-service
host_name
again for the helpful feedback.
James Whittington
-Original Message-
From: william(at)elan.net [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 21, 2007 12:11 PM
To: James Whittington
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] snmp community option in host
