2924XL Locking Up
boostinbadger
Member Posts: 256
in CCNA & CCENT
Here is an output of a "debug all" from one of my 2924s:
CBTSW2_2924XL#deb all
This may severely impact network performance. Continue? [confirm]
All possible debugging has been turned on
CBTSW2_2924XL#
00:01:41: start_timer id mismatch satellite dm 0 state 1 id 536DE0 exp id 536D60
00:01:41: start_timer id mismatch satellite dm 0 state 1 id 536D60 exp id 536F60
00:01:41: start_timer id mismatch satellite dm 1 state 1 id 537420 exp id 5371E0
00:01:41: start_timer id mismatch satellite dm 1 state 1 id 5371E0 exp id 537160
00:01:41: start_timer id mismatch satellite dm 2 state 1 id 537220 exp id 536E20
00:01:41: start_timer id mismatch satellite dm 2 state 1 id 536E20 exp id 5374E0
CBTSW2_2924XL#
00:01:43: CPU Interface 0 storage notify failed on queue 1
00:01:43: CPU Interface 0 storage notify failed on queue 1
00:01:44: SNMP: HC Timer 663134 fired
00:01:44: SNMP: HC Timer 663134 rearmed, delay = 5000
CBTSW2_2924XL#
00:01:45: CPU Interface 0 storage notify failed on queue 1
00:01:45: CPU Interface 0 storage notify failed on queue 1
CBTSW2_2924XL#
00:01:47: CPU Interface 0 storage notify failed on queue 1
00:01:47: CPU Interface 0 storage notify failed on queue 1
CBTSW2_2924XL#u all
00:01:49: SNMP: HC Timer 663134 fired
00:01:49: SNMP: HC Timer 663134 rearmed, delay = 5000
00:01:49: CPU Interface 0 storage notify failed on queue 1
00:01:49: CPU Interface 0 storage notify failed on queue 1
00:01:49: start_timer id mismatch satellite dm 1 state 1 id 536FE0 exp id 536FA0
00:01:49: start_timer id mismatch satellite dm 1 state 1 id 536FA0 exp id 536E20
00:01:49: start_timer id mismatch satellite dm 2 state 1 id 537160 exp id 5374E0
00:01:49: start_timer id mismatch satellite dm 2
All possible debugging has been turned off
What causes this? I have done a "wr er" and still get this. After a couple minutes (without debug all) the switch becomes unresponsive and I have to pull the plug.
CBTSW2_2924XL#deb all
This may severely impact network performance. Continue? [confirm]
All possible debugging has been turned on
CBTSW2_2924XL#
00:01:41: start_timer id mismatch satellite dm 0 state 1 id 536DE0 exp id 536D60
00:01:41: start_timer id mismatch satellite dm 0 state 1 id 536D60 exp id 536F60
00:01:41: start_timer id mismatch satellite dm 1 state 1 id 537420 exp id 5371E0
00:01:41: start_timer id mismatch satellite dm 1 state 1 id 5371E0 exp id 537160
00:01:41: start_timer id mismatch satellite dm 2 state 1 id 537220 exp id 536E20
00:01:41: start_timer id mismatch satellite dm 2 state 1 id 536E20 exp id 5374E0
CBTSW2_2924XL#
00:01:43: CPU Interface 0 storage notify failed on queue 1
00:01:43: CPU Interface 0 storage notify failed on queue 1
00:01:44: SNMP: HC Timer 663134 fired
00:01:44: SNMP: HC Timer 663134 rearmed, delay = 5000
CBTSW2_2924XL#
00:01:45: CPU Interface 0 storage notify failed on queue 1
00:01:45: CPU Interface 0 storage notify failed on queue 1
CBTSW2_2924XL#
00:01:47: CPU Interface 0 storage notify failed on queue 1
00:01:47: CPU Interface 0 storage notify failed on queue 1
CBTSW2_2924XL#u all
00:01:49: SNMP: HC Timer 663134 fired
00:01:49: SNMP: HC Timer 663134 rearmed, delay = 5000
00:01:49: CPU Interface 0 storage notify failed on queue 1
00:01:49: CPU Interface 0 storage notify failed on queue 1
00:01:49: start_timer id mismatch satellite dm 1 state 1 id 536FE0 exp id 536FA0
00:01:49: start_timer id mismatch satellite dm 1 state 1 id 536FA0 exp id 536E20
00:01:49: start_timer id mismatch satellite dm 2 state 1 id 537160 exp id 5374E0
00:01:49: start_timer id mismatch satellite dm 2
All possible debugging has been turned off
What causes this? I have done a "wr er" and still get this. After a couple minutes (without debug all) the switch becomes unresponsive and I have to pull the plug.
Comments
-
tiersten Member Posts: 4,505Reflash IOS on that switch. If it still does it then its probably bad and needs to be replaced.
-
boostinbadger Member Posts: 256Sometime over the weekend, the switch locked again. I did a debug all on my other switches and they too scroll the start_timer id mismatch... but they still work.