I have seen this behavior and I am running 6.02. I changed global default
and left the community names file empty. Later, after doing initital
discovery I put my company-defined community string in and added nodes to
discovery. From time to time, I have to go in and whack the public entry. No
idea why this happens but the trigger is when I see routers sending in SNMP
authentication failure traps. I know there is something screwy here but I
haven't been able to make it happen in a controlled fashion.
From: owner-nv-l AT tkg DOT com [mailto:owner-nv-l AT tkg DOT com]On Behalf Of
Sent: Monday, July 30, 2001 8:18 PM
To: IBM NetView Discussion
Subject: Re: [NV-L] community name changes
Don, I have seen confusing behavior in this area a lot. First, do you know
that at 6.01, public is used as if it were in the alternates file whether
want it or not, and at 6.02 it is not used unless specified? I hope you
are at 6.01,
because the explanation would be easier. The next odd thing I have been
seeing is the insertion of bogus communities. But I believe that in almost
case those turned out to be for nodes that had name resolution problems.
up the name resolution in both directions and a couple of demandpolls ( or
rediscovering the node) cleared it up. I know, I know, you couldn't
any name resolution problems....;) My routine now includes:
fix any name problems for the node
delete any related xnmsnmpconf entries (name or address)
demandpoll (it will always work, because it tries everything)
check snmp using one of the MIB appls, which only checks xnmsnmpconf
If it works for Monitor..MIB Values..System Info, then it should work for
snmpCollect, I think. The snmpCol.trace will tell you if it also has name
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
"Davis, Donald" <donald.davis AT firstcitizens DOT com>@tkg.com on 07/30/2001
Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
Sent by: owner-nv-l AT tkg DOT com
To: "'NV-L AT tkg DOT com'" <NV-L AT tkg DOT com>
Subject: [NV-L] community name changes
For the sake of this discussion, let's say that my Global Default community
name is "raleigh".
I have a default communityNames.conf file with no entrys (all comments).
I am NOT using the "-h" netmon flag. (alternate community strings during
Nodes using "raleigh" mysteriously are being added in xnmsnmpconf with a
unique community name of "public".
This really messes up SNMP data collection statistics :(
Has anyone else seen this?
What is happening here?
How do I turn this "feature" OFF ?
Systems Engineer Consultant
First Citizens Bank
100 East Tryon Road
Raleigh, NC. 27603-3526
This electronic mail and any files transmitted with it are confidential and
are intended solely for the use of individual or entity to whom they are
addressed. If you are not the intended recipient or the person responsible
for delivering the electronic mail to the intended recipient, be advised
that you have received this electronic mail in error and that any use,
dissemination, forwarding, printing, or copying of this electronic mail is
strictly prohibited. If you have received this electronic mail in error,
please immediately notify the sender by return mail.
NV-L List information and Archives: http://www.tkg.com/nv-l