<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Change which image is booted on an ASA5510 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/4055780#M1068446</link>
    <description>&lt;P&gt;Hi Marvin,&lt;/P&gt;&lt;P&gt;One quick question.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's say we boot 2 images on the boot system like the following&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vpnb# sh run boot&lt;BR /&gt;boot system disk0:/asa943-smp-k8.bin&lt;BR /&gt;boot system disk0:/asa941-smp-k8.bin&lt;BR /&gt;vpnb#&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Mar 2020 09:17:29 GMT</pubDate>
    <dc:creator>kasunrajapakse</dc:creator>
    <dc:date>2020-03-31T09:17:29Z</dc:date>
    <item>
      <title>Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630109#M559462</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I am wondering how to change which image is loaded by default on an ASA5510.&amp;nbsp; I have two image files stored in the flash memory on disk0:/ but need to change which one is loaded on boot.&amp;nbsp; 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.&amp;nbsp; Is there a command to change the order that is used?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:09:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630109#M559462</guid>
      <dc:creator>pgregg</dc:creator>
      <dc:date>2019-03-11T20:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630110#M559464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you run "sh run boot", it will show you all the boot system configuration, and it will be loaded from top to bottom.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Mar 2011 21:24:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630110#M559464</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-03-19T21:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630111#M559466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That did help, thanks for the response.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Mar 2011 22:51:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/1630111#M559466</guid>
      <dc:creator>pgregg</dc:creator>
      <dc:date>2011-03-19T22:51:34Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857410#M559468</link>
      <description>&lt;P&gt;To clarify, remove old or unnecessary system image with the negeting command "no boot system"...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Show run boot&lt;/P&gt;&lt;P&gt;boot system disk0:/asa915-k8.bin&lt;BR /&gt;boot system disk0:/asa982-lfbff-k8.SPA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(config)# no boot system disk0:/asa915-k8.bin&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Show run boot&lt;/P&gt;&lt;P&gt;boot system disk0:/asa982-lfbff-k8.SPA&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 11:40:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857410#M559468</guid>
      <dc:creator>jgustafzon</dc:creator>
      <dc:date>2019-05-16T11:40:03Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857447#M559471</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/10419"&gt;@jgustafzon&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While the logica for removing an old image is correct, your example mixes an older non-digitally signed image (&lt;SPAN&gt;asa915-k8.bin&lt;/SPAN&gt;) with a new one (&lt;SPAN&gt;asa982-lfbff-k8.SPA&lt;/SPAN&gt;).&lt;/P&gt;
&lt;P&gt;A given ASA will only run one type or the other - you never mix them on the same system.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 12:15:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857447#M559471</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-05-16T12:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857459#M559473</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;Sure, but this is from a real &lt;SPAN&gt;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.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 12:20:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/3857459#M559473</guid>
      <dc:creator>jgustafzon</dc:creator>
      <dc:date>2019-05-16T12:20:17Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/4055780#M1068446</link>
      <description>&lt;P&gt;Hi Marvin,&lt;/P&gt;&lt;P&gt;One quick question.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's say we boot 2 images on the boot system like the following&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vpnb# sh run boot&lt;BR /&gt;boot system disk0:/asa943-smp-k8.bin&lt;BR /&gt;boot system disk0:/asa941-smp-k8.bin&lt;BR /&gt;vpnb#&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 09:17:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/4055780#M1068446</guid>
      <dc:creator>kasunrajapakse</dc:creator>
      <dc:date>2020-03-31T09:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: Change which image is booted on an ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/4055845#M1068455</link>
      <description>&lt;P&gt;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.)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/c4.html#40125" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/A-H/cmdref1/c4.html#40125&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2020 11:35:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-which-image-is-booted-on-an-asa5510/m-p/4055845#M1068455</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-03-31T11:35:50Z</dc:date>
    </item>
  </channel>
</rss>

