Domenico,
This is not my area of expertise, and it is getting very difficult to
advise you remotely.
Without being present I am not certain what is going on. But it's
beginning to sound to me as though the two boxes do indeed use different
community names.
Did you set them up? If not, why isn't the person who did involved?
Does one have a communitynames.conf file and the other not? Do they have
the same exact /etc/snmpd.conf file?
The only advice I have left is to make everything the same, and I do mean
everything.
Otherwise, you should call Support and start sending them your files to
examine, because something is different somewhere.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
"D'Apice, Domenico" <D.D'Apice@SAQ.qc.ca>
Sent by: owner-nv-l@lists.us.ibm.com
12/03/2004 09:59 AM
Please respond to
nv-l
To
"'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
cc
Subject
RE: [nv-l] Error when starting Netview
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@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]De
la part de James Shanks
Envoyé : Thursday, December 02, 2004 16:52
À : nv-l@lists.us.ibm.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
|