Re: Netview changing snmp config by itself

2000-11-03 08:43:58
Subject: Re: Netview changing snmp config by itself
From: "Leslie Clark/Southfield/IBM" <lclark AT us.ibm DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Fri, 3 Nov 2000 08:43:58 -0500
Spooky, eh? Well, there only 2 possible explanations. Either someone has
added a specific entry unbeknownst to you, or someone has added an entry to
/usr/OV/conf/communityNames.conf, which Netview will try when nothing in
ovsnmp.conf works.  If something in there works, it adds entries to

The Sherlock Holmes approach to problem determination works for me:
When you eliminate the impossible, whatever remains, however improbable,
must be the truth.


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

"Peter Anderson" <pETERanderson AT westpac.com DOT au>@tkg.com on 11/02/2000
08:20:01 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com

To:   "Netview List (E-mail)" <nv-l AT tkg DOT com>
Subject:  [NV-L] Netview changing snmp config by itself


We have Netview Unix 6.0.1 on Solaris 2.7.

I've had a problem occur a couple of times where Netview in its infinite
wisdom creates new entries in the ovsnmp.conf_db database for individual
nodes, using Netview defaults but with community names not found anywhere
except in the managed device itself.

For example, we use public for all our read-only monitoring but use say
"xyz" as our read-write community name.

I setup the ovsnmp.conf_db with only static entries for our two Netview
boxes, and either the default or a smartset entry for every other managed

Our default is:


Our smartset entries are similar but with slightly different timeout
settings, depending on the set.


I've found two occasions where entries are created like:


It's only happened twice, and it has happened when nobody has been using
Netview, just the daemons in the background doing polling.  Entries haven't
been created for EVERY managed node - just some.

Unfortunately, the above settings cause high CPU usage on our smaller Cisco
routers, which I think is due to netmon wanting to get the entire routing
table and with a small timeout, retries occur.

I Netview designed like this and if so why?


Peter Anderson
Senior Communications Analyst
Westpac Banking Corporation
Ph:  0011 61 2 99025938
<Remove ETER from my address to reply>

Any views or opinions presented are solely those of the author and do not
necessarily represent those of Westpac Banking Corporation.

NV-L List information and Archives: http://www.tkg.com/nv-l

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