topic Upgrading FMC to 6.2.3 problems in Network Security

Upgrading FMC to 6.2.3 problems

Carstenlymann — Fri, 21 Feb 2020 15:42:13 GMT

Im upgrading my FMC FS-2000 from 6.2.2 to 6.2.3, from the documents it should take about 40mins.

Its now been running for 2 hours.

The last thing i can see in status.log from CLI is:
ui:[10%] Running script 000_start/400_run_troubleshoot.sh...

Is it just a waiting game now? Or is there an error and what to do?

Call TAC ?

Anything i can do ?

I ran the readiness check before and it was a pass:

[180504 08:20:21:596] Readiness check completed....
[180504 08:20:21:602] Attempting to remove upgrade lock
[180504 08:20:21:603] Success, removed upgrade lock
[180504 08:20:21:605]
[180504 08:20:21:606] #######################################################
[180504 08:20:21:607] # UPGRADE READINESS CHECK COMPLETE status : PASS #
[180504 08:20:21:608] #######################################################

All help appreciated

/ Carsten

Re: Upgrading FMC to 6.2.3 problems

yogdhanu — Fri, 04 May 2018 14:05:10 GMT

Hi There,

if the upgrade has not failed and is still waiting at a script, I would suggest to wait for some more time.

Check the /var/common directory on CLI and check if the size of new troubleshoot file being generates is increasing or no.

If its not increasing, raising TAC case would be a good idea.

Hope it helps,

Yogesh

Re: Upgrading FMC to 6.2.3 problems

Carstenlymann — Fri, 04 May 2018 16:23:22 GMT

Hi Yogesh

Thanks for reply.

The -troubleshoot.tar.gz file is not increasing in size. Its stayed the same all the way. Been stalling for 8 hours now.

I made a TAC case on it. Have got my first reply from them, now im awaiting the next after they got a copy of the main_upgrade_script file

/ Carsten

Re: Upgrading FMC to 6.2.3 problems

Carstenlymann — Tue, 08 May 2018 12:54:56 GMT

Just to update and finish this. 🙂

The upgrade process was stalled. TAC killed the process, and then it stalled again later on. According to TAC it was because of large events files, and many of them.

We deleted them all, and started the upgrade again, then it worked.

/ Carsten