06-19-2018 02:07 AM - edited 02-21-2020 07:53 AM
Hello,
I am running/having FMC 6.2.1 on a VM.
I want/need to update to 6.2.3 ; I went to Cisco's website and downloaded on my PC
Sourcefire_3D_Defense_Center_S3_Upgrade-6.2.3-88.sh.REL.tar
I went into Dashboard aka GUI, System\Update and manually added the package. I can see in the browser below the upload process increment then I am left with browser tabs rolling until my session times out.
I see no other progress bar or anything (see the attachment).
SSH into the box shows in \var\tmp the file being fully uploaded but obviously I am stuck.
Box has Internet access and obviously I have SSH admin on it.
Does anyone have any hint?
My idea would be to do the whole upgrade process from CLI, after all it's a Linux. Trouble is I COULD not find any CLI procedure.
Thanks in advance,
Florin.
06-19-2018 02:42 AM
How long you waited after the upgrade? When you go to update page again do you see the package listed? If yes, did you try to hit install for this package.
06-19-2018 03:49 AM
06-20-2018 05:25 AM
I managed to update (through GUI) to 6.2.3 after getting WebGui timeout from 6 to 60'.
Now I am left with two questions on this thread:
- "System processes are starting, please wait." After each update, appliance reboots and then I am left with this message for a while: several minutes. What's the "documentation" timeout/interval for all services to start?
- Is there any CLI procedure to upgrade FMC?
Thanks!
06-21-2018 12:33 AM
There's no documented time for FMC to start fully. As you noticed, it will give you the "...starting" message in the GUI until it's fully up.
You can initiate upgrades from the cli although it's not documented, recommended or supported. If you examine the upgrade files, they are generally .sh files or shell scripts. Actually they are scripts that bundle scripts and even more scripts further down. If you monitor the log files in /var/log/sf during an upgrade you will see all of the subscripts executing in sequence.
06-26-2018 04:00 AM
06-26-2018 05:08 AM
It can be done but as I noted Cisco TAC does not recommend it be performed by customers.
You are bypassing the intended behavior of the system (possibly including the ability to recover from failure) by using that method. It may work 99 times out of 100 but you don't want to be that 100th case.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide