I would like to point a very important point here. Version 4.x is meant for generation 1 boxes and Version 5.x is meant only for generation 2 MARS appliances (the one manufactured after Cisco's acuiqsition with more reliable components).
So there is nothing like a 4.3.x to 5.3.x upgrade unless you got a newer box. Keep that in mind :)
"Is it true that i need to upgrade it 1 version by 1, e.g. from 4.2 to 4.3 to 4.4 and so on...? "
yes. re-imaging is only an option if you can tolerate losing data or its a new appliance.
"Also, what would be the better way to do this, i.e. CD based or from URL/network server? "
Either way is fine. The first thing the network upgrade does is copy it locally. You mention the CLI in a followup post, definitely use the CLI versus the GUI. The GUI provides you with no status messages, the CLI does.
"Please share your experience/best practices, don't refer to any docs, as the available docs don't comparisions/options available.. thnx
There are two different situations. If you have a new box or don't care about the data on it, re-image. It doesn't make sense to apply all those incremental upgrades. I have gone through the incremental upgrade route with 2 different SEM's now, I can tell you that at the end of the day...IME the re-imaged box won't look exactly like the upgraded box. With Netforensics we had missing indexes, records, different database configurations, etc. I suspect the same with MARS, but as an appliance can't readily verify.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :