<?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: ASAv boot image in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4088784#M1070342</link>
    <description>&lt;P&gt;When you build an ASAv initially the boot image is embedded in the OVA's VMDK file.&lt;/P&gt;
&lt;P&gt;You can subsequently upgrade the usual way - copy a new boot image to disk and set it using the cli or ASDM. (or extra points for CDO)&lt;/P&gt;</description>
    <pubDate>Tue, 19 May 2020 16:32:30 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2020-05-19T16:32:30Z</dc:date>
    <item>
      <title>ASAv boot image</title>
      <link>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4088566#M1070338</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came across today two ASAv that I want to upgrade.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I observed through ASDM that there is no boot image.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you know why is that? Is it normal?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Konstantinos&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2020 11:04:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4088566#M1070338</guid>
      <dc:creator>kostasthedelegate</dc:creator>
      <dc:date>2020-05-19T11:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv boot image</title>
      <link>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4088784#M1070342</link>
      <description>&lt;P&gt;When you build an ASAv initially the boot image is embedded in the OVA's VMDK file.&lt;/P&gt;
&lt;P&gt;You can subsequently upgrade the usual way - copy a new boot image to disk and set it using the cli or ASDM. (or extra points for CDO)&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2020 16:32:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4088784#M1070342</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-05-19T16:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv boot image</title>
      <link>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4308086#M1079337</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; we uploaded ASav to the new image, and now we must roll back the old one but we can't find old image.&lt;/P&gt;&lt;P&gt;If we delete the new image from ASAv, does it will boot again via embedded image?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Mar 2021 12:07:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4308086#M1079337</guid>
      <dc:creator>Jahangir Tahirov</dc:creator>
      <dc:date>2021-03-16T12:07:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv boot image</title>
      <link>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4308694#M1079358</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/411240"&gt;@Jahangir Tahirov&lt;/a&gt; I'm not sure if the method you ask about would work. I personally would recommend you copy the old image .bin file onto the ASAv and specify that in the boot variable. Save and then reload.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Mar 2021 07:00:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-boot-image/m-p/4308694#M1079358</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-03-17T07:00:53Z</dc:date>
    </item>
  </channel>
</rss>

