Don,
there is a really simple solution for your problem:
Just update to NetView 6.0.2.
6.0.1 netmon has problems with ip address wildcards
and ip addresses under specific nodes in the snmp configuration.
Kind regards
Oliver Bruchhaeuser
Tivoli NetView EMEA L2 Support
IBM Deutschland GmbH - ITS Tivoli - Dept. 7977 - Hechtsheimer Str. 2 -
55131 Mainz - Germany
Phone: +49-6131-84-5108 - Fax: +49-6131-84-6585 - email:
bruchhae AT de.ibm DOT com
Need help with Tivoli Software Products?
Ask Tivoli!
http://www.tivoli.com/asktivoli (login with your customer account)
"Don Helms"
<dhelms AT sw DOT org To: "'IBM NetView
Discussion'" <nv-l AT tkg DOT com>
> cc: <design_team AT sw DOT org>
Sent by: Subject: [NV-L] New Install - SNMP
conf failing
owner-nv-l@tkg
.com
15.11.2001
16:01
Please respond
to IBM NetView
Discussion
If this is covered in an archive somewhere, just point me
there and I'll gladly do the grunt work myself.
We are in the process of getting Tivoli Enterprise
Framework and NetView 6.01 installed on AIX. The
consultants have not fully turned it over, so we are
not set up with Tivoli Tech Support yet.
We are running multiple community strings on our network.
In the SNMP conf settings, I have "public" as a global
default and I'm trying to set up other strings in IP
address ranges.
During discovery, the global default "public" is working.
The wildcards are being ignored. If I enable the
communityNames.conf file, the correct community name gets
picked up here as a last resort, but then places hundreds of
individual device entries in the top section on the SNMP
config screen. This will be a major pain whenever we change
community strings - like as soon as this consulting team leaves.
Oddly, the wildcard entries fail during discovery, but seem to
work during a TEST:IP/TCP/SNMP Connectivity. The objects come
up as unknown types (e.g. not routers) and demand poll fails.
MIB browsing and connectivity testing work though, so the
correct community string is getting in there for part of the
process anyway.
An example from snmp.conf is included below
(Managed via GUI, not edited directly, SNMP strings
changed of course)
My seed file device is on the first line, this works OK.
The last line for "public" works OK.
Currently I am only using the two sets of strings. I expect
to see about 3-4 sets for different Admin teams in final
production.
------------------
r-core1.sw.org:community1:*:50:2:300::community2:604800::3600::1:1:1
*.*.*.250-254:community1:*:50:2:300::community2:604800::::1:1:1
10.1-9.*.*:community1:*:50:2:300::community2:604800::::1:1:1
10.250.*.*:community1:*:50:2:300::community2:604800::::1:1:1
10.99.*.*:community1:*:50:2:300::community2:604800::::1:1:1
205.203.59.*:community1:*:50:2:300::community2:604800::::1:1:1
205.203.*.1-19:community1:*:50:2:300::community2:604800::::1:1:1
10.*.*.1-19:community1:*:50:2:300::community2:604800::::1:1:1
*.*.*.*:public:*:50:2:300::system:604800::::1:1:1
------------------
Don Helms
Scott & White Hospital
dhelms AT sw DOT org
All Opinions are just that...
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|
