Re: communitynames.conf seems not to work properly for NV 6.01 for N T.
This is working fine for me. There is an option to say whether to use the
alternates only on initial discovery. Perhaps your devices were discovered
once as non-snmp nodes before you added the names? You could change
the setting (on Discovery, I think) to use it all the time for a while (it
overhead), and demand-poll some of the nodes. Or delete them and
rediscover them. When I had to add a new community string to the file after
some nodes were discovered as non-snmp, I only had to demand-poll them
and then they changed into routers. I believe mine is set to only use it on
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Hlaves Josef <hlaves AT datasys DOT cz>@tkg.com on 09/04/2000 12:19:17 PM
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
Subject: [NV-L] communitynames.conf seems not to work properly for NV 6.01
for N T.
I have five read community names for all routers in my network. I entered
the community names in the file communitynames.conf.
But the routers haven't been discovered at all.
I must write down my community names for each router by means of SNMP
to make NetView discover my routes properly.
I would greatly appretiate if somebody tell me how to make use of the file
communitynames.conf properly for discovery process.
NV-L List information and Archives: http://www.tkg.com/nv-l