[Top] [All Lists]

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

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Authentication Failure Traps Root Cause Question
From: Paul Stroud <pstroud@bellsouth.net>
Date: Mon, 8 Dec 2003 11:33:32 -0500
Delivery-date: Mon, 08 Dec 2003 16:44:37 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <42AF0749A8EB7448A661EC423CBE76FA01EDAD52@pbswmu00003.corp.pep.pvt>
References: <42AF0749A8EB7448A661EC423CBE76FA01EDAD52@pbswmu00003.corp.pep.pvt>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Are there any other NMS's running around, we see this quite often were
a rogue group is running thier own NMS. The best way to check this is
to trace the SNMP agent on the device itself and see if you can determine
where the requests are originating. 


On Monday 08 December 2003 11:19, you wrote:
> 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 ( 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