Are you sure that NetView is causing the error? Could some other box be sending
you SNMP traffic with a bad community name?
I would edit snmpd.conf set the logging level equal to 3 for full trace and then
restart snmpd and see what gets written to the trace log. The other logging
entry in snmpd.conf tells you where the log will go. To restart SNMP you would
enter
"stopsrc - s snmpd" (to stop it) and then "startsrc -s snmpd" to re-start
it. Then when you get the error go look at the snmpd log and see if you can
find the request that was made. It should show you the sender and community
name used.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Indy <indy.chakrabarti@ewllc.com> on 02/17/2000 10:50:11 AM
Please respond to indy.chakrabarti@ewllc.com
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Netview authentication failure on community name
I have Netview 5.1.2 on AIX 4.3.2.
I continually get an event that says I have an authentication failure on the
node on which Netview is installed due to a bad community name. Yet I see
that the node shows as "managed", and that snmpd is running on it, and I can
do an snmpwalk. The community name is set to public for my entire network,
and I can see the other nodes on the network w/o bad community name
problems. My snmp.conf and snmp.peers file looks okay too. And Netview seems
to run fine, despite this supposed bad community name. What causes this? And
how can I turn of this trap so I don't get this error?
Thanks.
|