CSM fails after software upgrade

Unanswered Question
Sep 8th, 2009
User Badges:

Dear All,


We have upgraded the CSM software from 3.1(4) to 4.2(12).After upgrading the CSM software and reset, CSM module is in unknown state as shown in the following output:


Switch#show module 8


Mod Ports Card Type Model Serial No.


--- ----- -------------------------------------- ------------------ -----------

8 4 SLB Application Processor Complex WS-X6066-SLB-APC SAD……..



Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

8 0015.2b3d.cbbb to 0015.2b3d.cbbb 1.7 Unknown Unknown Other


After sometime Other state change to Power Down.


Switch#show module 8


Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

8 4 SLB Application Processor Complex WS-X6066-SLB-APC SAD……


Mod MAC addresses Hw Fw Sw Status


--- ---------------------------------- ------ ------------ ------------ -------

8 0015.2b3d.cbbb to 0015.2b3d.cbbb 1.7 Unknown Unknown PwrDown


Mod Online Diag Status


---- -------------------


8 Not Applicable


Another weired output:


Switch#show module csm 8 status

CSM module is offline.

Requires CSM module version 3.1.


Following are the logs we are getting:


Sep 6 14:32:15.061 : ÆKPWR-SP-4-DISABLED: power to module in slot 8 set off (Module Failed SCP dnld)


Sep 6 14:33:57.222 : %ONLINE-SP-6-TIMER: Module 8, Proc. 0. Failed to bring online because of timer event


Sep 6 14:33:57.222 : ÆKPWR-SP-4-DISABLED: power to module in slot 8 set off (Module Failed SCP dnld)


Sep 6 14:34:14.445 : ÆKPWR-SP-4-DISABLED: power to module in slot 8 set off (Reset)


We also physically removed the CSM module and insert it again but issue is still same.


We are also unable to access the csm module by the following command:


Switch#session slot 8 processor 0

The default escape character is Ctrl-^, then x.

You can also type 'exit' at the remote prompt to end the session

Trying 127.0.0.80 ...


We have also enabled the power serveral times by the following command:


Switch(config)#power enable module 8


How can I rollback(downgrade) the CSM software to the previous software.


We are using IOS version "IOS (tm) s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(18)

SXF7, RELEASE SOFTWARE (fc1)".


Another Testing:

when we remove this CSM module (slot 8) and insert it onto another slot (say slot 3), the module boots properly, without any issues. But ofcourse there is no configuration for this module in the running configuration. The 'show module' output on the core switch display the new version correctly 4.2(12). I can also do a 'session slot 3 proc 0' successfully. I have also checked the file we downloaded via an MD5 checker, and the file is not corrupted.


But when we again insert the module in slot 8 or 3, now the module won't boot in any slot. Same error as before for slot 8.


Another post regarding this issue:

http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Data%20Center&topic=Application%20Networking&topicID=.ee7814f&fromOutline=true&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cd44c13/6


Please reply soon


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Tue, 09/08/2009 - 02:10
User Badges:
  • Cisco Employee,

you probably uploaded an image that was corrupted. CSM can't boot anymore.

You need to unscrew the front panel cache to get access to the console port.


Connect to this port during boot and force access to rommon.


There is an option there to select previous image.


You should probably open a service request to get guidance on the exact procedure.


Here is the exact steps:


1 - Stop the boot process by pressing a key at "Press any key to stop

auto-boot..."

(I noticed that the customer has already tried this out)


2 - At the "[vxWorks Boot]" prompt, type "R"

3 - When the prompt returns, type "@" to boot the board


Please note that once step (1) is done, steps (2) and (3) must be

done right away. Waiting too long will cause the supervisor to cut

power from the CSM.


This process will allow the previous image to boot.


Gilles.

Actions

This Discussion