Re: 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 AT GECITS-EU DOT 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 AT 2nd-wave DOT com> on 05.06.2000 19:25:43

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

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




Karsten.Schweiger AT gecits-eu DOT 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.

I personally like this new behavior.
chris.cowan.vcf
Description: Binary data