nv-l
[Top] [All Lists]

RE: [nv-l] Authentication Failure Traps Root Cause Question

To: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Authentication Failure Traps Root Cause Question
From: Brian Kraftchick <Brian.Kraftchick@odfl.com>
Date: Mon, 8 Dec 2003 11:38:22 -0500
Delivery-date: Mon, 08 Dec 2003 16:47:27 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Scott,

I also from time to time see those same exact traps come in.  The
1.3.6.1.4.1.311 is Microsoft of course, so these are coming from our Windows
workstations, but I've yet to understand why.

Brian

-----Original Message-----
From: Bursik, Scott {PBSG} [mailto:Scott.Bursik@pbsg.com]
Sent: Monday, December 08, 2003 11:20 AM
To: Nv-L (nv-l@lists.us.ibm.com)
Subject: [nv-l] Authentication Failure Traps Root Cause Question


NetView 7.1.3 AIX 4.3.3

I am getting a lot of these events in my trapd.log for different nodes and I
am a bit confused. I know this is probably a basic question but what is the
root cause for these events? It appears that I have the community names
configured correctly in xnmsnmpconf so I am at a loss here. It is probably a
concept that I am missing.

nodea.pepsi.com  A Incorrect Community Name (authenticationFailure Trap)
enterprise:ENTERPRISES (1.3.6.1.4.1.311.1.1.3.1.2) args(0):

Thanks,

Scott Bursik
PepsiCo Business Solution Group


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web