To: | "'Qureshi, Fawad'" <Fawad.Qureshi@ssa.gov>, nv-l@lists.tivoli.com |
---|---|
Subject: | RE: [nv-l] Snmpwalk failure |
From: | "Davis, Donald" <donald.davis@firstcitizens.com> |
Date: | Fri, 25 Jul 2003 17:27:19 -0400 |
Delivered-to: | mailing list nv-l@lists.tivoli.com |
Delivery-date: | Fri, 25 Jul 2003 22:29:36 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
List-help: | <mailto:nv-l-help@lists.tivoli.com> |
List-post: | <mailto:nv-l@lists.tivoli.com> |
List-subscribe: | <mailto:nv-l-subscribe@lists.tivoli.com> |
List-unsubscribe: | <mailto:nv-l-unsubscribe@lists.tivoli.com> |
Mailing-list: | contact nv-l-help@lists.tivoli.com; run by ezmlm |
I
have
seen this movie before :)
Are
you using /usr/OV/conf/communityNames.conf???
Here's
my "guess" at why this is happening is
this: Netmon
has access to communityNames.conf and therefore, netmon can successfully
demandpoll the node.
However, other applications use the xnmsnmpconf (snmp) database
exclusively.
Any
of
the snmp commands (set, get, walk), Monitor-->MIB Values-->System
Information, etc.. - ALL fail.
Are
you doing data collection? It is probably not working
either.
Cleanup your community names database (xnmsnmpconf).
Get
rid of communityNames.conf.
My advise is
to only use communityNames.conf temporarily to
help
with node discovery and not to use it routinely.
Don
Davis
First
Citizens Bank
Raleigh, NC. 27603-3526
------------------------------------------------------------------------------ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] Snmpwalk failure, Gareth Holl |
---|---|
Next by Date: | Re: [nv-l] Deletion of objects from normal topology DB, Paul |
Previous by Thread: | Re: [nv-l] Snmpwalk failure, Gareth Holl |
Next by Thread: | [nv-l] RE: Switch Analyzer, Scherting, Mark |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web