cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2835
Views
0
Helpful
5
Replies

sge2010p software upgrade problem - switch always boots with old firmware

krzysztofsyguda
Level 1
Level 1

I have just downloaded new software for sge2010p. I had tried to made an upgrade on some switches, but switches still boot with the old software.

I have installed software 3.0.0.18 and boot  2.0.0.03. I have downloaded software 3.0.1 from cisco, put it on tftp and started an upgrade via switch web interface.  I have checked that the active image is set to 1, and started the upgrade.

Switch has downloaded soft from tftp, and reported that process has been finished without errors.

After the restart switch have 3.0.0.18 software again. 

I have try to do this same on 4 different switches working in L3 and L2 mode - always with the same effect.

Should I upgrade  both images in the same time to get this work?

I have noticed, that the new firmware is located on image 2.

# show bootvar

Image  Filename   Version     Date                    Status

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

1      image-1    3.0.0.18    08-Nov-2009  16:21:37   Active

2      image-2    3.0.1.0     19-May-2011  13:05:53   Not active*

"*" designates that the image was selected for the next boot

and I try to change the active imaga via www interface

Unit No.  Active Image After Reset

1               Image 1          Image2

..but 

# show bootvar

Image  Filename   Version     Date                    Status

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

1      image-1    3.0.0.18    08-Nov-2009  16:21:37   Active

2      image-2    3.0.1.0     19-May-2011  13:05:53   Not active*

"*" designates that the image was selected for the next boot

so I try to set active image via console command:

# boot system image-2

and again...

a# show bootvar

Image  Filename   Version     Date                    Status

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

1      image-1    3.0.0.18    08-Nov-2009  16:21:37   Active*

2      image-2    3.0.1.0     19-May-2011  13:05:53   Not active

"*" designates that the image was selected for the next boot

...finally i have tried to set the active image to "2" using console menu:

I have set it like this:

                                 Active Image

                                 ============

Unit ID                 Active Image            Active Image after Reset

=======                 ============            ========================

1                       Image 1                 Image 2

and save..

but...

# show bootvar

Image  Filename   Version     Date                    Status

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

1      image-1    3.0.0.18    08-Nov-2009  16:21:37   Active

2      image-2    3.0.1.0     19-May-2011  13:05:53   Not active*

"*" designates that the image was selected for the next boot

#$!$#!@!$!#$@!#@#

Could somebody please explain me what am I doing wrong or what is wrong with this #@!! switch?

Why is it so inconsistence between web gui, console menu and command line?

I have noticed that some settings are not stored using copy running to startup command from the web gui (I have to use cli to store the settings)

Where is the right place to set active image for 2.

Is the "active image" settings only sets the firmware image which switch uses  or configuration files too?

5 Replies 5

David Hornstein
Level 7
Level 7

Hi Krzysztof,

The 3.0.1.0 release notes, referenced  on the download page at URL says;

http://www.cisco.com/en/US/docs/switches/lan/csbms/sfe2000/release/notes/SxE20x0_3.0.1.0.pdf

• If a new firmware image is loaded on image 2, a reboot will set image 1 as

the active image. (CSCtq62385)

- Workaround: Install the firmware onto active image 1

I think there is the answer, the CSCtq62385 indicates that a bug report has gone in to fix this issue. .

regards Dave

Hi ;

I have been read this release note. But after upgrade (Image 1 sets as active) firmwale loads on image 2, after reboot active image is image 1. I try to load image again (as described - Workaround: Install the firmware onto active image 1)

but it  is installed  on image 2 again. So is this any way to install it on image active 1 as described in the relese notes?


Hi Krzysztof,

I tried this myself and came across the same error, your spot on with your assessment of the situation..

I'm was a wee bit confused by the release note, so I rang the  wonderful folks at the Small Business Support Center and  opened a case.

They set me straight   and closed the case within half an hour of me opening the case.

Though I had done what you did via the GUI, but had the same problem.

Krzysztof,  as you have already stated, to ensure there is always one good image, the firmware always download to the location of the non-active image.

Seems to be it works when i call SBSC. I downloaded the firmware and it loaded it into image 2 area as image 1 was active.

I then selected image 2 to be the  active image after the reboot and then  rebooted my switch.

This is what I saw after the reboot.;

So it worked, but then loaded again the firmware, which would then download the firmware into the inactive amage area 1.

Felt a bit foolish for opening a case for something that seemed to simple, as it seemed to work after i called SBSC,  but have the hide as thick as a Rhino    and SBSC are there to help.

regards Dave

Hi Dave;

Thank you for your support.

I have finally upgrade the switches, but i still don't know why the switch shows different botvar status in webgui and the cli and which settings has the higher priority.

E.g. I see the active image  2 in web gui, but the cli shows active image 1 untill it is changed  from the cli directly.

regards

KS

matmcfad
Level 1
Level 1

To be clear for any others that may be experiencing this problem. The problem is that if you load the new firmware onto image 2, your switch may occasionaly reboot into image 1 even if it appears you have it set to do otherwise. In order to work around this issue, you should install the new firmware onto image 1. The switch allways installs the new firmware onto the image you are current NOT on.

Here is step by step how to work around this current issue.

1. On the GUI or CLI set the active image after reboot to be image 2, then reboot

2. Confirm you are on active image 2.

3. Upload the new firmware, THIS WILL INSTALL THE FIRMWARE ON IMAGE 1

4. Set the active image after reboot to be image 1, reboot.