Either management station could be the culprit, if the systems having the
problem are in their maps. In the
/etc/snmpd.conf on the affected node there is an entry that tells you where the
log file is (it varies) and there
is a number that tells you the debug level, and another one that tells you the
size limit. I would check the
man page for snmpd.conf (man snmpd.conf) and change those settings, then
'refresh -s snmpd'. This is
on the affected node. If you crank up the debug level a notch, the error
messages in the log file will include
the bad community string being used, if that is the problem. Knowing what
community is being sent
usually helps you guess who is doing it. Looking in /etc/snmpd.conf on the
affected node tells you what it
is supposed to be for that node. That's for requests going to the affected node
(inbound). Then check the
two netviews and see what they are using for community strings on outbound
requests. That's configured
in 'Options...SNMP.. ' in Netview. See the Admin guide for how this works. I
suspect that you have a
default of private or something on one or both of the managent stations, and
the affected nodes don't have
that for a community string, so they are logging errors to report the
'trespass'.
If this is the case, you can: 1) change the community on the affected nodes to
match Netview, 2) change
the setting of the community to be used on the outbound in the Netviews, or 3)
ignore it and change the
log size on the affected nodes to something small enough to live with.
Until you look in the error logs, you won't know for sure what the problem is.
Cordially,
Leslie Clark
IBM Global Services - Network & Systems Management - Detroit
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 07-14-98
10:37 PM ---------------------------
NV-L@UCSBVM.UCSB.EDU on 07-14-98 11:01:57 AM
Please respond to NV-L@UCSBVM.UCSB.EDU
To: NV-L@UCSBVM.UCSB.EDU
cc:
Subject: Re: snmpd.log
Hi Leslie,
I think you could be right, because just a few days ago (or weeks) I
configure my NV to send traps to another network management station. That
station as a different community name than my NV box. Could that be causing
the problem ?
Thank you
Moe
|