[c-nsp] no more snmp traps

[Cameron.Dry at didata.com.au]

This looks like bug CSCeg02095

Release Notes
 
Symptoms: A Cisco router may not report its SNMP sysobjID. Instead, the
router generates the following tracebacks:

%SNMP-3-BADOID: Attempt to generate an invalid object identifier
-Traceback= 611DD8EC 611DD76C 611DD560 61203F90 60EA7238 60EA721C

This situation prevents the router from being identified as a Cisco
device,
and network management applications are unable to manage the router.

Conditions: This symptom is observed on a Cisco 3660 (CISCO3660-MB-1FE)
that
runs a telco image.

Workaround: Run an enterprise image, which enables the device to be
managed.
If this is not an option, there is no workaround.


HTH

Cameron

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of consta at gmail.com
Sent: Wednesday, 17 November 2004 6:29 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] no more snmp traps


Hi,

I hope i'm not crossing the line asking too many (some might find
stupid) questions here on the list. First, let me tell you that i've
searched on google, and also on Cisco Bug Toolkit.

I had 2 Cisco 3660 running Telco 122-23a. They both used to send snmp
traps to a collector machine. I can't say exactly when it happened, but
for some time, none of them sends traps (checked it with tcpdump), and
int the log buffer i get tracebacks:

Nov 16 23:54:17.779 EET: %LINK-3-UPDOWN: Interface FastEthernet0/0,
changed state to up Nov 16 23:54:17.779 EET: %SNMP-3-BADOID: Attempt to
generate an invalid object identifier -Traceback= 607B0130 607AFD1C
607DD380 607DDE84 607DE3F4 607DD868 607E187C 607E1958 607D1358 Nov 16
23:58:29.530 EET: %SNMP-3-BADOID: Attempt to generate an invalid object
identifier -Traceback= 607B0130 607AFD1C 607DD380 607DDE84 607DE3F4
607DD868 607E187C 607E1958 607D1358 Nov 17 00:14:24.891 EET:
%LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up Nov 17
00:14:24.891 EET: %SNMP-3-BADOID: Attempt to generate an invalid object
identifier -Traceback= 607B0130 607AFD1C 607DD380 607DDE84 607DE3F4
607DD868 607E187C 607E1958 607D1358 Nov 17 00:14:27.091 EET:
%SNMP-3-BADOID: Attempt to generate an invalid object identifier
-Traceback= 607B0130 607AFD1C 607DD380 607DDE84 607DE3F4 607DD868
607E187C 607E1958 607D1358

I decided today to upgrade to 122-27, 122-23a having some software
advisories, but it didn't help either.

The link found on Google points to a post from a couple of years ago,
which didn't get any answer...

http://www.google.ro/search?q=cache:kgR7PTsntGsJ:www.groupstudy.com/arch
ives/cisco/200205/msg00141.html+SNMP-3-BADOID&hl=ro

Any clues?

Regards,
-- 
Sorin CONSTANTINESCU
consta at gmail.com
Linux Registered User #222086
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


******************************************************************************
 - NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged information.  If you have received this email in error, please notify the sender and delete it immediately.

Internet communications are not secure. You should scan this message and any attachments for viruses.  Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.
******************************************************************************