nv-l

RE: [nv-l] Error when starting Netview

2004-12-03 10:00:13
Subject: RE: [nv-l] Error when starting Netview
From: "D'Apice, Domenico" <D.D'Apice AT SAQ.qc DOT ca>
To: "'nv-l AT lists.us.ibm DOT com'" <nv-l AT lists.us.ibm DOT com>
Date: Fri, 3 Dec 2004 09:59:41 -0500
Hello James,

Even I copy /usr/OV/conf from one server to another, i always have 2
differents hostname community name. How is possible ?  i did the xnmsnmpconf
-clearCache and it is the same thing...

Dominic

-----Message d'origine-----
De : owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
com]De
la part de James Shanks
Envoyé : Thursday, December 02, 2004 16:52
À : nv-l AT lists.us.ibm DOT com
Objet : RE: [nv-l] Error when starting Netview


Perhaps I am missing something here, but this should not be this 
difficult.

We copy usr/OV/conf from box to box all the time. But we use tar and pax 
and ftp to do it.

On AIX, snmpd is configured in /etc/snmpd.conf via edit.
NetView is configured in /usr/OV/conf/ovsnmp.conf_db which is accessed via 
xnmsnmpconf

After you copy that from one system to another, do 
        xnmsnmpconf -clearCache
to force the resolution to be from the files and not what is in memory, 
and then try your test
        xnmsnmpconf -resolve <hostname> | grep community.

If the two (snmpd.conf and xnmsnmpconf) match, all NetView daemons and 
processes will start successfully but otherwise not.
If they do match and you still get the "cannot talk to snmpd" message, 
then try stopping and starting snmpd
        stopsrc -s snmpd
        startsrc -s snmpd

And if that doesn't work, make sure you are using the SNMPv1 agent.
        snmpv3_ssw -1 
should switch it if you are not.




James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group