nv-l
[Top] [All Lists]

AW: SNMP-Configuration and more Problems

To: nv-l@lists.tivoli.com
Subject: AW: SNMP-Configuration and more Problems
From: FITZINGER Richard <richard.fitzinger@it-austria.com>
Date: Fri, 9 Jun 2000 14:30:04 +0200
hi!

we did some testing and found out that the only way to prevent unwanted
"public" entries in ovsnmp.conf is to rename/remove the communityNames.conf
file. 

some more stuff? here is the description of the test:

scenario: 
- Netview/AIX V6 with default options for all netview daemons
- seed-file with one entry (CISCO RSM). the device with read community
"public".
- ovsnmp.conf contains two entries: global default read community "xxx" and
a specific entry for the RSM with read community "rsm".
- communityNames.conf is existing. netmon is NOT configured to use it (no -h
option)

test1: "demand poll" from the menu bar -> the specific entrie gets its own
IP addy as "proxy" and it gets "public" instead of "rsm". cool!!!

test2: change it back to "rsm", restart netmon. netmon does a new node poll
and... changes ovsnmp.conf in the same way. "public" again. cool? no.
hardcoded, I guess.

test3: rename communityNames.conf and "demand poll": everything ok, "rsm" is
still there.

if you do NOT want to use "alternate communities" you should move the file
to a save place to avoid this behaviour of netview. at least, this is true
for OUR environment.

we have also got some other testing results (e.g. what netmon does after it
is restarted, what the ovsnmp.conf values "time-out" and "retries" mean,
what happens to a CISCO RSM and a Nortel VNR during demand poll and
therefore asking for ipNetToMediaTable twice...). if somebody is interested
I will post it.

regards, richard


-----Ursprüngliche Nachricht-----
Von: Karsten.Schweiger@gecits-eu.com
[mailto:Karsten.Schweiger@gecits-eu.com]
Gesendet: Freitag, 9. Juni 2000 09:35
An: IBM NetView Discussion
Betreff: Re: [NV-L] SNMP-Configuration and more Problems




Hi Chris.
We have no entries in /usr/OV/conf/communityNames.conf, so it must be a
different behavior.
Thanks Leslie for your solution about the workspace problem "Name already
exists".


Mit freundlichen Gruessen - Yours sincerely

Dr. Karsten Schweiger
GE CompuNet Hamburg
Netzwerk und System Management
Ost- West Strasse 49, 20457 Hamburg, Germany
Phone: +49 (0) 431-3609-0, +49-0177-6302825, Fax: +49 (0) 431-3609-190,
E-Mail : Karsten.Schweiger@GECITS-EU.COM


This email is confidential. If you are not the intended recipient,
you must not disclose or use the information contained in it.
If you have received this mail in error, please tell us
immediately by return email and delete the document.





Chris Cowan <chris.cowan@2nd-wave.com> on 05.06.2000 19:25:43

Please respond to IBM NetView Discussion <nv-l@tkg.com>

To:     IBM NetView Discussion <nv-l@tkg.com>
cc:      (bcc: Karsten Schweiger/Hamburg/GECITS-EU)
Subject:  Re: [NV-L] SNMP-Configuration and more Problems
 

 

 
----------------------------------------------------------------------------
-- 




Karsten.Schweiger@gecits-eu.com wrote:
>
> Hi all.
> In our newly created environment (NetView 6.0, AIX 4.3.3, CW2000) we have
> different problems. We are using a seed-file and a different
community-name
(not
> public, public is deleted). After discovering new nodes there appeared
newly
> entries in ovsnmp.conf, especially for those nodes which have
"public"-entries
> in their snmpd.conf file. It seems that NetView writes automatically after
> discovering in its ovsnmp.conf file.

This is most likely because you have entries in
/usr/OV/conf/communitynames.conf.


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

Archive operated by Skills 1st Ltd

See also: The NetView Web