On 5/2/07, dschrock <[EMAIL PROTECTED]> wrote:
On both of my installs, the configuration file examples, in $ZENOSSHOME/etc/,
are identical to the real .conf files, which, for the most part, are empty.
Are there real examples anywhere that show all of the possible options that can
be included in the conf files?
Based on the conf file names, it appears that some of the minor issues i'm
having could possibly be resolved with the correct conf option.
For instance-
zenmib.conf - is there an option to load the mibs from net-snmp so I don't have
to create standard trap events myself? Right now, many traps show up as
/Unknown and I really don't want to create an event for every possible trap we
may receive... i'd rather not recreate the wheel when the traps are already
defined in the mib file.
zenping.conf - can this be setup similar to zenperfsnmp.conf to move the ping
process to the remote monitor instead of the master? Running the ping from the
Chicago datacenter to a Phoenix customer is not as useful as running the ping
from the Phoenix datacenter to a Phoenix customer. There is too much in
between to skew the result and give a false failure- carrier issues, vpn
issues, etc.
A list of options for each file would really help out, as it could reveal
functionality that isn't well documented elsewhere
Daniel,
It's easy to see all of the options you can put in the conf files. If
you wanted to see what options zenping.conf supported, you'd run
"zenping run --help" All of the long-form options can be specified in
the conf file.
With zenmib you should copy all the MIBs (and dependencies) into
$ZENHOME/share/mibs/site then run "zenmib run" It will try to import
all mibs in that site directory.
You can setup zenping to run on a remote monitor. You'll have to setup
a remote status monitor instead of remote performance monitor since
that's what it is. Due to this you'll also need to run zenstatus on
the remote monitor too, since it is the other part of a full status
monitor. The most important config option to set in zenping.conf for
this setup is "configpath
Monitors/StatusMonitors/nameOfYourStatusMonitor" so that it knows
which devices it is responsible for.
Hope this answers your questions.
--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
