cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2435
Views
0
Helpful
10
Replies

Boot system not effective on 2940s ?

tommyboay
Level 1
Level 1

Hi everyone,

I have a bunch of 2940s I wanted to upgrade along with 2950s. Exact model is WS-C2940-8TT-S.

After copying new IOS to flash, I used the boot system marker to make sure the right version would be chosen on next boot.

show boot shown the following statement :

agfr01swtadp01#show boot
BOOT path-list:       c2940-i6k2l2q4-mz.121-22.EA14.bin
Config file:          flash:/config.text
Private Config file:  flash:/private-config.text
Enable Break:         no
Manual Boot:          no

I used the "reload in xx" command to schedule upgrade but the switch somehow rebooted to the old IOS version.

Is there any better way to make sure the switch will boot on specific IOS version when several exist on flash ?

Thanks,

Tom

1 Accepted Solution

Accepted Solutions

     I think it would be pretty safe to get rid of the image you don't need on these.  Both these models are end of life and you can assume the code is pretty stable .

View solution in original post

10 Replies 10

Latchum Naidu
VIP Alumni
VIP Alumni

Hi Thomas,

The 2950/2955 automatically searches for a valid software image to boot from, even if a boot system statement is not set. Cisco recommends that you set the boot statement as a precaution. The command to set a boot system statement is boot system flash: .


After you copied the new file to flash issue the below command...


#boot system flash:c2950-i6q4l2-mz.121-13.EA1.bin

!--- The boot system statement does not show up in the configuration.
!--- Issue the show boot command to verify whether the new image
!--- boots on the next reload of the switch.

Now issue the wr mem command to save your changes and reload the switch.


Please rate if this helps you...


Regards,
Naidu.

Hi Naidu,

Thanks for the answer.

Unfortunately, this is exactly what I did otherwise, I wouldn't have the show boot statement providing latest IOS version.

For now, my only choice is to delete other IOS versions from flash before scheduling reload.

I also noticed that the boot system statement does not show in running config here.

I'm still unsure why it reloaded on oldest version.

Tom

Hi Thomas,

I have a doubt that is your flash capable to store both new and old ios images?

I dont think that 2950 can store both ios at same time as the flash is not enough free.

Try to remove old IOS and upload new ios then give booth statement and write mem and then reload...

Also follow the below link for more details:

http://www.cisco.com/en/US/products/hw/switches/ps628/products_configuration_example09186a0080169627.shtml

Now it should boot with new IOS.

Regards,

Naidu.

Thanks Naidu.

This was the document I used to prepare and proceed with upgrade. The flash is 8MB large and enough for two IOS versions with no Web GUI. I do not consider erasing all but the new IOS from flash to be a solution. It would rather be a workaround. I have more upgrades planned on 2940/2950 switches so I'll try to reproduce the issue.

What is the config register set to on the switch? I was recently surprised in upgrading a Catalyst switch which did not follow the boot system commands that I had configured. It turns out the switch config register instructed the switch to rom boot and to use the first image that it found. I wonder if this could be what you are running into?

HTH

Rick

HTH

Rick

Leo Laohoo
Hall of Fame
Hall of Fame

Can you please post the output for the following:

1.  dir

2.  sh version

glen.grant
VIP Alumni
VIP Alumni

  If it originally had a boot statement then unless you deleted that boot statement it will load the old IOS because that is the first image in the config boot statement order.  Check to 2 see if there is 2 boot statements in the config .  Do  a show boot or show bootvar to see what is configured.  If its loading the old image even with a new boot statement then the config register is set to look for the first image in flash and the boot statement will make no difference. You would have to change the config register to follow the boot statement.

Thanks you all for your help & comments !

From the upgrade reference guide for 2950, these low end models do not have any config-register :

"Unlike other Catalyst switches, there is no config-register command on the 2950 or 2955. You cannot change the configuration register value from the default."

The 2940 seems to share this spec : There is no available command to change the register value. Also note the last line on show ver (taken after IOS upgrade) :

agde04swt07#show ver
Cisco Internetwork Operating System Software
IOS (tm) C2940 Software (C2940-I6K2L2Q4-M), Version 12.1(22)EA14, RELEASE SOFTWARE (fc1)
Technical Support:
http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by cisco Systems, Inc.
Compiled Tue 26-Oct-10 10:17 by nburra
Image text-base: 0x80010000, data-base: 0x8068C000

ROM: Bootstrap program is C2950 boot loader

agde04swt07 uptime is 12 hours, 55 minutes
System returned to ROM by power-on
System restarted at 19:25:44 UTC Mon Jan 24 2011
System image file is "flash:c2940-i6k2l2q4-mz.121-22.EA14.bin"


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 you require further assistance please contact us by sending email to
export@cisco.com. WS-C2940-8TT-S (RC32300) processor (revision D0) with 19867K bytes of memory.
Processor board ID FHK0852W0HS
Last reset from system-reset
Running Standard Image
8 FastEthernet/IEEE 802.3 interface(s)
1 Gigabit Ethernet/IEEE 802.3 interface(s)
The password-recovery mechanism is enabled.

If

cisco

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:12:D9:F6:49:00
Motherboard assembly number: 73-8784-05
Power supply part number: 341-0085-01
Motherboard serial number: FOC085231Z4
Power supply serial number: HIC084303DD
Model revision number: D0
Motherboard revision number: A0
Model number: WS-C2940-8TT-S
System serial number: FHK0852W0HS
Configuration register is 0xF

I was not able to reproduce the issue. The one I did 12 hours ago had both images and what I believe to be the right boot config. See below :

agde04swt07#dir
Directory of flash:/

    2  -rwx     3757537  May 28 2009 15:18:33 +00:00  c2940-i6k2l2q4-mz.121-22.EA12.bin
    3  -rwx     3758409  Jan 24 2011 17:02:00 +00:00  c2940-i6k2l2q4-mz.121-22.EA14.bin
    5  -rwx        5510  Jan 24 2011 17:02:46 +00:00  config.text
    6  -rwx        1344  Apr 22 2010 08:14:04 +00:00  vlan.dat
    7  -rwx        1048  Jan 24 2011 17:02:48 +00:00  multiple-fs
    8  -rwx        1957  Jan 24 2011 17:02:48 +00:00  private-config.text

7612416 bytes total (84480 bytes free)

agde04swt07#show boot
BOOT path-list:       flash:c2940-i6k2l2q4-mz.121-22.EA14.bin
Config file:          flash:/config.text
Private Config file:  flash:/private-config.text
Enable Break:         no
Manual Boot:          no
HELPER path-list:
NVRAM/Config file
      buffer size:    32768
Timeout for Config
          Download:    0 seconds
Config Download
       via DHCP:       disabled (next boot: disabled)

I'll be testing upgrade on other 2940s and will post the result here : If none reproduces the issue, I was probably doing something wrong the 1st time.

     I think it would be pretty safe to get rid of the image you don't need on these.  Both these models are end of life and you can assume the code is pretty stable .

You're right. I finished my upgrades by cleaning all existing IOS versions on the flash before planning reboot. These devices may not be meant to store more than one IOS image at once.

Thanks to every one of you that took time to help in this thread.