CM 4.0.13 Collection crashes IOS on 2960-24-PC-L

Unanswered Question
Jul 27th, 2009

The switches 2960-24-PC-L and 2960-48-PST-L listed as supported by CM 4.0.13 get crashed when perform data collection.

Cisco Output interpreter does not recognize the errors.

See crash output bellow:

000039: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: System previously crashed with the following message:

000040: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE, RELEASE SOFTWARE (fc1)

000041: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Copyright (c) 1986-2009 by Cisco Systems, Inc.

000042: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Compiled Sat 28-Feb-09 03:51 by weiliu

000043: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED:

000044: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Debug Exception (Could be NULL pointer dereference) Exception (0x2000)!

000045: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED:

000046: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: SRR0 = 0x01037C54 SRR1 = 0x00029230 SRR2 = 0x00648384 SRR3 = 0x00021000

000047: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: ESR = 0x00000000 DEAR = 0x00000000 TSR = 0x8C000000 DBSR = 0x10000000

000048: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED:

000049: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: CPU Register Context:

000050: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Vector = 0x00002000 PC = 0x010893F0 MSR = 0x00029230 CR = 0x22000042

000051: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: LR = 0x010893B4 CTR = 0x0102C6F8 XER = 0x20000075

000052: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R0 = 0x010893B4 R1 = 0x029DDFE0 R2 = 0x00000000 R3 = 0x02620A7C

000053: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R4 = 0x00000000 R5 = 0x00000000 R6 = 0x00000000 R7 = 0x00000000

000054: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R8 = 0x00007530 R9 = 0x00000000 R10 = 0x00000000 R11 = 0x00000005

000055: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R12 = 0x25AB8316 R13 = 0x00110000 R14 = 0x011F033C R15 = 0x00000000

000056: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000

000057: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x0000006A

000058: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R24 = 0x00000000 R25 = 0x0000006B R26 = 0x00000000 R27 = 0x00000000

000059: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: R28 = 0x00000000 R29 = 0x0150675C R30 = 0x01B181D4 R31 = 0x00000000

000060: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED:

000061: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Stack trace:

000062: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: PC = 0x010893F0, SP = 0x029DDFE0

000063: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Frame 00: SP = 0x029DDFF0 PC = 0x010893B4

000064: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Frame 01: SP = 0x029DE020 PC = 0x0102740C

000065: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Frame 02: SP = 0x029DE038 PC = 0x01027230

000066: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Frame 03: SP = 0x029DE070 PC = 0x0102155C

000067: Jul 24 20:02:50.004: %PLATFORM-1-CRASHED: Frame 04: SP = 0x029DE090 PC = 0x0122A588

000068: Jul 24 20:02:50.013: %PLATFORM-1-CRASHED: Frame 05: SP = 0x029DE0C8 PC = 0x00AFC634

000069: Jul 24 20:02:50.013: %PLATFORM-1-CRASHED: Frame 06: SP = 0x029DE0E8 PC = 0x011F062C

000070: Jul 24 20:02:50.013: %PLATFORM-1-CRASHED: Frame 07: SP = 0x029DE0F0 PC = 0x0108B37C

000071: Jul 24 20:02:50.013: %PLATFORM-1-CRASHED: Frame 08: SP = 0x00000000 PC = 0x01081E4C

000072: Jul 24 20:02:50.013: %PLATFORM-1-CRASHED:

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Mon, 07/27/2009 - 09:45

This is CSCta48905. It is fixed in 12.2(50)SE3.

Symptom:

A system running 12.2(50)SE or later may unexpectedly restart when

configured for SSH (or ip http secure-server) access, when an interface

that has macro description configured with

a description that does not match an Auto Smartports trigger name.

This command may be configured by Smartports with a smartports

macro name.

Conditions:

This has only been observed on Cisco IOS Software release 12.2(50)SE and

later with the macro description configuration has

been added by Smartports. When the interface that has this configuration

goes down, Auto Smartports tries to run a trigger that matches what is

configured by the macro description command.

If no such IOS shell trigger exists, the attempt to run the trigger fails. Later

when an SSH or Secure HTTP session is attempted and fails due to

authentication failure, the device may unexpectedly restart.

A second condition can cause this unexpected restart. If the device has

macro auto global processing configured and

a Cisco Discovery Protocol (CDP) enabled device that sets the host bit or

does not set any bits in the CDP capability TLV is connected to a switch

Auto Smartports tries to run a trigger that does not exist which fails.

Later when an SSH or Secure HTTP session is attempted and fails due to

authentication failure, the device may unexpectedly restart.

Workaround:

Add triggers and Auto Smartports macros for the macro

description commands that were created by Smartports.

For example if the macro description cisco-phone

is configured the following can be added to the configuration to avoid

the unexpected restart:

shell trigger cisco-phone cisco-phone

macro auto execute cisco-phone {

enable

}

With the trigger now existing it won't fail to execute and the unexpected

restart will be avoided.

rgomes Mon, 07/27/2009 - 10:42

Thanks for the information.

The 12.2(50)SE3 for the 2960 platform is not available in the download area.

How can we obtain such IOS release?

Joe Clarke Mon, 07/27/2009 - 10:50

It has not yet been released. It is scheduled to be released at the end of this month.

Actions

This Discussion