cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3539
Views
0
Helpful
15
Replies

Problem in upgrading IOS version 15.0-SE5 to 12.2-SE12

Aida Hadad
Level 1
Level 1

hi guys,

I've just started working in company which I should upgrade Switch IOSs based on Cisco website recommendations.

Among the all Switches which we upgraded, One of them is 2960 which runs IOS version 15.0(2)SE5.

Based on Cisco recommendation I wanted to change it to version 12.2(55)SE12 but during boot up it fails .

Can we change IOS from 15 to 12?

What might be its problem?

It must to mention that I don have any log right now but I remembered it passed the post procedures and hang right CPU .. but requirement for our devices is OK .DRAM 64 flash 32

1 Accepted Solution

Accepted Solutions

Peter Paluch
Cisco Employee
Cisco Employee

Hello Aida,

As mentioned by other colleagues here already, we unfortunately depend on seeing the complete and accurate console logs from that switch. The general fact is that on a Catalyst 2960 platform, you can freely upgrade and downgrade between any arbitrary IOS versions. Since your switch behaves differently, we need hard evidence to understand what is going on. We may speculate but neither of the hypotheses will be actually useful if not paired with correct symptoms.

By the way, there is not much you could have done wrong during the downgrade. If the IOS image in the flash: filesystem has not been corrupt, we might be looking at a hardware problem.

One thing - I faintly recall that in another thread here on CSC, another user reported a problem with 12.2(55)SE12 that was similar to yours. What I would suggest is to try to go back and try 12.2(55)SE10 or 12.2(55)SE9 to see if any of them boots. To do this, I am afraid, you will need to erase the flash: filesystem and transfer the IOS image through the console port and XModem which will take hours. The general procedure is described in this document:

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-2950-series-switches/41845-192.html

Once again, however, it would be best to see the console logs and not jump to conclusions. Any attempt to recover the switch will require you to access its console, anyway.

Best regards,
Peter

View solution in original post

15 Replies 15

Leo Laohoo
Hall of Fame
Hall of Fame

@Aida Hadad wrote:

Based on Cisco recommendation I wanted to change it to version 12.2(55)SE12 but during boot up it fails .


Console into the switch and reboot.  We want to see what is going on.

hi
As I said it get in to problem during boot up as passed all of post procedures successfully.
I am working in alive network with lots of staff and I couldn't do it right now. but in this weekend I should upgrade it any way cause my boss told me so.
I just wanted to know any possibility causes about situation which I mentioned above.
It must to mentioned that I couldn't simulate it so.
Many thanks for your reply

Deepak Kumar
VIP Alumni
VIP Alumni

HI,

Please share the console logs.

 

Regards,

Deepak Kumar

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

As I said to our other Cisco friend, I don have logs and also couldn't reboot switch in live network right now.

Also as I mentioned it passed all POST procedures after booting up successfully and after that it gets to problem.

I just want any possibilities of this changing from V15 to V12...Any troubleshoots regarding that might be help full.

Please give me reply other than sending logs or rebooting to see what will happen.

Many thanks for your considerations.


@Aida Hadad wrote:

I've just started working in company which I should upgrade Switch IOSs based on Cisco website recommendations.


Right.  I know what happened.  So you are new to this world of Cisco stuff. 


@Aida Hadad wrote:

 


Unwilling to provide logs other than "trust me".  


@Aida Hadad wrote:

Also as I mentioned it passed all POST procedures after booting up successfully and after that it gets to problem.


So the switch boot up fine, albeit running the same IOS instead of downgrade.

Which leads me to this question:  Exactly HOW did you perform an upgrade.  

If done right, the script would've told you if things went wrong.  But it didn't.  So this means the upgrade was done using a very archaic and dangerous method (for those who don't know what they're doing) of copying the BIN file from one machine to another.  Now if this BIN file was corrupt, there is no chance the appliance is going to boot this IOS.  

Or the IOS could be pulled from a completely different appliance and copied across without any verification.

Hi 

Of-course before copying .bin file you must check hashing and size of that file on your system to be match with the one in Cisco site.

Then after copying that to flash you can see the exact size just with show flash.

So it can't be corrupted with those easy verification.

 

A-ha. We're getting somewhere.
So the upgrade was just copying the BIN file across.
Show us the boot-up process.
Post the complete output to the command "dir".

Peter Paluch
Cisco Employee
Cisco Employee

Hello Aida,

As mentioned by other colleagues here already, we unfortunately depend on seeing the complete and accurate console logs from that switch. The general fact is that on a Catalyst 2960 platform, you can freely upgrade and downgrade between any arbitrary IOS versions. Since your switch behaves differently, we need hard evidence to understand what is going on. We may speculate but neither of the hypotheses will be actually useful if not paired with correct symptoms.

By the way, there is not much you could have done wrong during the downgrade. If the IOS image in the flash: filesystem has not been corrupt, we might be looking at a hardware problem.

