Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
882
Views
0
Helpful
4
Replies

Problem Upgrade ASA5520 v8.2.5 to v9.0.3

lbellicaud
Level 1
Level 1

‎09-25-2013 05:18 PM - edited ‎03-11-2019 07:43 PM

Hello all,

We tried to upgrade our cluster Asa5520 version 9.0.3 last night!

Today, the flow dysfunctions for, and we had an error in the GUI (Ressource Connect limit)

Sans titre.JPG

why have we got this error, hardware it's ok for version 9 ? :

Hardware:   ASA5520, 2048 MB RAM, CPU Pentium 4 Celeron 2000 MHz,

Internal ATA Compact Flash, 256MB

BIOS Flash M50FW080 @ 0xfff00000, 1024KB

A downgrade emergency had to be made.

Someone could help me on this problem,

thanks

Labels:
0 Helpful
4 Replies 4

Mike Williams
Level 5
Level 5

‎09-25-2013 10:17 PM

Can you please post more specific of the problem?

Also, I believe the correct upgrade path is 8.2.5 -> 8.4 -> 9.x.

Please try upgrading first to 8.4 and see if you have any problems. If not, then try upgrading to 9.x.

Regards,
Mike


Sent from Cisco Technical Support Android App

0 Helpful

lbellicaud
Level 1
Level 1
In response to Mike Williams

‎09-25-2013 10:33 PM

Hi Mike,

my customer upgrade cluster 8.2.5 --> 9.x it's same problem, they had ressource limit after 6 hours.

Me i upgrade cluster to 8.2.5 --> 8.4.7 --> 9.0.3 it's same problem they had ressource limit after 4 hour.

I have a show tech when my customer had this problem,

thanks


0 Helpful

pankaj29in
Level 1
Level 1
In response to lbellicaud

‎09-26-2013 12:31 AM

Hi,

I feel that the major change in the IOS was from 8.3(1) so i think you should upgrade from 8.2-->8.3(1) --> 8.3(2)--> 9.0

Directly upgrading to 8.4 might give some bugs.

about your problem kindly elaborate on this, what issue exactly are you facing?

Regards

Pankaj

0 Helpful

lbellicaud
Level 1
Level 1
In response to pankaj29in

‎09-26-2013 02:03 AM

Hi,

the problem is a loss of packets and problems of delays on the network that the problem appears:

Here "show conn":

fw-intranet# show conn

19765 in use, 32645 most used

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:00:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:00:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:1096 inside UCM2:0, idle 0:00:51, bytes 0, flags Ti

TCP pvives 172.27.72.127:1097 inside UCM2:0, idle 0:00:58, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:02:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:02:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:04:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:04:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:06:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:06:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:08:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:08:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:10:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:10:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:12:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:12:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:14:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:14:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:16:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:16:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:18:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:18:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:20:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:20:44, bytes 0, flags Ti

<--- More --->

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:22:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:22:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:24:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:24:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:26:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:26:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5062 inside UCM3:0, idle 0:28:44, bytes 0, flags Ti

TCP pvives 172.27.72.127:5060 inside UCM3:0, idle 0:28:44, bytes 0, flags Ti

UDP pvives 172.28.61.242:5741 inside 172.20.1.174:64707, idle 0:01:56, bytes 92, flags -

UDP pvives 172.28.63.240:5741 inside 172.20.1.174:64700, idle 0:01:57, bytes 110, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:58691, idle 0:00:00, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:41753, idle 0:00:05, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:37396, idle 0:00:10, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:37337, idle 0:00:16, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:47803, idle 0:00:21, bytes 8529, flags -

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:00:23, bytes 0, flags Ti

UDP pvives 172.27.63.44:1049 inside UCM1:44352, idle 0:00:26, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:35562, idle 0:00:32, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:58474, idle 0:00:37, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:42020, idle 0:00:42, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:57635, idle 0:00:48, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:48088, idle 0:00:53, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:41501, idle 0:00:59, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:47136, idle 0:01:04, bytes 8529, flags -

<--- More --->

UDP pvives 172.27.63.44:1049 inside UCM1:51395, idle 0:01:09, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:34541, idle 0:01:15, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:54197, idle 0:01:20, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:43172, idle 0:01:25, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:52176, idle 0:01:31, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:40809, idle 0:01:36, bytes 8529, flags -

TCP pvives 172.27.63.44:1073 inside UCM2:0, idle 0:01:37, bytes 0, flags Ti

UDP pvives 172.27.63.44:1049 inside UCM1:45621, idle 0:01:41, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:57593, idle 0:01:47, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:50029, idle 0:01:52, bytes 8529, flags -

UDP pvives 172.27.63.44:1049 inside UCM1:46190, idle 0:01:57, bytes 8529, flags -

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:02:23, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:04:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:06:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:08:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:10:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:12:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:14:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:16:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:18:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:20:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:22:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:24:24, bytes 0, flags Ti

TCP pvives 172.27.63.44:5060 inside UCM3:0, idle 0:26:25, bytes 0, flags Ti

,

thanks

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card