<?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 Problem Upgrade ASA5520 v8.2.5 to v9.0.3 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326749#M342489</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I feel that the major change in the IOS was from 8.3(1) so i think you should upgrade from 8.2--&amp;gt;8.3(1) --&amp;gt; 8.3(2)--&amp;gt; 9.0&lt;/P&gt;&lt;P&gt;Directly upgrading to 8.4 might give some bugs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;about your problem kindly elaborate on this, what issue exactly are you facing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pankaj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Sep 2013 07:31:00 GMT</pubDate>
    <dc:creator>pankaj29in</dc:creator>
    <dc:date>2013-09-26T07:31:00Z</dc:date>
    <item>
      <title>Problem Upgrade ASA5520 v8.2.5 to v9.0.3</title>
      <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326746#M342486</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We tried to upgrade our cluster Asa5520 version 9.0.3 last night!&lt;/P&gt;&lt;P&gt;Today, the flow dysfunctions for, and we had an error in the GUI (Ressource Connect limit)&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/5/7/1/158175-Sans%20titre.JPG" alt="Sans titre.JPG" class="jive-image-thumbnail jive-image" onclick="" width="450" /&gt;&lt;/P&gt;&lt;P&gt;why have we got this error, hardware it's ok for version 9 ? :&lt;/P&gt;&lt;P&gt;Hardware:&amp;nbsp;&amp;nbsp; ASA5520, 2048 MB RAM, CPU Pentium 4 Celeron 2000 MHz,&lt;/P&gt;&lt;P&gt;Internal ATA Compact Flash, 256MB&lt;/P&gt;&lt;P&gt;BIOS Flash M50FW080 @ 0xfff00000, 1024KB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A downgrade emergency had to be made.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone could help me on this problem,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:43:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326746#M342486</guid>
      <dc:creator>lbellicaud</dc:creator>
      <dc:date>2019-03-12T02:43:44Z</dc:date>
    </item>
    <item>
      <title>Re:Problem Upgrade ASA5520 v8.2.5 to v9.0.3</title>
      <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326747#M342487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you please post more specific of the problem?&lt;BR /&gt;&lt;BR /&gt;Also, I believe the correct upgrade path is 8.2.5 -&amp;gt; 8.4 -&amp;gt; 9.x.&lt;BR /&gt;&lt;BR /&gt;Please try upgrading first to 8.4 and see if you have any problems. If not, then try upgrading to 9.x.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Mike&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 05:17:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326747#M342487</guid>
      <dc:creator>Mike Williams</dc:creator>
      <dc:date>2013-09-26T05:17:43Z</dc:date>
    </item>
    <item>
      <title>Problem Upgrade ASA5520 v8.2.5 to v9.0.3</title>
      <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326748#M342488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mike,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my customer upgrade cluster 8.2.5 --&amp;gt; 9.x it's same problem, they had ressource limit after 6 hours.&lt;/P&gt;&lt;P&gt;Me i upgrade cluster to 8.2.5 --&amp;gt; 8.4.7 --&amp;gt; 9.0.3 it's same problem &lt;SPAN style="font-size: 10pt;"&gt;they had ressource limit after 4 hour.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I have a show tech when my customer had this problem,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 05:33:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326748#M342488</guid>
      <dc:creator>lbellicaud</dc:creator>
      <dc:date>2013-09-26T05:33:59Z</dc:date>
    </item>
    <item>
      <title>Problem Upgrade ASA5520 v8.2.5 to v9.0.3</title>
      <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326749#M342489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I feel that the major change in the IOS was from 8.3(1) so i think you should upgrade from 8.2--&amp;gt;8.3(1) --&amp;gt; 8.3(2)--&amp;gt; 9.0&lt;/P&gt;&lt;P&gt;Directly upgrading to 8.4 might give some bugs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;about your problem kindly elaborate on this, what issue exactly are you facing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pankaj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 07:31:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326749#M342489</guid>
      <dc:creator>pankaj29in</dc:creator>
      <dc:date>2013-09-26T07:31:00Z</dc:date>
    </item>
    <item>
      <title>Problem Upgrade ASA5520 v8.2.5 to v9.0.3</title>
      <link>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326750#M342490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the problem is a loss of packets and problems of delays on the network that the problem appears:&lt;/P&gt;&lt;P&gt;Here "show conn":&lt;/P&gt;&lt;P&gt;fw-intranet# show conn&lt;/P&gt;&lt;P&gt;19765 in use, 32645 most used&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:00:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:00:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:1096 inside UCM2:0, idle 0:00:51, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:1097 inside UCM2:0, idle 0:00:58, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:02:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:02:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:04:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:04:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:06:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:06:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:08:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:08:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:10:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:10:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:12:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:12:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:14:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:14:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:16:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:16:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:18:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:18:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:20:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:20:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;&amp;lt;--- More ---&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:22:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:22:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:24:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:24:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:26:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:26:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:28:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:28:44, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;UDP pvives 172.28.61.242:5741 inside 172.20.1.174:64707, idle 0:01:56, bytes 92, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.28.63.240:5741 inside 172.20.1.174:64700, idle 0:01:57, bytes 110, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:58691, idle 0:00:00, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:41753, idle 0:00:05, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:37396, idle 0:00:10, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:37337, idle 0:00:16, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:47803, idle 0:00:21, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:00:23, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:44352, idle 0:00:26, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:35562, idle 0:00:32, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:58474, idle 0:00:37, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:42020, idle 0:00:42, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:57635, idle 0:00:48, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:48088, idle 0:00:53, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:41501, idle 0:00:59, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:47136, idle 0:01:04, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;&amp;lt;--- More ---&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:51395, idle 0:01:09, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:34541, idle 0:01:15, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:54197, idle 0:01:20, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:43172, idle 0:01:25, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:52176, idle 0:01:31, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:40809, idle 0:01:36, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:1073 inside UCM2:0, idle 0:01:37, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:45621, idle 0:01:41, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:57593, idle 0:01:47, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:50029, idle 0:01:52, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;UDP pvives 172.27.63.44:1049 inside UCM1:46190, idle 0:01:57, bytes 8529, flags -&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:02:23, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:04:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:06:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:08:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:10:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:12:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:14:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:16:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:18:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:20:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:22:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:24:24, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:26:25, bytes 0, flags Ti&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;,&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 09:03:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-upgrade-asa5520-v8-2-5-to-v9-0-3/m-p/2326750#M342490</guid>
      <dc:creator>lbellicaud</dc:creator>
      <dc:date>2013-09-26T09:03:55Z</dc:date>
    </item>
  </channel>
</rss>