One thing - I faintly recall that in another thread here on CSC, another user reported a problem with 12.2(55)SE12 that was similar to yours. What I would suggest is to try to go back and try 12.2(55)SE10 or 12.2(55)SE9 to see if any of them boots. To do this, I am afraid, you will need to erase the flash: filesystem and transfer the IOS image through the console port and XModem which will take hours. The general procedure is described in this document:

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-2950-series-switches/41845-192.html

Once again, however, it would be best to see the console logs and not jump to conclusions. Any attempt to recover the switch will require you to access its console, anyway.

Best regards,
Peter

Many thanks for your attention and complete reply :)

unfortunately it didn't solved!!!

 

 

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

 

Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(55)SE10, RE LEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Wed 11-Feb-15 11:46 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01900000

Initializing flashfs...

fsck: Disable shadow buffering due to heap fragmentation.
flashfs[1]: 564 files, 20 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 32514048
flashfs[1]: Bytes used: 27646976
flashfs[1]: Bytes available: 4867072
flashfs[1]: flashfs fsck took 2 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.

Checking for Bootloader upgrade.. not needed
POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed

POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed

POST: CPU MIC interface Loopback Tests : Begin
POST: CPU MIC interface Loopback Tests : End, Status Passed

POST: PortASIC RingLoopback Tests : Begin
POST: PortASIC RingLoopback Tests : End, Status Passed

POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed

POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed

Waiting for Port download...Complete


This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

 

00:00:32 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 300, PC = 14B22C C
-Traceback= 14B22CC FAC4B0 FAD678 FADD9C 13BE4D8 1410D6C 14B7730 14B77C8 FB935C FB9590 1535030 152B804

Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_9

=== Flushing messages (00:00:35 UTC Mon Mar 1 1993) ===

Buffered messages:
Queued messages:
*Mar 1 00:00:35.374: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console d ebugging output.

*Mar 1 00:00:31.381: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, cha nged state to down
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(55)SE10, RE LEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Wed 11-Feb-15 11:46 by prod_rel_team

Data Access Exception (0x0300)!
SRR0 = 0x014B22CC SRR1 = 0x00029230 SRR2 = 0x006D05B4 SRR3 = 0x00029230
ESR = 0x00800000 DEAR = 0x00000062 TSR = 0x84000000 DBSR = 0x00000000

CPU Register Context:
Vector = 0x00000300 PC = 0x014B22CC MSR = 0x00029230 CR = 0x99000033
LR = 0x00FAC4B0 CTR = 0x014B94D4 XER = 0xC0000024
R0 = 0x00007F90 R1 = 0x0271E3A0 R2 = 0x00000000 R3 = 0x0000005E
R4 = 0x40000316 R5 = 0x00000000 R6 = 0x00000000 R7 = 0x00000000
R8 = 0x00007C7A R9 = 0x023DEE68 R10 = 0x00007F90 R11 = 0x02030000
R12 = 0xC0007C7A R13 = 0x00110000 R14 = 0x00FB9530 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x0271E430
R20 = 0x00000000 R21 = 0x00000001 R22 = 0x00000000 R23 = 0x00FADD98
R24 = 0x00000000 R25 = 0x0202C040 R26 = 0x00000002 R27 = 0x00000000
R28 = 0x01A5A340 R29 = 0x01A5A340 R30 = 0x0000005E R31 = 0x00000056

Stack trace:
PC = 0x014B22CC, SP = 0x0271E3A0
Frame 00: SP = 0x0271E408 PC = 0x00000000
Frame 01: SP = 0x0271E4A0 PC = 0x00FAD678
Frame 02: SP = 0x0271E528 PC = 0x00FADD9C
Frame 03: SP = 0x0271E550 PC = 0x013BE4D8
Frame 04: SP = 0x0271E598 PC = 0x01410D6C
Frame 05: SP = 0x0271E5A0 PC = 0x014B7730
Frame 06: SP = 0x0271E5B8 PC = 0x014B77C8
Frame 07: SP = 0x0271E5D8 PC = 0x00FB935C
Frame 08: SP = 0x0271E6E0 PC = 0x00FB9590
Frame 09: SP = 0x0271E6E8 PC = 0x01535030
Frame 10: SP = 0x00000000 PC = 0x0152B804


Switch uptime is 37 seconds

cisco WS-C2960-24TT-L (PowerPC405) processor (revision D0) with 65536K bytes of memory.
Processor board ID FCQ1525Y2S3

ijiz,x. . l[[[[[[[[[[[[]

The appliance is crashing.
May I recommend loading a different version. 12.2(55)SE12, perhaps?

I tried that one too before and it had the same log as abow

RMA the appliance. Something doesn't add up.

I found 9 crash info in that switch but I think some of them are from the past.

all of them are same as each other and the time goes to 1993!!!!!

I think some one in past wanted to upgrade it and face to this problem too.


*Mar 1 00:00:31.390: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down

=== Start of Crashinfo Collection (00:00:32 UTC Mon Mar 1 1993) ===

For image:
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(55)SE10, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Wed 11-Feb-15 11:46 by prod_rel_team

 

========= Show Alignment ============================


No alignment data has been recorded.

No spurious memory references have been recorded.

Review Cisco Networking for a $25 gift card