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
-----Original Message-----
We have an issue on one of our AIX Servers where an application is
Thanks, Brian Brian W. Green
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] SNMP Community Strings, Frank W. Hansen |
---|---|
Next by Date: | RE: [nv-l] SNMP monitoring anomaly, Evans, Bill |
Previous by Thread: | [nv-l] Finding offending application, Brian W Green |
Next by Thread: | [nv-l] SNMP Community Strings, Frank W. Hansen |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web