Scott, run the same command, but with only the short name "nodex" and
see if results are the same. I have seen strange things with how it
resolves the community name that I haven't figured out yet. Also try
clearing the xnmsnmp -clearcache and try it again.
Jeff Fitzwater
OIT Systems & Networking
Princeton University
On Oct 13, 2003, at 4:08 PM, Bursik, Scott {PBSG} wrote:
NetView 7.1.3 AIX 4.3.3
I am getting authenticationFailure traps in my trapd.log so I am
researching
the cause.
One of the nodes I am targeting that is sending authenticationFailure
traps
is "nodex.pepsi.com". His community name should be "comm2"
When I look at his snmp settings with xnmsnmpconf I get the following:
[netviewserver][/usr/OV/bin]>xnmsnmpconf -res nodex.pepsi.com
name = nodex.pepsi.com
community = comm5
proxy = <none>
timeout = 50
retry = 8
pollInterval = 600
remotePort = 161
setCommunity = comm6
discoveryPoll = 1
useAutoAdjust = 1
fixedInterval = 900
confInterval = 86400
nodeDownIntrval= 604800
routeEntries = 800
discoverManage = 1
ipAddr = 157.146.181.153
isProxied = FALSE
ipAddrAge = Mon Oct 13 14:57:45 2003
Obviously the settings are not correct so I run the following command:
[netviewserver][/usr/OV/bin]>xnmsnmpconf -update
nodex.pepsi.com:comm2:*:5:3:10m::comm3
And when I run the xnmsnmpconf -res command again the same OLD settings
still show. I have tried to clear the cache and tried deleting the
nodes
settings using the xnmsnmpconf -delete nodex.pepsi.com and still the
old
setting show. Here is the kicker though. If I enter the GUI the
community
name looks correct.
Am I missing something here?
Thanks,
Scott Bursik
PBSG
|