Leslie,
Looks like this is a bug. Here is the scenario. I have a network
device (Cisco Router)
which has a "public" read community set on it (This is a lab
environment). I setup
different community string in ovsnmp.conf using xnmsnmpconf
application. Just for an example say it was set to "notusepublic".
There is no community string
defined in /usr/OV/conf/communityNames.conf. That file is blank. If
I use demandpoll or configuration polling on that device, it is
modifying community string from "notusepublic" to public. I have
tested this for at least 5 times. If the community
string is set to something else then "public" on that device,
demandpoll/configuration polling fails. That is the way it is
supposed to work. My global default is set to "public". If demandpoll
defaults to Global default that is fine but it should not modified
entry in ovsnmp.conf file.
Any comments?
Shailesh Patel
EDS
-----Original Message-----
From: Leslie Clark/Southfield/IBM [mailto:lclark@us.ibm.com]
Sent: Friday, November 03, 2000 8:44 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] Netview changing snmp config by itself
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
ovsnmp.conf.
The Sherlock Holmes approach to problem determination works for me:
When you eliminate the impossible, whatever remains, however improbable,
must be the truth.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Peter Anderson" <pETERanderson@westpac.com.au>@tkg.com on 11/02/2000
08:20:01 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "Netview List (E-mail)" <nv-l@tkg.com>
cc:
Subject: [NV-L] Netview changing snmp config by itself
Hi,
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
node.
Our default is:
*.*.*.*:public:*:100:2:7200:::604800:604800:86400:10:1:0:1
Our smartset entries are similar but with slightly different timeout
settings, depending on the set.
branch_swch:public:*:200:2:7200:::604800:2419200:86400:1:0:0:0
I've found two occasions where entries are created like:
hostname1:xyz::::::::::::
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?
Regards,
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
|