nv-l
[Top] [All Lists]

RE: [nv-l] Finding offending application

To: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Finding offending application
From: "Evans, Bill" <Bill.Evans@hq.doe.gov>
Date: Wed, 23 Jun 2004 17:59:03 -0400
Delivery-date: Wed, 23 Jun 2004 23:18:51 +0100
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

Common problem with no good solution.  Cisco products generally send the originating node of the failing SNMP request in their trap.  No one else seems to.  You have to go to the ORIGINATING machine for the trap and look in its log to find the ultimate offender.  If the trap was sent by a router,  switch or server other than Cisco the identifier will usually be in that device's log. 

Bill Evans
Tivoli NetView Support for DOE
301-903-0057

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Brian W Green
Sent: Wednesday, June 23, 2004 1:19 PM
To: Netview Mailing List
Subject: [nv-l] Finding offending application

We have an issue on one of our AIX Servers where an application is
sending SNMP polls with the incorrect community string.  Does anyone
know of a way to figure out what application is doing this, other than
going through every app individually?  We checked the /var/tmp/snmpd.log
file, but that only shows the source as 127.0.0.1

Thanks,

Brian

Brian W. Green
IBM Certified Deployment Professional
CGI Information Systems and Management Consulting
275 Slater Street, 14th Floor
Ottawa, Ontario
K1P 5H9
(613) 234-2155
brian.green@cgi.com

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

Archive operated by Skills 1st Ltd

See also: The NetView Web