|
Hello Stephanie,
I got only the direct copy of this note though I am subscribed to the nv-l list. But the address I use is nv-l@lists.ca.ibm.com, so perhaps that is why.
You do know that netmon uses the community name stored for a device or the default one from xnmsnmpconf. So if you change the device community name before you change NetView, then of course you would get authentication failures, especially if these are routers and you are polling them with SNMP. Also, if you have a communitynames.conf with multiple community names in it, and netmon is configured to use that for polling (via serversetup), then when an SNMP request fails, then netmon will try to use each name in the file in turn, resulting in multiple authentication failures, until one of them works. This may account for the barrage of authentication failures you get when you change community strings.
If this doesn't help, then I suggest you open a PMR to Support and get some individualized assistance.
James Shanks
Tivoli Network Availability Management Level Three
Network Availability Management
Tivoli Software, IBM Corp
1-919-224-1642 | T/L 687-1642 | ITN 26871642
 ss cc <steph_cornish@yahoo.com>
ss cc <steph_cornish@yahoo.com>
12/19/2008 02:24 PM
Please respond to
steph_cornish@yahoo.com |
|
|
All,
From time to time nvcorrd will core dump and I believe it's because it gets too many messages to process or it runs out of memory.
Does anyone have recommendations on how we should configure nvcorrd to handle large amounts of messages?
TIA,
Stephanie
|
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
