<?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 5510 Active/stdby upgrade query (8.2-&amp;gt;9.1) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798227#M175233</link>
    <description>&lt;P&gt;Hello experts,&lt;/P&gt;
&lt;P&gt;Planning to upgrade Active/stdby pair from 8.2.x-&amp;gt;8.4.6-&amp;gt;9.1.10. ASAs got reqd memory. Also, the config got only couple of 'nonat' statements and related VPN configs.&lt;/P&gt;
&lt;P&gt;Can I upgrade pair to 8.4.6 first (standard method) and once all looks good then goto 9.1.10? Any manual config intervention required?&lt;/P&gt;
&lt;P&gt;Or I need to break the pair and do one after the other with necessary config changes?&lt;/P&gt;
&lt;P&gt;Configuration conversion worked fine on singe test ASA.&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;
&lt;P&gt;MS&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 06:50:28 GMT</pubDate>
    <dc:creator>mvsheik123</dc:creator>
    <dc:date>2019-03-12T06:50:28Z</dc:date>
    <item>
      <title>5510 Active/stdby upgrade query (8.2-&gt;9.1)</title>
      <link>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798227#M175233</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;
&lt;P&gt;Planning to upgrade Active/stdby pair from 8.2.x-&amp;gt;8.4.6-&amp;gt;9.1.10. ASAs got reqd memory. Also, the config got only couple of 'nonat' statements and related VPN configs.&lt;/P&gt;
&lt;P&gt;Can I upgrade pair to 8.4.6 first (standard method) and once all looks good then goto 9.1.10? Any manual config intervention required?&lt;/P&gt;
&lt;P&gt;Or I need to break the pair and do one after the other with necessary config changes?&lt;/P&gt;
&lt;P&gt;Configuration conversion worked fine on singe test ASA.&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;
&lt;P&gt;MS&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:50:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798227#M175233</guid>
      <dc:creator>mvsheik123</dc:creator>
      <dc:date>2019-03-12T06:50:28Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798228#M175235</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Since configuration conversion was fine on a test ASA you should not face any issue with upgrading the failover setup. You can follow the standard upgrade path.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;hope this helps.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Shivapramod M&lt;/P&gt;</description>
      <pubDate>Fri, 06 Nov 2015 04:49:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798228#M175235</guid>
      <dc:creator>Shivapramod M</dc:creator>
      <dc:date>2015-11-06T04:49:12Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798229#M175238</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Following are the steps which are suggested for an upgrade which involves migration&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;++ Issue command&lt;/P&gt;
&lt;P&gt;#no names&lt;/P&gt;
&lt;P&gt;++ Issue command&lt;/P&gt;
&lt;P&gt;#no nat-control&lt;/P&gt;
&lt;P&gt;++ If there is any NAT exempt statement constructed using ACL, then make sure that there&lt;/P&gt;
&lt;P&gt;is no ACL with source and destination IP as "any".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case there is any such ACL then remove that ACL before migration and add it after&lt;/P&gt;
&lt;P&gt;migrating to new ASA version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;gt;&amp;gt; Above mentioned steps are required prior to an upgrade.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For more details you can refer:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa83/upgrading/migrating.html#wp77266"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa83/upgrading/migrating.html#wp77266&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;R.Seth&lt;/P&gt;</description>
      <pubDate>Fri, 06 Nov 2015 04:58:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/5510-active-stdby-upgrade-query-8-2-gt-9-1/m-p/2798229#M175238</guid>
      <dc:creator>Rishabh Seth</dc:creator>
      <dc:date>2015-11-06T04:58:58Z</dc:date>
    </item>
  </channel>
</rss>

