cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
16804
Views
15
Helpful
7
Replies

Change which image is booted on an ASA5510

pgregg
Level 1
Level 1

Hello,

  I am wondering how to change which image is loaded by default on an ASA5510.  I have two image files stored in the flash memory on disk0:/ but need to change which one is loaded on boot.  I used the command "boot system disk0:/asa722-12-k8.bin" which completed successfully, but when the system starts it says two images exist and the default is 1, loading the previous file.  Is there a command to change the order that is used?

1 Accepted Solution

Accepted Solutions

Jennifer Halim
Cisco Employee
Cisco Employee

If you run "sh run boot", it will show you all the boot system configuration, and it will be loaded from top to bottom.

If your newer image is at the bottom, just remove the old boot system line, and if you run "sh run boot", you will only see 1 line referring to the new image.

If you want to be sure and have 2 images, just re-enter the old image, and it will show up on the second line.

Basically the new line entered for boot system will be entered as the last line, so if you remove the existing one and reenter it after you enter the new image, you will have the new image at the top.

Hope this helps.

View solution in original post

7 Replies 7

Jennifer Halim
Cisco Employee
Cisco Employee

If you run "sh run boot", it will show you all the boot system configuration, and it will be loaded from top to bottom.

If your newer image is at the bottom, just remove the old boot system line, and if you run "sh run boot", you will only see 1 line referring to the new image.

If you want to be sure and have 2 images, just re-enter the old image, and it will show up on the second line.

Basically the new line entered for boot system will be entered as the last line, so if you remove the existing one and reenter it after you enter the new image, you will have the new image at the top.

Hope this helps.

That did help, thanks for the response.

To clarify, remove old or unnecessary system image with the negeting command "no boot system"...

 

Show run boot

boot system disk0:/asa915-k8.bin
boot system disk0:/asa982-lfbff-k8.SPA

 

(config)# no boot system disk0:/asa915-k8.bin

 

Show run boot

boot system disk0:/asa982-lfbff-k8.SPA

@jgustafzon 

While the logica for removing an old image is correct, your example mixes an older non-digitally signed image (asa915-k8.bin) with a new one (asa982-lfbff-k8.SPA).

A given ASA will only run one type or the other - you never mix them on the same system. 

@Marvin Rhoads Sure, but this is from a real scenario where I restored configuration from an old ASA 5510 (Obselete) to a newer X-series ASA with firepower services. The old configuration also contains old system images that needs removal. 

Hi Marvin,

One quick question. 

 

Let's say we boot 2 images on the boot system like the following

 

vpnb# sh run boot
boot system disk0:/asa943-smp-k8.bin
boot system disk0:/asa941-smp-k8.bin
vpnb#

 

If the first image fails/or if it's corrupted while booting the device, will the ASA router pick the second image and boot correctly?

 

Thanks

 

That's generally correct - except the image has to be unavailable. A present but corrupted available image will try and fail to boot. (Uunless you have changed the default config-register to not follow the order of images specified in the startup-config.)

https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/c4.html#40125

Review Cisco Networking for a $25 gift card