03-14-2005 03:58 AM - edited 03-02-2019 10:07 PM
I've some problems on my 6500 I think that could be happened a switchower event with all modules resets... but I do not understand why...
After the resets the active supervisor is the second, and all works fine...
I post the sh tech
Thanks all
G.
03-14-2005 05:47 AM
I see the following in the sh log output
30. 3/12/2005,10:04:43: ProcessStatusPing:Module 2 not responding over SCP
31. 3/12/2005,10:08:00: ProcessStatusPing:Module 1 local SCP error detected... reinitializing SCP
32. 3/12/2005,10:08:00: ProcessStatusPing:Module 1 SLCP not responding... resetting module
33. 3/12/2005,21:49:12: ha_swover_sync_status:static-db:1, dyn-db:1 (0-invalid, 1-valid)
34. 3/12/2005,21:49:12: updateRuntimeWithNVRAM:Redundancy switch over: 1
35. 3/12/2005,21:50:33: ha_entity_swover_action:action: 4 (1-NOP, 4-CINIT), reason:9
36. 3/12/2005,21:50:33: ha_swover_type:Switchover type: 0 (1-HA, 0-Non-HA)
37. 3/12/2005,21:59:30: ProcessStatusPing:Module 1 local SCP error detected... reinitializing SCP
38. 3/12/2005,21:59:30: ProcessStatusPing:Module 1 SLCP not responding... resetting module
It is normally caused by a bad module in the chassis. Code enhancements were done to better handle this issue through
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCea38268
You cannot upgrade to latest 7.6 since you only have 64MB DRAM. Consider 6.4(15) which is GD and has this enhancement as well
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_11235.htm
03-14-2005 06:30 AM
Great!
thank you very much!
However at this moment all "sh test, sh mod, sh scp etc..." show me NO hardware issue...???
When I had the problem the switch's CPU was 69%... could be that strong traffic could provide SCP communication failure between the modules?
Thank you,
G.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide