Incorrect Community Name

Unanswered Question
Nov 13th, 2008

Hi,

I'm using HP OV Network Node Manager for monitoring network.

for tha past few weeks, four (out of 8) 2811 routers are reporting "Incorrec Community Name" auth failure traps. Snmp get commands were suposed to be generated by NNM (authAddr gives me that info), but I'm sure that RO community is same in NNM as one on routers.

Any suggestions?

BR,

Ivan

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dany.datacraft Fri, 11/14/2008 - 00:13

Dude, you're posting in wrong forum. But here's what I think you can do:

Sniff the traffic going to the 4 routers reporting auth failure traps, and find out whether or not the community is correct.

Alternatively you can run 'debug snmp packet' and 'debug snmp requests' in the router.

icolakicolak Fri, 11/14/2008 - 00:29

Hi Dany!

I tried with "debug snmp xxx" but I can't see anything. Nothink logs, after snmp get with incorrect community name is run.

Any suggestions?

That's why I posted message here.

Points guaranteed!

BR,

Ivan

icolakicolak Mon, 11/17/2008 - 01:27

Hi Dany!

I've checkt sniffer log. What happens is that only once a day NNM uses incorrect community name.

So, read community is plinacro and NNM uses (as I said only once a day, few minutes after midnight) community: [email protected]

Any idea how to deal with it?

BR,

Ivan

icolakicolak Tue, 11/18/2008 - 01:50

Hi Dany!

I've just noticed that, when rediscovery is being done, suffix is attached on a community name. So, all devices have community name plinacro, and NNM polls devices with [email protected], [email protected] etc !!!

However, switches obviously can resolve “extended” community name, unlike routers which can't.

Any idea why is NNM doing that? Is that normal? Is there anything I can do to make routers able to “understand” extended community name?

Thanks for you time.

BR,

Ivan

Actions

This Discussion