[Top] [All Lists]

Re: [nv-l] data collection/thresholds, config files, daemons

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] data collection/thresholds, config files, daemons
From: "Leslie Clark" <lclark@us.ibm.com>
Date: Mon, 24 Jun 2002 22:16:00 -0400
I believe you are right, snmpCollect covers it. One thing, though. If
you change something in mib.coerce that affects anything that has
been collected on before, you need to purge that collected data.
Once the unit is stored in the ! file, it is not  changed until you delete
that file.


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

                      (Todd H.)                To:       nv-l@lists.tivoli.com  
                      06/24/2002 08:17         Subject:  [nv-l] data 
collection/thresholds, config files, daemons                 
                      Please respond to                                         


I'm creating procedures for adding trap support for some new devices
that will be followed by other NetView administrators.  I'd like to be
able to specify the procedures completely from the command line by
distributing a text file that can be appended to each of the
configuration files that are affected.

When changing various configuration files, which daemons must be
restarted for the change to be noted to the running daemons?
Unfortunately the man page for each of these really doesn't say.

mib.coerce   ->  snmpCollect is my best guess?
mibExpr.conf -> snmpCollect ?
snmpcol.conf -> snmpCollect ?

or do all deamons need to be brought down?

Is this documented anywhere?

TIA for any insight or advice!

Best Regards,
Todd H.

To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web