topic Re: PA-500 Upgrade to 4.0.3 in General Topics

PA-500 Upgrade to 4.0.3

migration — Wed, 22 Jun 2011 09:59:19 GMT

Hi All,

I have just upgraded a PA-500 from 3.1.8 to 4.0.3 loading the 4.0.1 base first.

Once the unit rebooted the "Autocom" job has been stuck at 10% for the last 30 minutes and is still running.

Has anyone experienced this before, not sure if I should kill the job and recommit ?

Marc

Re: PA-500 Upgrade to 4.0.3

migration — Wed, 22 Jun 2011 10:09:37 GMT

Autocom just finished:

Results:

Enqueued ID Type Status Result Completed
--------------------------------------------------------------------------
2011/06/22 11:29:02 1 AutoCom FIN OK 12:08:35
Warnings:device: L3 Service Configuration is changed. l3svc will be restarted.

Details:device: Signature DFA installed successfully

Configuration committed successfully
Successfully committed last configuration

Re: PA-500 Upgrade to 4.0.3

reaper — Wed, 22 Jun 2011 11:34:27 GMT

Hi Marct

the autocommit after upgrading from3.1 to 4.0 will take a fairly long time and can take up to 1 hour in some rarer cases

what actually happens is that the config file gets migrated and the log index needs to be recompiled into a newer format introduced in 4.0, if the unit has been running for a long time, the log index is pretty big so this operation can take a while

regards

Tom

Re: PA-500 Upgrade to 4.0.3

migration — Thu, 23 Jun 2011 06:30:30 GMT

Thanks

Marc

Re: PA-500 Upgrade to 4.0.3

networkadmin — Sat, 25 Jun 2011 10:03:18 GMT

It was suggested I allow around an hour when we do upgrade from 3.1.x. Apparently you don't have to go to 4.0.1 first though. You do need it downloaded as it's the base image, but you can install 4.0.3 (or whatever is the latest) and upgrade directly to that.