I had to read that a couple of times to understand what you are talking
about,
so first let me confirm that I understood you correctly:
The node on the map is a Microsoft box, with snmp enabled, but none of
those
boxes checked in the snmp configuration in Windows. The thing barely knows
its own name, but does respond to the basic test for isSNMP Supported,
which
I think is just the snmp sysobjectid.
You say the node is deleted during configuration polling, which you
circumvent
by giving it a bad community. And you want to know if this is normal/new.
I think it is probably both normal and new. I suspect it is part of the
tightening up
of the discovery process that has given us improvements in the merging of
objects into a single object, which used to be a common problem and seems
to work very well lately. I would consider them to be badly-behaved nodes
and worthy of deletion. Netview seems to agree.
Something to check: bad name resolution could cause the same kind of
behavior.
Like, it resolves one way but not the other, or it resolves both ways but
not to
the same thing. Common problems when using a DNS. So check to make sure
that is not the real reason.
Another way to deal with the problem (besides correcting the agent on the
target node): add the I flag (capital i) to the oid_to_type file. Treats
them as
non-snmp at configuration poll time.
My opinion....
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
lesdickert@att.ne
t To: NV-L@lists.tivoli.com
cc:
07/29/2002 05:05 Subject: [nv-l] Netmon deleted
SNMP nodes with no MIBs
PM
I have noticed that if a Windows NT or Windows 2000
server has an SNMP agent loaded and running, but
does not have any MIB loaded, that netmon will delete
the node the next time it does a poll (I think for
configuration change, but maybe status too). I
have even manually added such a node, then done a
Demand Poll, and netmon will delete it immediately.
When I do a command line snmpwalk badnode system
I get an immediate
"End of MIB" reply, no variables or data.
Question: Is this new to NetView 7.0 or 7.1 or has
this been going on forever and I'm just now noticing
it?
BTW, I have a workaround that will force netmon to
not delete the node: put an entry in ovsnmp.conf
for the node with an invalid community string, and
netmon never gets as far as finding out that there are
no MIBs, so the node does not get deleted.
Thanks,
Les Dickert
Trigon Blue Cross/Blue Shield
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|