Hi,

I have a peculiar problem with bad community while NetView is talking to
some nodes. We use four different community names beside the default
"public", and they have been added to the communityNames.conf file. Most
nodes and their community name (except the ones using "public") are then
added to the snmp configuration database automatically by NetView itself.
But not all of them. Some of them (of some reason they're all Cisco
switches) just don't get there, so each time I demand poll the node or
NetView uses SNMP to query it, I get numerous of authentication failure
traps before I get any respond from it. Like if it first tries "public",
then the first entry in communityNames.conf, the second entry and so on
until it gets to the one that work with the actual node. If I manually add
the node in snmp configuration ofcourse it will the work alright but that
shouldn't be needed, right?
To spare my event log I added a SmartSet called Cisco_Switches to my snmp
configuration with the right community, but how do I solve this without
doing such walk-around?

TIA

Hälsningar/Regards
Måns Langert

IBM Global Services
Phone: +46 8 793 3935
Mobile: +46 70 793 3935
E-mail: mans.langert AT se.ibm DOT com
SMS: 0707933935 AT sms.tele2 DOT se